> ## Documentation Index
> Fetch the complete documentation index at: https://docs.monk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Move to another cloud

> Run your app in a different cloud alongside the current one, then switch over

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

* Credentials for the target cloud: [AWS](/getting-started/credentials-aws), [GCP](/getting-started/credentials-gcp), [Azure](/getting-started/credentials-azure), [DigitalOcean](/getting-started/credentials-digitalocean) or [Hetzner](/getting-started/credentials-hetzner).
* The app's `MANIFEST` and Dockerfiles in your repository.

## 1. Compare estimates

```
/monk estimate what this app would cost on Hetzner in fsn1
```

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

```
/monk plan a deployment of this app to a new cluster on Hetzner in fsn1
```

Review the plan in the [local dashboard](/getting-started/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

```
/monk is everything healthy on the new cluster?
/monk show me the api logs on the new cluster
```

## 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](/guides/backup-and-restore).

## 5. Switch traffic

Point your domain at the new cluster. See [Custom domain](/guides/custom-domain). Keep the old cluster until you are sure.

## 6. Remove the old cluster

```
/monk delete the old AWS 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](/guides/cicd).

## Next

* [Choose a cloud](/guides/choose-a-cloud)
* [Clusters and clouds](/concepts/clusters-and-clouds)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.