On this page:
- Overview
- 1. What are your upgrade options?
- 2. Your upgrade responsibilities?
- 3. What influences upgrade complexity?
- 4. If you upgrade to D8 first, then what?
- 5. What’s involved to upgrade from D7?
- 6. What happens if you don’t upgrade?
- 7. Where and how do you start?
- 8. What resources do you need?
- 9. Cost and time to upgrade from D7?
- Can’t find the answers you’re looking for?
Overview
The following FAQs provide information about upgrading your GovCMS SaaS Drupal 7 site to Drupal 9.
A list of all D9 FAQ topics can be found at GovCMS Drupal 9 upgrade FAQs.
1. What are your upgrade options?
Drupal 9 is not backward compatible with Drupal 7.
There was a major change in the underlying Drupal architecture after Drupal 7. Therefore, a simple upgrade path is not available from Drupal 7 to Drupal 9. This is also true from Drupal 7 to Drupal 8. This means sites on Drupal 7 will require a rebuild and migration.
The following upgrade options are available to you:
- Rebuild and migrate like-for-like onto Drupal 8 first (recommended):
Rebuild and migrate means that all functions and frontend theme templates need to be rebuilt on the Drupal 8 distribution and all content will need to be migrated.
Once on Drupal 8 you can then leverage an easier upgrade path to Drupal 9, which will be supported by Finance. See SaaS Drupal 8 FAQs - What are for further information.
GovCMS encourages this option if your budget and resources allow it. The GovCMS D8 distribution is available and is stable. This will also reduce critical dependencies on the GovCMS Drupal 9 release date and reduce the risk of project delays.
Rebuild and migrate like-for-like onto Drupal 9:
Rebuild and migrate directly onto the GovCMS Drupal 9 distribution as soon as the release is available.
Choose this option if you can’t secure funding this budget cycle, or can’t commence the upgrade until after the release of the Drupal 9 distribution.
The rebuild and migrate complexity for both options will depend on the types and levels of customisations required (see SaaS Drupal 7 FAQ - What influences ). For both options, a like-for-like rebuild is recommended. However, you can incorporate minor enhancements. If significant enhancements are required, then you should consider a new design and build.
2. Your upgrade responsibilities?
The table below shows the SaaS Drupal 7 upgrade steps and your responsibilities versus GovCMS’s.
Activity | Responsibility | Description |
|---|---|---|
Upgrade site | Agency* | SaaS Drupal 7 agencies are encouraged to take responsibility for upgrading their own sites. Since Drupal 9 is not backward compatible with Drupal 7, upgrading requires a rebuild and migration. See FAQ SaaS Drupal 7 - What are my upgrade for details. See FAQ SaaS Drupal 7 - What’s involved in upgrading Drupal . |
Regression test | Agency | You’ll be responsible for regression testing and identifying issues. |
Remediation | Agency | You’ll be responsible for remediating all issues identified. |
Go live | GovCMS | GovCMS will deploy your site live once approved by the Agency product owner. |
*Finance will not leave you hanging and will provide support along the way. See the FAQ SaaS Drupal 7 - What tools, resources, guidelines and support are available to help me upgrade from .
3. What influences upgrade complexity?
The following factors influence rebuild and migrate complexity when upgrading from Drupal 7 to Drupal 8 or 9.
| Influencer | Description |
|---|---|
Content structures  | Content types. Media. Taxonomies. Paragraphs. Number and make up of the content structures, including standard content types, media, taxonomies, paragraphs, etc., influences upgrade migration complexity from SaaS Drupal 7. |
Modules  | Ported modules. Deprecated modules. Similar modules. Drupal 7 modules are not compatible with Drupal 8 and Drupal 9 and thus a mapping is required for feature parity. The more modules used, the more site configuration is required. The number of deprecated modules that do not have one-to-one simple upgrade paths typically influence the upgrade rebuild complexity. |
Theme templates  | Basic theme. Extended theme. Custom theme. Level of site theme customisations (such as number of templates, stylesheets, CSS, JavaScript, number and fidelity of functions, and ‘cyclomatic complexity’, etc.) influences upgrade rebuild complexity. This also applies for the admin theme. Fewer out-of-the-box theme variations = more one-to-one mappings = easier rebuild. |
Views  | Listing pages. Content blocks. Search pages. Views are used to build content listing pages, content blocks, search pages, etc. Views cannot be migrated/upgraded programmatically. Thus rebuild is required. The number of views and the level of customisation influences upgrade rebuild complexity. |
Search  | Faceted searches. Search indexes. Number and level of faceted search configurations and search indexes typically influences upgrade rebuild complexity. |
Webforms  | Field validations. Dynamic interactions. API integrations. Number and complexity of webforms (number of fields, interactions, API integrations, etc.) influences upgrade rebuild complexity. |
Integrations  | 3rd party integrations. API integrations. Custom integrations. Number and nature of integrations influences rebuild complexity. ‘Standard’ migrations, such as AB testing tools, Google Tag Manager, etc., require less upgrade rebuild effort than complex integrations such as batch migrations, etc. |
Pages  | Content structures. Page counts. Manual or automated migrations. Number of pages combined with the number of content structures can inform upgrade migration complexity, and when manual vs automated migration of content is required. A site with only 100 content pages across 2-3 content types can be migrated manually, however a site with 1000s of pages across multiple content structures requires automated migration scripts. |
4. If you upgrade to D8 first, then what?
See FAQ SaaS Drupal 7 - What are my upgrade on
when you should consider upgrading to Drupal 8 first.
The Dept of Finance will design and build upgrade scripts for all SaaS D8 sites. As part of this process, it will also determine how to best map deprecated Drupal 8 distribution features onto Drupal 9 (in consultation with agencies).
Finance will then run the upgrade scripts on behalf of all SaaS D8 agencies and deploy the upgraded D9 version to a test branch.
It’s up to each site owner to then conduct a full regression test and remediate any identified issues/bugs. Once approved, the site owner gives GovCMS the green light to push live.
5. What’s involved to upgrade from D7?
At a high level, upgrading from Drupal 7 involves mapping your site’s content structures, features, and UI to Drupal 9 out-of-the-box content structures, features and theme templates and then addressing any gaps.
The illustration and table below provide a summary of the six key phases involved in rebuilding and migrating from Drupal 7 to Drupal 9.
Salsa has designed and made publically available our entire 24-step rebuild and migration project delivery process. Please visit Drupal 9 site migration project delivery blueprint to view.
Phase | Activity |
|---|---|
1. Discovery  | An audit of functionality, design and content, which is then mapped to corresponding Drupal 9 features/modules, templates and content structures. We’ll also identify any gaps between your D7 site and GovCMS Drupal 9, and make recommendations on how to proceed. |
2. UI/UX design  | Optional design to create new or adapted visual designs and user interactions. This is not typically required if rebuilding like-for-like. |
3. Planning  | Sprint planning to build a groomed product backlog to inform sizing and priority. Developer onboarding in preparation for build. |
4. Upgrade  | Upgrade involves core rebuild and migrate activities. Features are developed, UI is themed and content is migrated. |
5. Go live  | Go-live deploys your site and delivers supporting documentation and training. |
6. Support  | Support is optional and available to provide minor enhancements, issue investigations, bug fixes, content support and general enquiries, all via our service desk. |
6. What happens if you don’t upgrade?
Since Drupal 7 will be end-of-life, not upgrading will mean no security updates or enhancements. This means your site will pose a critical security risk, not only for the agency but also to the entire GovCMS SaaS platform.
If you cannot upgrade you’ll need to reach out to GovCMS ASAP to explore your options.
Some options to consider are:
Seeking upgrade support from the Dept of Finance
Decommissioning your site as it may no longer be required
Rehosting your site elsewhere
7. Where and how do you start?
GovCMS recommends all Drupal 7 sites should aim to switch to Drupal 9 by the end of August 2022. The first step we recommend is to start planning — this involves understanding your upgrade options, costs, risks and timelines.
If you haven’t already done this we have a few free resources to help you plan:
Free GovCMS Drupal 9 upgrade price guide: Our price guide helps you self-assess and understand your options, costs and timelines for upgrading like-for-like from Drupal 7 to D8 or D9.
Free GovCMS Drupal 9 readiness assessment: Our free readiness assessment provides you with a high level overview of your specific upgrade options, costs and timelines.
If you know your scope and/or have a team and want to jump straight into it then the next step is to start your upgrade project.
In FAQ SaaS Drupal 7 - What’s involved in upgrading from we outline the high-level stages of the upgrade process, along with Salsa’s free GovCMS Drupal 9 upgrade project delivery blueprint. Our upgrade project blueprint provides the entire delivery process, including tools and templates, for rebuilding and migrating your Drupal 7 site to D8 or D9. We encourage you to use this blueprint as a guide for your own team to deliver your upgrade project.
If you require further support or direction with planning then you may consider one of our Drupal 9 assessment or advisory services:
GovCMS Drupal 9 site assessment: A deep dive to assess your Drupal site to determine viable options, risks, mitigations, costs and timelines. We will provide formal recommendations to support budgeting and approvals.
GovCMS Drupal 9 upgrade technical advisory and support: Access to Drupal expertise to provide your upgrade project delivery team with technical advice and/or ad-hoc support.
GovCMS Drupal 9 upgrade site discovery: Our functional and technical Drupal experts pair up to facilitate a series of workshops to help create, groom and size your upgrade project backlog for prioritisation and planning.
Once you have completed your planning and you’re ready to start your upgrade project then you may consider the following service:
- Drupal 7 like-for-like upgrade to Drupal 8 or 9: Engage our team to rebuild your site like-for-like. We’ll run the audits, confirm the mappings and present your options. More information can be found on our GovCMS Drupal 9 upgrade services page.
8. What resources do you need?
If upgrading from Drupal 7 you’ll require a rebuild and migration. The typical roles involved in a like-for-like rebuild and migration project are outlined below. The roles can often be fulfilled by the same person. The allocation for each role depends on the size and complexity of your rebuild.
| Role | Responsibility |
|---|---|
Product Owner | Responsible for representing the business benefit of proposed solutions. Responsible for approving and ranking the user story backlog, accepting work achieved in sprints, and signing off on development milestones. |
Project Manager | Project coordination and management of risks, issues, timeline, budget, resourcing and stakeholder communications. |
SCRUM Master / Business Analyst | Provide expert advice on the functional specification. Responsible for refining and grooming the requirements and acceptance criteria as part of discovery and throughout the project. SCRUM Master will also facilitate agile ceremonies including sprint planning, demos and retros. |
Solution Architect | Solution architecture design. Facilitates technical decisions and alignment with all key stakeholders. Responsible for overall solution direction and roadmap, as well being the technical client liaison. Typically only required for complex upgrades where new/revised solution architecture is involved. |
Technical Lead | Provides implementation blueprint and technical solution direction, technical governance and engineering process. Responsible for user story estimations, code reviews, peering, coaching, and troubleshooting. |
Backend developer(s) | Backend Drupal development, integrations and content migrations, user story estimations, peering, coaching and troubleshooting. |
Frontend theme(s) | Frontend Drupal theme development, user story estimations, peering, coaching and troubleshooting. |
QA | Design and execute test cases (including automation if/as required), collaborate and verify fixes, etc. |
The following design-related roles are optional and are only considered if your upgrade from Drupal 7 to Drupal 8 or 9 requires new/different designs from your current site.
| Role | Responsibility |
|---|---|
Design Lead | Overall visual strategic direction, representing client’s brand while ensuring user needs are front-and-centre. Creating individualised designs while leveraging design systems for usability, accessibility and cost savings. |
UI/UX Designer | Drives user-centred design, including creative workshops. Responsible for taking the client’s website design from low-fidelity wireframes to high-fidelity mockups for user testing. Works with the Design Lead to leverage relevant design system components, focusing on the user experience and user interface. |
9. Cost and time to upgrade from D7?
Upgrading from Drupal 7 requires a rebuild and migration. See FAQ SaaS Drupal 7 - What are your upgrade for more details. Rebuild and migration costs are informed by site build configuration and complexity.
The FAQ SaaS Drupal 7 - What influences covered this in detail however in summary site build and configuration complexity depend on the number and nature of the following eight key factors:
- Content structures
- Modules
- Theme templates
- Views
- Search
- Webforms
- Integrations
- Pages
Costs also depend on whether you’re upgrading to the basic default theme, an extended theme or a custom theme.
PaaS vs SaaS hosting has little-to-no influence on the complexity and cost however Drupal 7 sites on PaaS likely have more complex site build configurations. This assumes you remain on your current hosting configuration.
The table below provides a price guide to rebuild and migrate your GovCMS Drupal 7 site.
| Rebuild and migration options, costs and timelines | Suitability and summary of inclusions |
|---|---|
Basic site: Out-of-the-box theme Cost: $10K-$20K (ex-GST) Timeline: 2-4 weeks Sprints: 1-2 discovery workshops; 1-2 build sprints | For very basic sites with basic functionality that can be mapped to out-of-the-box features and theme templates with basic configuration. Configuration of out-of-the-box content structures, theme templates and views. Basic feature module configuration, basic search (no facets) and basic webforms. No integrations. Content migration of unlimited pages (with Merlin). |
Moderate site: Extended theme Cost: $20K-$120K (ex-GST) Timeline: 4-8 weeks Sprints: 1 discovery sprint; 2-3 build sprints | For sites with moderate features and UI that can be mapped to out-of-the-box theme with moderate extensions and moderate backend configuration. Minor extensions to out-of-the-box theme templates, views and content structures. Configuration of out-of-the-box modules. Basic search with simple facets. Moderately complex webforms. Basic integrations. Migration of unlimited pages (with Merlin). |
Complex site: Custom theme Cost: $120K-$280K+ (ex-GST) Timeline: 8-16+ weeks Sprints: 1-2+ discovery sprints; 3-6+ build sprints | For complex sites with custom features and UI that can be rebuilt with Drupal using custom themes and custom backend configuration. Customisation of complex content structures, themes and views. Moderately complex feature module configuration, site search with complex facets and complex webforms. Complex custom integrations and content migration of unlimited pages (with Merlin). |
Salsa has created a free comprehensive GovCMS Drupal 9 upgrade price guide that allows you to self-assess your project costs and prepare your upgrade budget. Our price guide is designed to allow you to self-assess based on your site configuration.
You can request this price guide here: GovCMS D9 price guide registration.
Alternatively Salsa has designed a free D9 readiness assessment service that provides you a high level overview of your upgrade options, costs and timelines. With this service we take you through our 4 step process to get you ready for Drupal 9.
You can register for this service here: GovCMS D9 readiness assessment registration.
Can’t find the answers you’re looking for?
Ask us. We love tough questions. Contact us for the answers you seek.
