Skip to main content

Migrating an existing site to GovCMS

Talk to us first

If you're going to be migrating to GovCMS, you need to sort out your hosting plan. Contact us early, we can give you advice on your hosting options, the differences between SaaS and PaaS (and which may be right for you), and we will prepare a quote so you know what your ongoing costs will be.

You don't need to lock in your hosting plan before you get started on your migration, you might choose to start with a development plan, and finalise things later in your project. We only invoice you for your hosting once your site is ready to go live. Development plans are invoiced separately, depending on what option you choose.

The minimum you need to do is sign your Memorandum of Understanding (MOU). This is a standard agreement signed by all our customers. The GovCMS team includes engagement and onboarding specialists and we will walk you through the entire process.

Planning your migration

GovCMS Drupal websites (SaaS)

If you're going to use the fully managed SaaS hosting option, you need to:

  • ensure that the configuration and codebase used for your site match the official GovCMS Distribution
  • arrange installation of your website into GovCMS - we do this for you - make sure you leave plenty of lead time so we can fit your job in
  • test the new website to confirm that it's ready to go-live
  • link your domain to the relocated website - and GovCMS will link your site into the web protection services that are included with your plan
  • set a date, drop your site shield, and your site is live on the SaaS platform.

Non-GovCMS Drupal websites (PaaS)

If you use unsupported modules you will have to choose PaaS hosting. You need to manage more of the migration process yourself. For PaaS:

  • GovCMS will setup your project, user accounts, and give access to your developers (or your service provider)
  • you are responsible for
    • installing your site on the platform
    • security certificates
    • testing the new website to confirm that it’s ready to go-live
    • conducting your own IRAP assessment and accreditation
    • linking your domain to the relocated website
    • managing your launch plan.

Non-Drupal websites

GovCMS only hosts websites that use Drupal as the content management system - if you're wanting to migrate a site that's not build on Drupal - you need to rebuild your site.

Using your own resources or chosen provider, it's time to start building.

You can build directly into the GovCMS environment. Your project is secure and backed up from day 1, and you start using the tools you will use to manage your site once it's live and publicly available.

You can alternatively build in your preferred development environment and arrange later migration to the GovCMS environment. There's a few more steps involved in this option, and getting your site ready to go live will include additional lead time.

Once the appropriate documentation is agreed between your agency, any relevant service providers and the GovCMS team, the build can commence.

During your project, you will need to:

  • identify any functionality that matches the GovCMS Distribution - if you use unsupported modules you will have to choose PaaS hosting
  • confirm whether a website redesign will form part of moving to GovCMS - you can keep the look and feel of your site the site, but you will need to rebuild all of the templates
  • decide if you're building on the GovCMS platform, or building the site elsewhere and forklifting on closer to go live
  • map and migrate content from your old website to the new one - and dont forget to set up redirects where links are changing
  • test the new website to confirm that it’s ready to go-live
  • arrange for your site to be installed on to the GovCMS platform (if you chose not to build on the platform)
  • work with the GovCMS team to link your domain to the relocated website.