Server to cloud migration guide

Use our step-by-step migration guide for resources and best practices to ensure a successful move to cloud

Phase 4: Test

In this phase we’ll do a test run and make sure everything is in order, figure out how long the migration will take, uncover any issues, and develop our migration runbook.

Test migration

Regardless of company size or migration complexity, we recommend all customers run through a test migration before executing a production migration. Make sure you’ve completed everything in the pre-migration checklist from Phase 3 prior to using our testing guide to walk through your test migration.

Exclamation point icon

Refer to our documentation on how to use the Cloud Migration Assistants to run your migration if you’re using this method.

During the test migration, here are some of the tasks you’ll carry you as part of this phase:

Test migration

Backup your data

Regardless of which migration strategy and method you’ve chosen, we recommend backing up your self-hosted instance prior to migrating it. If there is data in your cloud site already, ensure this is backed up as well.

User Acceptance Testing

Part of the test migration is conducting User Acceptance Testing (UAT) so your end users can replicate common day to day tasks and make sure they work as expected. Through this process you can uncover any issues that will impact your end users and help your teams prep for the change that comes with cloud. Review step 6 of the testing guide for details on conducting UAT. 

Build your runbook and timeline

Throughout your test migration, put together a runbook or step-by-step checklist of what needs to happen when and any instructions needed, who the owner is for each task, and how long each step will take. It also helps to note what steps are dependent on each other and will prevent you from moving forward if not completed. At the end of your runbook, include a mitigation plan with owners just in case you need to roll anything back. To get started, download our runbook template below and modify any tasks as needed. 

Once you’re comfortable with your test migration and how it went, move on to choosing your production migration window and communicating your plan in the next step.