Skip to Content
Open Beta — managed Kubernetes, DNS & more are live.
Migrations · beta

Move any server to Canada. Keep it running while you do.

One command on the source VPS, wherever it is hosted. We copy the disks over an outbound tunnel, keep syncing the changes, and cut over when you say so — with a health check and a way back.

Transfer

Block-level copy, over a tunnel the source opens

The agent reads the source disks live — no reboot, no downtime — and streams them, compressed and rate-limited if you ask, to volumes on Ceph in Montréal. Pick which disks come along; the first one is the boot disk.

Linux & WindowsOutbound TLSCompressionBandwidth cap
Start a migration
Cutover

Minutes of downtime, on the day you choose

When the full copy is done the migration sits in a syncing state for as long as you need. Trigger the cutover and the agent runs your quiesce command, sends the last delta, boots the instance on Patrii and polls your health-check URL — then repoints the DNS records you listed.

  • Quiesce — a command on the source before the final sync, for a consistent copy.
  • Health check — a URL polled after boot; failure fails the migration.
  • Rollback — DNS reverted and the source application restarted, automatically.
DNS & domains
Groups

Database, API, frontend — moved as one

Describe every server of a stack in one request, each with its role, flavor, network and DNS records. One installer per source, one progress view for the whole group, and three ways to cut over so the database lands before the services that depend on it.

SequentialCoordinatedManualPer-server roles
Open the console

Four steps, one of them yours

1

Describe the target

Name the migration, give the source's public IP, pick a flavor, a network and an SSH key, and choose how the agent connects.

2

Run the one-liner

Paste the generated installer on the source as root. It installs the agent and the full copy starts on its own.

3

Let it sync

Watch the passes and the last delta in the console. The source keeps serving; you pick the moment.

4

Cut over

Quiesce, final sync, boot, health check, DNS. If anything fails, the rollback puts the source back in charge.

Migration questions

No. The agent reads the disks while the server keeps running. The only downtime is the cutover: the quiesce command, the final delta and the boot on Patrii — usually minutes.

In the recommended outbound mode, nothing inbound: the agent needs HTTPS to Patrii Cloud to download itself and report, and it dials the transfer out. The direct mode pulls from the source and needs one inbound TCP port from Patrii's addresses.

Yes. Set a bandwidth cap in Mbit/s and enable compression; both are transfer options on the request. The copy simply takes longer and the live traffic is left alone.

Give the request a health-check URL. It is polled after the boot; if it never succeeds the migration is marked failed and, with rollback enabled, the DNS records are reverted and the source application is restarted.

List the records to repoint, in a zone hosted in Patrii DNS, and they are switched to the new address at cutover — and switched back on rollback. Zones hosted elsewhere you update yourself once the health check passes.

If you tick 'uninstall agent after success' the agent removes itself from the source once the migration is complete. Otherwise it stays idle until you remove it.