A guide on how to set up content migrations on GovCMS SaaS where the requirements fall outside what is usually handled by the Migrate module.
Frequently asked questions
GovCMS migrations need to account for the platform's specific module set, hosting model (SaaS vs PaaS), security and compliance requirements, and the Australian Government Design System, meaning generic Drupal migration experience isn't automatically the same as GovCMS-specific migration experience, and a partner should be able to demonstrate GovCMS-specific migration delivery, not just Drupal migrations generally.
Drupal 7 reached end-of-life in January 2025, meaning security patches have stopped, an agency running a GovCMS 7 site is carrying real security exposure the longer this continues, and migration planning should be treated as a near-term priority, not a "someday" project.
Not necessarily in full, but migration is a natural opportunity to fix accumulated content and information-architecture debt at the same time as the technical upgrade, since you're already touching every piece of content, most organisations find the marginal cost of improving structure during migration is far lower than doing it as a separate project later.
Insights
Related content
Topic
Morpht is a member of the GovCMS Drupal Services Panel and is the leading supplier of GovCMS web development services.
Service
We are a leading provider of GovCMS sites and have worked on the largest and most complex builds on the platform.
Service
Fast track your the build of your site with this personalisation-enabled, feature-rich starter site optimised for the GovCMS platform.
Service
Take advantage of the GovCMS platform by migrating your current site to the platform.