---
title: "Migrate to exe.dev"
description: "Move a server, a Worker, or Durable Objects to an exe.dev VM: copied and checked while the original keeps serving, moved when you say so."
url: https://exe.dev/deploy/category/migration
---

# Migrate to exe.dev

Moving house is mostly packing. These recipes do the packing: they copy
what you run elsewhere onto an exe.dev VM, check the copy against the
original while the original keeps serving, and leave the moment of the
move to you. Until then, the original serves as before, and your copy
is private behind exe.dev's [proxy](/docs/proxy).

## All 2 migration recipes

- [Migrate a DigitalOcean Droplet to exe.dev](https://exe.dev/deploy/migrate-digitalocean-droplet.md): Same server, new home. Rehearsed while the droplet keeps serving.
- [Migrate a Durable Object from Cloudflare](https://exe.dev/deploy/migrate-durable-objects.md): Same Worker, same objects, new home. Every key and row checked.

## Frequently asked questions

### Is my app down while it moves?

Only for the final copy. The rehearsal copies everything while the original keeps serving; the move stops it, copies what changed since, and then your domain points at the VM.

### Can I go back?

Until your domain moves, yes: the original keeps its data and carries on as before. After that, new data lives only on the VM.

### Who can reach the copy?

Only you, until you [share](/docs/sharing) the VM or make it public with `ssh exe.dev share set-public <vm>` as part of the move.

[All recipes](https://exe.dev/deploy.md)