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.
A migration that makes your site better, not only newer
Migration touches every piece of content, so it's the cheapest moment to fix accumulated problems such as inconsistent content types, messy taxonomies, and poor findability. Most organisations find that improving structure during migration costs far less than doing it as a separate project later.
We plan the content model and the redirect strategy before migration begins, so your content and search rankings are protected rather than repaired afterwards.
What you get:
- Content and links preserved. Redirects and metadata handled before migration starts.
- A platform agencies trust. GovCMS's vetted codebase and IRAP-assessed security.
- A clear way to engage. Through the Drupal Services Panel.
Our approach to GovCMS migration
Start with a content audit
We review what content exists, what's still valuable, what should be retired, and how it should be re-modelled in Drupal.
Plan for GovCMS
We account for the platform's module set, hosting model (SaaS or PaaS), security and compliance requirements, and design system, drawing on our experience of building on GovCMS.
Migrate and redirect
We map old URLs to new ones with redirects, keep metadata and structured data, and validate indexing before and after go-live.
Design and build with one partner
We can be your design and development partner. Our starter site, Convivial for GovCMS, gives the new site editor-friendly tools and accessibility features from day one.
Why agencies choose GovCMS
Procurement
A Head Agreement with Drupal suppliers makes it easy to engage quality Drupal agencies.
Codebase
A vetted open-source codebase, maintained by the GovCMS team.
Security
An IRAP-assessed platform that removes many of the headaches of finding a secure host.
Drupal Services Panel
A select group of Drupal agencies available to deliver website development.
Pricing
Levels from micro sites up to giga, with attractive pricing for smaller sites.
Frequently asked questions
GovCMS migrations need to account for the platform's module set, hosting model (SaaS or PaaS), security and compliance requirements, and the Australian Government Design System. Generic Drupal migration experience isn't the same as GovCMS migration experience, so ask a partner to show GovCMS-specific delivery.
Drupal 7 reached end of life in January 2025, so security patches have stopped. An agency still running a Drupal 7 site carries real security exposure, and migration planning should be a near-term priority, not a "someday" project.
Not necessarily in full. Migration is a natural opportunity to fix content and information architecture problems, because you're already touching every piece of content. Most organisations find the extra cost of improving structure during migration is far lower than doing it as a separate project later.
The two biggest risks are losing content or search rankings through poor URL and metadata handling, and simply replicating old structural problems (inconsistent content types, messy taxonomies) on new infrastructure. Both are managed the same way: proper content modelling and a redirect strategy planned before migration begins, not bolted on afterwards.
With proper planning, yes. Mapping old URLs to new ones with correct redirects, preserving metadata and structured data, and validating indexing before and after go-live are well-understood practices. Ranking loss during migration usually signals a rushed redirect strategy, not a risk of moving to Drupal.
A discovery and content audit - understanding what content exists, what's still valuable, what should be retired, and how it should be re-modelled in Drupal comes before any technical migration work. Migrating without this step usually means moving years of content debt onto new infrastructure rather than actually improving it.
Case studies
Case study
Morpht moved Reef Guardian Schools to GovCMS SaaS with 382 schools and 800+ users, no re-registration, and a secure resource library just for teachers.
Case study
Morpht rebuilt the Australian Energy Regulator website on GovCMS, migrating 26,997 pages and 41,815 documents with no data loss, on schedule and on budget.
Case study
Morpht moved the Attorney-General's Department website from SharePoint to GovCMS, organising 1,200 pages and 6,000+ publications into nine searchable sections.
Case study
Morpht moved the NSW Food Authority website to GovCMS, migrating 8,000+ pages and files. Traffic rose 9.7% year on year and time on page increased by 44%.