Agentless VM migration · Zadara · AWS · Azure
Move VMs between clouds. Know they boot before you switch.
Z-Move copies each disk through the cloud APIs, adapts the operating system when the new cloud needs it, and starts a test VM that has to answer on SSH or RDP. Nothing is installed inside your VMs.
- Speed and bottleneck measured live: 39.7 MB/s, limited by the source.
- Boot test passed: SSH answered on port 22 in 2m 28s.
- Every phase timed: 19m 40s from start to finish.
Timings from a real Azure East US → Zadara run (30 GiB). Names from the demo environment.
How it works
Four steps. One screen.
Your team, or your customers, run every migration from the same wizard. No scripts, and no jumping between consoles.
Wizard · source · AWS US East (Ohio)
Routes
Where are you moving?
Pick a source and a destination. Every figure comes from a real run.
Azure → Zadara
ValidatedDirect. One worker in Zadara reads the Azure snapshot itself, with nothing in the middle.
A Zadara image, with the system already adapted.
Adapted automatically in 3 s: cloud-init, network (netplan), Azure agent and fstab.
Validation run, Azure East US to Zadara, Ubuntu 24.04.
For cloud providers and MSPs
Offer migration under your own brand.
Run Z-Move as your own migration service. Your customers move their workloads into your cloud by themselves, and you bill the usage at your price.
Drag to switch brands. Acme Cloud is a fictional example.
- Your name, logo and color across the whole platform
- Your regions and endpoints, ready for your customers
- Self-service wizard with pre-checks, in English and Portuguese
- Usage metered per GB and per customer, with CSV export
- Each customer manages its own users, with MFA for administrators
- Private deployment inside your own cloud
A telecom operator runs Z-Move as its own Migration Service.
Security
Ready for your security review.
The questions your security team will ask, answered up front.
Your VMs stay untouched
Z-Move only reads snapshots through the cloud APIs. The source is never stopped or changed, so rolling back means carrying on with it.
Keys encrypted, then deleted
Cloud credentials are encrypted at rest, never written to logs, and deleted 30 days after the job ends.
Workers without secrets
Each temporary worker gets a token valid only for its job, opens no inbound ports and is destroyed at the end.
Encrypted in transit
TLS on every hop. Relayed disks stream in memory and are never written to disk. Azure routes go straight between the clouds.
MFA and an audit log
Administrators sign in with a second factor. Every change is recorded: who, what, when and from where.
Your own cloud, if you prefer
Run Z-Move inside your own infrastructure and keep every byte there.
Pricing
Pay for the data you move.
Pay as you go
For one-off migrations and teams that want full control of the cost.
- Billed on the data written to the destination, not on disk size
- A retry does not pay again for disks already copied
- Boot test, OS adaptation and cleanup included
- No setup fee and no subscription
Provider license
For cloud providers and MSPs that offer migration to their own customers.
- White-label and multi-tenant
- Private deployment in your cloud
- Usage reports per customer
- Onboarding, training and priority support
FAQ
The questions we hear most
Something else? Write to hello [at] zmove.click
Do I need to install anything in my VMs?
No. Z-Move works with snapshots and volumes through the cloud APIs, using temporary workers that it creates and removes itself.
How much downtime should I plan for?
Z-Move copies a snapshot, so the source keeps running. For a consistent copy of a busy application, stop the application or the VM before the snapshot, and the downtime becomes the copy time of that VM. Between Zadara regions, replication keeps a standby up to date for shorter windows.
Which operating systems are supported?
Linux and Windows. Disks are copied block by block, so the system moves as it is. Linux VMs from Azure are adapted automatically. For Windows, check the destination's drivers before the cutover.
Does my data pass through your servers?
On Zadara ↔ Zadara and AWS ↔ Zadara routes, disks stream through the Z-Move relay over TLS, in memory, and are never written to disk. Azure routes go straight between the clouds. With a private deployment, everything stays in your infrastructure.
What happens if a migration fails?
The job log shows where and why. Workers are cleaned up and you retry from the same screen; disks already copied are reused and not billed again. The source is never touched, so a failure never puts it at risk.
Can I replicate or export instead of migrating?
Yes. Replication keeps a standby VM in another Zadara region in sync, every 30 minutes up to every 24 hours, with failover from the dashboard. Export writes a VM's disks as qcow2 or VHD to your own S3 bucket.
Demo
See a full run, from wizard to boot test.
Book a demo and follow a complete migration: wizard, pre-checks, live session, boot test and cleanup.
Or write to hello [at] zmove.click