Frequently Asked Questions

See our Timeline page for the most up-to-date information. If you have an Open Berkeley site, you may choose to either rebuild your site in Berkeley Web Builder as an early adopter or wait for the Web Platform Services team to programmatically migrate your site. If you are a new customer without an existing Open Berkeley site, then you may request to be an early adopter.

Berkeley Web Builder will offer the same features and benefits as Open Berkeley with the following enhancements and improvements:

• Redesigned user dashboards
• Ability to use custom as well as templated layouts
• Streamlined content types
• Updated Berkeley Brand look and feel
• And more

See the Preview page for more information about the above list.

Open Berkeley, the original version of the platform, was built using Drupal 7. Berkeley Web Builder has been built using Drupal 10, a more recent version of Drupal with more robust capabilities, which has allowed us to introduce new and improved features to better serve the needs of our university community. See the About and Preview pages for more information. 

The Berkeley Web Builder platform supports the Berkeley Brand guidelines for design, and the Berkeley Brand is managed by the Office of Communications & Public Affairs. Please contact the Berkeley Brand team with any questions and/or feedback: brand@berkeley.edu.

Depending on the size and scope of the Open Berkeley site, rebuilding the site in Berkeley Web Builder may be faster and less complicated than waiting for programmatic migration.

Programmatic migration requires significant technical processes and will take additional time to accomplish in order to ensure that Open Berkeley sites (i.e., all content and files and structure) are correctly moved to the new Berkeley Web Builder platform without disruption. If you have an Open Berkeley site and are eager to move forward with Berkeley Web Builder, then rebuilding your site will likely take less time than migration.

In addition to the technical processes, migration will require some manual work from campus teams. We will ask teams to review their content before migration and perform tasks (e.g., remove unpublished pages, update page layouts, etc.), and teams may also need to do post-migration cleanup on their sites due to technical and design differences between the two platforms. If you are taking the time to review your Open Berkeley site content, then it may be easier and more efficient to rebuild your site in Berkeley Web Builder at the same time. 

The Web Platform Services team will reach out to your designated Site Manager when we are ready to migrate your site. In addition to the programmatic migration, the overall process will involve some manual work from the respective website team. The Web Platform Services team will communicate the recommended steps that the website team should take before and after as a part of the migration process.

The new Site Manager role will be the main contact for the people working on individual Berkeley Web Builder sites. The Site Manager will also be the only role that will be able to modify other users’ roles in Berkeley Web Builder.

For more information, see the Site Manager Role page.

Eventually, all Open Berkeley sites will need to be rebuilt or migrated to the Berkeley Web Builder platform. We will not be developing new features or enhancements for the older platform. 

The Web Platform Services team will continue to support your Open Berkeley site until it has been migrated to Berkeley Web Builder. Sites hosted on Pantheon (including all Open Berkeley sites) have Drupal 7 Extended Support (D7ES) until at least January 2027.