All systems operational · 99.99% uptime SLA
CDP — Cloud Data Protection & Migration · Cross-account · Cross-project · Zero IP changes

Migrate
everything.
Change nothing.

NubexCloud CDP lets you move your entire cloud infrastructure — VMs, networks, storage, databases — between accounts or projects. Every IP address, resource ID, network configuration, and firewall rule arrives at the destination unchanged. Migration without reconfiguration.

10Resource types
0IP changes
0ID changes
2Migration modes
Source Account ☁ Cloud Host ID: vm-a4f2c1 IP: 10.0.1.5 💾 Cloud Disk disk-8b3a2 500 GB 🌐 Elastic IP 203.0.113.42 🔒 VPC 10.0.0.0/16 🛡 Firewall 8 rules CDP Migration VM Disk EIP Target Account ☁ Cloud Host ID: vm-a4f2c1 IP: 10.0.1.5 ✓ 💾 Cloud Disk disk-8b3a2 500 GB ✓ 🌐 Elastic IP 203.0.113.42 unchanged ✓ 🔒 VPC 10.0.0.0/16 preserved ✓ 🛡 Firewall 8 rules intact ✓ Zero IP changes Zero ID changes CDP Migration
The Migration Guarantee

Before. After. Identical.

The reason teams don't migrate is the fear of reconfiguration. CDP eliminates that fear completely. Every resource arrives at the destination with the same settings it left with — no IP updates, no DNS changes, no firewall reconfiguration needed.

IP Address
203.0.113.42
203.0.113.42
unchanged ✓
Resource ID
vm-a4f2c1d8
vm-a4f2c1d8
unchanged ✓
VPC Subnet
10.0.0.0/16
10.0.0.0/16
preserved ✓
Firewall Rules
8 rules
8 rules
intact ✓
Routing Table
12 routes
12 routes
intact ✓
Your applications, DNS records, and integrations continue working exactly as before — because from their perspective, nothing changed.
What You Get

Complete cloud environment migration — without the pain

CDP handles the migration of your entire infrastructure stack in a single operation. You don't migrate resource by resource — you migrate a complete, interconnected environment.

🏗
10
Resource types
VMs, disks, IPs, VPCs, subnets, firewalls, NAT gateways, ACLs, route tables, and databases — all migrated together.
🔀
2
Migration modes
Cross-project migration for internal restructuring. Cross-account migration for team separation, acquisition, or external transfer.
0
Reconfigurations
No IP address updates. No DNS changes. No firewall rewrites. No routing table edits. Your applications work immediately after migration.
Brief
Interruption only
There is a brief interruption during the migration window. Plan it during maintenance hours. CDP handles billing settlement and auto-renewal automatically.
What Migrates

Every layer of your infrastructure — in one operation.

CDP migrates the complete stack: compute, storage, networking, and databases. Associated resources like EIPs and disks bound to cloud hosts are migrated automatically — no unbinding required.

☁️
Cloud Host
Resource ID, internal IP address, and MAC address remain identical before and after migration.
ID · IP · MAC unchanged
💾
Cloud Disk
System and data disks — resource ID and mounting status unchanged. Migrated with their attached cloud host automatically.
ID · mount status unchanged
🖥
Local Disk
Local system and data disks — resource ID and mounting status unchanged during migration.
ID · mount status unchanged
🌐
Elastic IP
The EIP address remains the same after migration. Your DNS records and external integrations continue pointing to the same public IP.
IP address unchanged
🔒
Private Network (VPC)
VPC network segment remains the same. If the VPC was interconnected with other VPCs, re-enable the interconnect after migration.
Subnet range unchanged
📡
Subnet
Subnet segment remains identical before and after migration. All assigned IP addresses within the subnet continue working.
Subnet segment unchanged
🛡
Firewall
All firewall access rules — inbound and outbound — remain exactly the same after migration. No security policy rewrite needed.
All rules preserved
🔀
NAT Gateway
NAT gateway forwarding rules are preserved through migration. Outbound internet traffic continues routing identically.
Forwarding rules unchanged
📋
Access Control List
All ACL rules for data inflow and outflow remain the same. Network access control policies carry over without modification.
All rules unchanged
🗺
Route Table
All routing rules in route tables are preserved. Traffic between subnets and to the internet continues following the same paths.
All routes unchanged
🗄
Cloud Database (MySQL)
Cloud databases on NVMe and CLOUD_SSD models can be migrated. Requirements: not expired, backup to Object Storage not enabled at migration time, Proxy mode not active. Routing table rules remain the same after migration.
NVMe · CLOUD_SSD Routing rules preserved
Migration Modes

Two paths. One tool.

CDP supports two distinct migration scenarios — from an internal project restructure to a full account transfer. Both preserve all resource settings identically.

Mode 01

Cross-Project Migration

Move resources between projects within the same cloud account. Use this to restructure how your infrastructure is organised — separating environments, regrouping resources by team, or consolidating legacy projects — without any changes to the resources themselves.

Typical scenarios
Separating staging and production environments into dedicated projects
Regrouping resources by product line or business unit after an internal restructure
Consolidating legacy projects into a unified infrastructure project
Mode 02

Cross-Account Migration

Transfer resources from one NubexCloud account to a completely different account. The source account's resources move to the target account — IPs, IDs, and configurations intact — and the source account is automatically settled. Used for business acquisitions, team spin-offs, client handovers, and vendor transfers.

Typical scenarios
Business acquisition — consolidate acquired company's cloud into your main account
Team spin-off — give a newly independent team full ownership of their resources
Client handover — transfer infrastructure built for a client into their own NubexCloud account
How It Works

Four steps. No surprises.

CDP handles the complexity of a multi-resource migration automatically. You initiate the transfer — CDP does the work, including billing settlement, auto-renewal, and resource transfer.

1
Verify prerequisites
Confirm account status, real-name authentication, and sufficient balance for the target account. Check that all resources to be migrated have not expired and meet the migration requirements for their type.
2
Initiate migration in console
Select the resources to migrate and the destination (project or account). CDP automatically includes associated resources — EIPs and disks bound to cloud hosts migrate together without manual unbinding.
3
Brief interruption — migration executes
Resources experience a brief interruption while migrating. CDP handles the transfer, maintains all IDs and configurations, settles the source account's used costs, and refunds unused prepaid amounts automatically.
4
Done — verify and resume
Resources are now live in the target account with all settings preserved. Auto-renewal is activated on the target account for one cycle. Verify connectivity and resume normal operations — no reconfiguration needed.
Migration timeline
Before
Source account · all resources active
IPs, IDs, configs in original account
Billing: source account
↓ Migration initiated
During (brief interruption)
Resources transfer between accounts
Billing settled, refunds issued
Auto-renewal activated on target
↓ Migration complete
After
Target account · all resources active
Same IPs, IDs, configs as before
No reconfiguration needed
Migration Checklist

Five things to verify before you begin.

The migration process runs automatically, but a few preconditions must be in place. Review these before initiating — most take seconds to confirm.

Account status and real-name authentication
The cloud account receiving the resources must be in normal status with real-name verification complete. Accounts under suspension cannot receive migrated resources.
Sufficient balance in the target account
CDP auto-renews migrated resources for one cycle in the target account immediately after migration. Ensure the target account has sufficient balance to cover this renewal.
Resources have not expired
Resources to be migrated must be within their active period. Expired resources cannot be migrated — renew them before initiating the migration if needed.
Sufficient resource quotas in target
The target account must have sufficient quota for all resource types being migrated — particularly EIP quotas. Check and request quota increases if needed before migration.
Cloud host requirements met
Hosts to be migrated must: not have disk encryption enabled, not have Data Ark activated, not be bound to a Load Balancer, not be of Big Data D type, and not be in a private area.
Plan for the brief interruption window
Resources experience a brief interruption during migration. Schedule the migration during a maintenance window to minimise impact on your users and services.
CDP handles automatically — no action needed from you:
Billing settlement for used resources on source
Refund of unused prepaid amounts
Auto-renewal for one cycle on target
Transfer of associated resources (EIPs, disks)
Use Cases

When teams turn to CDP Migration

From startup scale-ups to enterprise acquisitions — CDP handles every migration scenario where cloud resources need to move without disruption.

Business Acquisition · Cross-Account

Acquired company. Migrated in one weekend.

A regional technology company acquired a smaller SaaS startup. The startup ran 12 cloud hosts, 24 disks, 4 databases, and a complete VPC network — all on NubexCloud. Instead of rebuilding the infrastructure from scratch in the acquiring company's account, they used CDP to migrate the entire environment over one weekend. The startup's cloud infrastructure — with all its IP addresses, internal routing, and database configurations — arrived in the acquirer's account unchanged. Their customers never noticed a thing.

12 cloud hosts 24 disks 4 databases 1 weekend
Technology company · UAE · Cross-account migration
0
IP changes needed
Infrastructure Restructure · Cross-Project

From one giant project to four clean ones

A fast-growing SaaS company had everything — production, staging, QA, and internal tools — in a single NubexCloud project. CDP moved each environment to its own project with correct ownership and billing. Internal IPs didn't change. The team rebooted their staging environment one morning and everything worked.

SaaS company · GCC · Cross-project migration
Team Spin-Off · Cross-Account

Two founders. One account. Then separately.

Two co-founders split into independent companies. Both had been running on a shared NubexCloud account. CDP transferred one founder's resources — VMs, databases, VPCs — to a new account they owned. No IP reconfiguration, no service outage beyond the migration window.

Technology startup · MENA · Cross-account migration
Global Network

A truly global infrastructure for fast, reliable service delivery.

26
Regions
33
Availability Zones
25ms
Regional latency
99.95%
SLA uptime
Active region
Hub region (Dubai HQ)
Backbone link
Customer Stories

Real migrations. Real results.

Cross-Account · Acquisition · UAE
We migrated 32 VMs and their entire network configuration across accounts. Not a single IP address changed. Our DevOps team expected a week of reconfiguration work — CDP completed the entire transfer in one scheduled maintenance window. Everything came up and worked immediately.
Head of Engineering · Acquired SaaS company · Dubai
32
VMs migrated · 0 IPs changed
Cross-Project · Restructure · KSA
Moving eight environments from one chaotic project into eight organised ones would have taken our platform team a month of careful work. With CDP, we did it in three migration windows over a long weekend. The network segments, firewall rules, and routing tables all arrived exactly as configured.
Platform Lead · Technology company · Riyadh
8
Environments · 1 weekend
Cross-Account · Client Handover · Egypt
We build and operate cloud infrastructure for clients, then hand over ownership. Previously this meant rebuilding the client's environment in their account from scratch — a week of work per client. Now we use CDP to transfer. The client receives their infrastructure exactly as we built it. Their IPs, their firewall rules, their VPC — all there.
Infrastructure Director · Cloud services agency · Cairo
0
Hours of rebuild work per client
Trusted by teams across the region
Falcon AITradeSparkMasaarNEXAGENSalam DigitalOrbita
FAQ

Common questions about CDP Migration

Ready to migrate?

Migrate everything.
Change nothing.

Move your entire cloud environment — VMs, networks, storage, databases — between accounts or projects. Same IPs. Same IDs. Same everything. Zero reconfiguration.

Start Migration → Read the Docs
10
Resource types
0
IP changes
2
Migration modes
Brief
Interruption only