Migration to Integrated Web Platform (IWP)
Migration means that content will be exported from Site Builder and become available in Drupal. The goal is to migrate existing, relevant content to Drupal while avoiding migration of irrelevant, outdated, duplicate, and unused content, images, and files. Site Builder editors should complete the Site Builder and Blogs Cleanup actions provided in the last section below.
The list below provides information on what will be migrated. The migration is slated to begin Feb. 25, 2025. If these dates change, we will communicate it broadly. (Updated 2/3/2025)
Migration and conversion will be for existing sites and blogs on a specific date that will be communicated well in advance. Anything created before the migration date will be captured.
Cutover Stages
Migration is just one part of a multi-step transition process to Drupal/IWP. The stages are:
1. Migration Period: Content will be moved to IWP/Drupal (currently scheduled to begin Feb. 25 and taking approximately 8 days). Remember to finish your cleanup tasks and critical updates by Feb. 24; you will not be able to make website changes during the Migration Period.
2. Testing & Validation: Vendor & IT Team will check on migrated content.
3. Cleanup Window: All UC ANR content editors will clean up their content in Drupal, as best as possible, during a window planned for March 11 to March 21. Instructions will be provided, and office hours will be available for questions.
4. Go-Live: IT Team and Vendor will direct “ucanr.edu” to go to new IWP/Drupal site. Content editors will continue to edit on new IWP/Drupal platform.
5. Cutover Complete: The former Site Builder sites/Blogs will have a new “legacy” URL; old Site Builder and Blogs will not be editable, they will be hidden and accessible only through the Portal. Daily office hours for support will be available for a period after cutover.
What’s Migrating
Only Active Sites and Blogs and their contained content
Active sites are defined as published on Site Builder and/or Blogs. Draft and inactive pages with their containing assets will not be migrated. There will be no date of publication restriction on the content. Published Content in Site Builder will be set as “Published” in Drupal. This will avoid the risk of content issues across the entire website due to missing owners, editors, challenges with resources, etc.
Images and Files
Only files that are in use (i.e., published) will be migrated. “In use” is defined as published on the same site where the associated file library exists. Images and Files have the option of Alt and Title attributes as well as Captions; these will be migrated. Because Site Builder converts original file names into numbers, the Alt and Title Attributes become very important for identifying what images are about. Editors should ensure images on Site Builder have these attributes and captions populated.
Meta Descriptions
Each Page in Site Builder should have a unique and descriptive Meta Description. Existing Meta Descriptions will be migrated.
What’s Not Migrating
Site Builder comprises approximately 700 websites, thousands of pages, and thousands of files and images that are no longer being used. The overhead is enormous. Blogs suffer from the same issues. Over 465 Blogs exist and contain as many as 47,000 posts. Many of these blogs haven’t been used in years. Site Builder and Blogs use different underlying technologies, and some features or customizations won't translate directly to Drupal due to technical incompatibility.
Not migrating
These may be assessed for possible future migrations:
- Some Site Builder assets (e.g., ANR Survey Tool integration with sites, Site Builder blog comments, Newsletter subscribers).
- All custom Site Builder assets – These include assets that are widgets built by ANR IT for one site or one unit’s use (e.g., Universal Review System, custom databases and media players, custom survey result pages).
- Removed and inactive Site Builder pages and assets – These will be available on Site Builder during the transition period and eventually will be permanently deleted. If desired, individuals should back up this information onto a cloud service like Box.
- Unused images and files will not be migrated. These are files that are not being displayed in/inserted into any Site Builder pages.
- Sites hosted on other content management system platforms (e.g., WordPress, SiteFarm, UC IPM Cold Fusion site).
- Sites with no owner, no traffic, or no content – These will be made inactive and will not migrate. IWP team will reach out to admins/responsible parties/editors prior to inactivating any sites.
Not in scope
- ANR Portal applications will not be affected or changed (e.g. ANR Survey Tool, Collaborative Tools, Bibliography, Repository, Volunteer Management Systems).
- Customized websites are not part of the foundational build, which will provide a solid platform for enhancements in the future.
This may cause some disappointment. We appreciate your patience as we focus on delivering the foundational release. After the IWP system stabilizes, more information will be shared about alternative tools and how to request these items to be migrated in future stages. Non-Site Builder site migration can be evaluated post go-live on a case-by-case basis.
Questions or Concerns?
Check out the IWP FAQ page, and email iwp@ucanr.edu with any concerns that are not addressed there.
Disclaimer
IWP is an active project and all recommendations and requirements are subject to change. We will highlight any changes and encourage you to visit this page and other IWP web pages often to see the current status and recommendations.