Z-Move is an agentless multi-cloud migration platform. Move VMs and enterprise workloads between Zadara, AWS and Azure without installing a single agent.
GCP, OVH, and private infrastructure on the roadmap.
Battle-tested
Real migrations. Real production workloads.
Not a demo environment. Every number comes from live enterprise migrations.
30
Migrations completed
82
Disks transferred
100%
Success rate
5
Cloud routes active
SAP HANA
United Investment
Enterprise ERP — production
Disks transferred7 volumes
Duration253 minutes
RouteLuanda 01 → Luanda 02
Errors0
SQL Server
Angola Cables
Enterprise database cluster
Disks per instance3 volumes
Duration97 minutes
Instances migrated2
Data integrity100%
Cross-Cloud
Angola Cables
AWS → Zadara migration
SourceAWS US East (Ohio)
TargetZadara Luanda 02
Duration3 minutes 20s
TypeIntercontinental
Zadara Cloud — Events · 17-Apr-26 · +42 Items
+42 infrastructure events. Every ephemeral worker, volume, network interface, and elastic IP automatically destroyed after migration, zero residual cost, zero attack surface.
Use Cases
Every reason to move.
From cost savings to compliance, Z-Move handles the full spectrum of cloud mobility needs.
🚪
Cloud Exit
Escape hyperscaler pricing without operational pain. Move your entire stack to a more cost-effective provider with near-zero downtime.
🛡️
Disaster Recovery
Build a cross-cloud replication strategy that doesn't depend on a single vendor's availability or pricing model.
💰
Cost Optimization
Move workloads to environments with better price-performance. Pay for infrastructure that fits your actual needs, not your vendor's defaults.
🌍
Data Sovereignty
Control exactly where your data lives. Move to providers that meet your regulatory and geographic data placement requirements.
Pricing
Simple. Honest. No lock-in.
Pay only for what you move. No subscriptions, no setup fees.
Pay as you go
$0.05 / GB
For one-off migrations and teams that want full cost control.
Adjust the values below to get an instant estimate. No signup required.
Estimated cost
Based on $0.05/GB · no hidden fees
$51.20
Final cost depends on actual data transferred. Contact us for volume quotes.
Security
Security is the foundation, not an afterthought.
🔑
Encrypted credentials
All cloud credentials encrypted with Fernet. Never stored in plaintext, ever.
💨
Zero persistent compute
Ephemeral workers are destroyed after every job. No persistent attack surface remains.
👥
Role-based access
RBAC with full multi-tenant isolation. Each organization's data stays completely separate.
📋
Full audit trail
Every migration action logged with timestamps, users, and outcomes. Complete visibility.
FAQ
Common questions.
Architecture
No. Z-Move is agentless by design. Zero software is installed inside your source or target VMs at any point. Your workloads are never touched — only the cloud API layer is used.
Yes. Z-Move has successfully migrated SAP HANA in production with 7 disks in 253 minutes, and SQL Server clusters with 3 disks per instance in under 100 minutes. Enterprise workloads are a core use case.
All ephemeral workers are automatically destroyed after every migration job. There are no persistent resources, no residual costs, and no attack surface left behind. Every job starts and ends clean.
Yes. Intercontinental migrations have been tested and validated, including Angola to Brazil and AWS US East to Zadara Africa. Z-Move handles the network complexity transparently.
Z-Move charges $0.05 per GB of data transferred. There are no setup fees, no subscriptions, and no idle charges. You pay only for what you actually migrate. Enterprise volume discounts are available from 10 TB.
Yes. Enterprise customers can run Z-Move as a private deployment in their own infrastructure, including white-label options for MSPs and cloud providers. Contact us for details.
Compatibility & Platforms
Z-Move supports Zadara (ZCompute/Symphony), AWS, and Microsoft Azure as both source and target in any direction — Zadara ↔ Zadara (cross-region), Zadara ↔ AWS, and Zadara ↔ Azure. GCP, OVH, and further private cloud providers are on the roadmap.
Requirements vary by provider. For Zadara: Access Key + Secret Key. For AWS: Access Key ID + Secret Access Key. For Azure: Subscription ID, Tenant ID, Client ID, and Client Secret. All credentials are Fernet-encrypted at rest and never logged or shared.
Z-Move operates at the disk/volume level via cloud APIs, making it OS-agnostic. Windows Server, any Linux distribution, and mixed-OS environments are all fully supported — no in-guest agents or OS-level access required.
Yes. Because Z-Move works at the block/disk level through the cloud API, different OS types can be orchestrated in parallel within the same account without any special configuration or per-OS treatment.
Yes. Disks are transferred at the block level using native cloud snapshot and volume APIs. Cloud-native encryption (AWS EBS, Azure Disk Encryption) is preserved transparently. BitLocker-encrypted disks are transferred as-is and remain encrypted at the destination — the key never leaves your environment.
Process & Control
Five steps: (1) Connect — authenticate with API credentials for source and target clouds; (2) Select — choose the VM, snapshot, or disk image to migrate; (3) Launch — Z-Move provisions ephemeral worker VMs in both regions simultaneously; (4) Stream — the export worker streams disk data (sparse-aware) to the import worker, which reconstructs volumes and creates a machine image in the target; (5) Cleanup — all workers are terminated and the full job log is persisted. No SSH, no agents, no manual intervention at any step.
Duration depends on disk size and available network bandwidth between clouds. Reference times: SQL Server cluster with 3 disks — 97 minutes; SAP HANA with 7 disks in production — 253 minutes; a standard 50 GB web server — under 60 minutes. The import VM is pre-warmed in parallel with the export phase to minimize total job time.
Yes. At the resource selection step you can choose individual volumes instead of migrating all attached disks. This is useful for separating data volumes from OS disks, or when only specific storage needs to move to the target cloud.
Yes. Active jobs can be cancelled directly from the dashboard. Ephemeral workers are terminated immediately upon cancellation to prevent any residual compute charges, and the cancellation is recorded in the full audit log.
Z-Move detects the failure, terminates all ephemeral workers regardless of outcome, and persists the full error context in the job log. You can review the failure reason in the dashboard and re-launch the job from scratch. The source VM and disks are never modified — there is no data loss on failure.
Security & Compliance
No. Data is transferred directly between cloud provider APIs using ephemeral worker VMs provisioned inside your own cloud accounts. Z-Move orchestrates the process; your data never transits Z-Move's infrastructure.
Credentials are encrypted at rest using Fernet symmetric encryption. They are never logged, never transmitted outside the orchestration layer, and are used exclusively for the duration of the active job. Enterprise deployments can use short-lived IAM roles and temporary tokens for zero-persistent-credential workflows.
Yes. Every job generates a complete audit trail: who triggered it, timestamps per step, all resources provisioned and destroyed, bytes transferred, compute time, cost, and any errors — all persisted and accessible from the dashboard. Admins can also export billing events as CSV.
Yes. Z-Move uses Fernet-encrypted credential storage, JWT-based authentication (ES256 via JWKS), RBAC with three role levels (user / admin / super_admin), and multi-tenant isolation via operator scoping. Data paths go directly between cloud providers. Enterprise security reviews and compliance documentation are available on request.
Cutover & Continuity
Downtime is limited to the final cutover moment — stopping the source VM and starting the migrated instance in the target cloud. For most workloads this is under 5 minutes. The bulk of the migration (disk streaming) runs independently and does not require the source VM to be offline.
No. Z-Move only reads snapshot and volume data through the cloud API — it never modifies, restarts, or shuts down the source VM. Decommissioning the source is always a deliberate, manual action under your control.
After the job completes, the target machine image is ready to launch. You can start the VM in the target cloud, run connectivity and application health checks, and only then decommission the source. Z-Move imposes no timeout on this validation window — it is entirely under your control.
Because Z-Move never modifies the source, rollback requires no action — your source VM and all its disks remain exactly as they were. If target validation fails, simply continue running from the source. No restore process, no data recovery required.
Scale & Use Cases
Yes. Z-Move's FastAPI backend with Redis-backed job orchestration is built for concurrent migrations with no shared bottleneck. Ephemeral workers are provisioned independently per job, so parallel jobs do not contend for resources. Contact us for capacity planning on large-scale programs.
Yes. Multi-disk VMs are handled natively — disks are streamed in parallel to maximize throughput. Network interface configurations are preserved as part of the machine image rebuild in the target cloud using the target platform's equivalent networking model.
Yes. Full data center migrations involving 100+ TB have been completed using Z-Move, with parallel job scheduling, real-time status monitoring across all active jobs, and zero-agent architecture on every workload. This is the scale the platform was designed for.
Commercial & Support
Enterprise customers receive dedicated support with defined response-time SLAs, a named technical contact, and access to private deployment and white-label options. Specific SLA tiers are defined per agreement — contact us to discuss your requirements.
Yes. We offer a supported POC for enterprise customers to validate Z-Move against your specific environment before committing. Most POCs run 2–4 weeks and include a live test migration of a real production workload with a dedicated technical contact.
Yes. Z-Move exposes both a CLI and a REST API, making it fully scriptable and automatable. MSPs use it to trigger migrations programmatically; DevOps teams integrate it into deployment pipelines for cloud mobility workflows. Contact us for API documentation and integration support.
Who built this
Built by someone who lived the problem.
Adilson Camenha
📍 Luanda, Angola
Principal Cloud Solutions Architect · Founder of Z-Move
I've spent years designing mission-critical cloud architectures across AWS, Azure, GCP, OCI, Zadara, and Alibaba Cloud, for enterprises operating in Angola, Nigeria, Mauritius, and Brazil. I've run complex migrations of over 100TB, led SAP critical environments, and watched every existing tool fail in the same way: agents that break, processes that don't scale, and zero real multi-cloud support.
Z-Move is the tool I built to solve that. Agentless by design, ephemeral by architecture, genuinely cloud-agnostic. Every migration in the proof section above is real | Angola Cables, United Investment, and BPC Safira trusted it with their production workloads. It delivered.
