Skip to main content
Monk has no one-step migration. Moving clouds means deploying the same app to a new cluster in the other cloud, checking it, moving data and traffic yourself, then removing the old cluster. Each step is reviewed.

​
Before you start

​
1. Compare estimates

The estimate covers the machines Monk would create, including Monk’s fee. Managed services and data transfer are billed separately by their providers.

​
2. Deploy to the new cloud

Review the plan in the local dashboard: machines, services and estimated cost. Some managed services are specific to one cloud (for example RDS on AWS). The plan shows what replaces them, or you can keep them where they are. Nothing is created until you approve. Both clusters run, and cost money, until you remove one.

​
3. Check the new environment

​
4. Move the data

Monk does not copy data between clouds. Use the database’s own export and import tools, or the backup and restore actions its integration provides. See Back up and restore.

​
5. Switch traffic

Point your domain at the new cluster. See Custom domain. Keep the old cluster until you are sure.

​
6. Remove the old cluster

The approval lists everything that will be deleted. Deleting a cluster removes its machines and the workloads on them. It can’t be undone. Back up anything you need first.

​
Limits

  • Settings made by hand in the old cloud, and data, are not carried over.
  • Update CI/CD so it deploys to the new cluster. See CI/CD.

​
Next