Cloud Workload Migration
Move virtual machines from AWS EC2 or Microsoft Azure to ConnectVM using a structured, repeatable image-based migration process.
Scope
What this migration covers.
This is an image-based migration procedure for moving virtual machines from AWS EC2 and Microsoft Azure into ConnectVM compute, storage and networking.
The core flow is: Discover → Prepare → Snapshot/Export → Transfer → Convert/Repair → Import/Deploy → Validate/Cut over.
Rollout phases
Migration flow
7 stages, end to end.
Discover
Inventory source VMs, disks and networking. Map source resources to ConnectVM.
Prepare
Check OS, drivers, boot configuration and application dependencies.
Snapshot / Export
Create a consistent image of the running workload (VMDK, VHD or RAW).
Transfer
Move the image to protected ConnectVM staging with integrity verification.
Convert / Repair
Convert disk format, verify bootloader, VirtIO drivers, networking and cloud-init.
Import / Deploy
Provision destination compute, storage, network and security on ConnectVM.
Validate / Cut over
Run acceptance tests. Production traffic moves only after you approve.
Step-by-step
AWS EC2 and Azure VM — both covered.
AWS EC2 → ConnectVM
EC2 · EBS · AMI export
- 01Connect your AWS account with least-privilege permissions for discovery and export.
- 02Inventory EC2 instances, EBS volumes, subnets and security groups.
- 03Create an AMI or use an eligible instance-export workflow; export to a controlled S3 bucket.
- 04Transfer the completed export to ConnectVM staging with file size and checksum verification.
- 05Convert the image, verify bootloader, VirtIO drivers, /etc/fstab and network configuration.
- 06Provision the ConnectVM instance. Validate before cutting over DNS and traffic.
Azure VM → ConnectVM
Azure VM · Managed Disks · VHD export
- 01Connect your Azure subscription with least-privilege access.
- 02Inventory VM size, OS, managed disks, NICs, VNets and NSGs.
- 03Snapshot the OS disk and all required data disks at a consistent point.
- 04Generate a short-lived read-only SAS URL per disk and transfer to ConnectVM staging.
- 05Download each VHD, verify size and checksum, convert and prepare guest OS.
- 06Import the image, provision the instance, validate, then revoke SAS access after transfer.
Your experience
What you see at every stage.
| Step | What you see | What happens |
|---|---|---|
| Connect account | AWS / Azure authorisation | Discover and validate permissions |
| Select workloads | VM list with sizing | Build migration inventory |
| Configure | Compute, storage, network, IP | Create destination plan |
| Migrate | Live progress by stage | Export, transfer, convert, import |
| Validate | Health checks | Boot and technical checks |
| Complete | Migration completed ✓ | Cutover, audit and cleanup |
Acceptance criteria
Production traffic moves only after every item passes.
Security requirements
Built into every stage of the migration.
Ready to start your migration?
Contact us with your source cloud (AWS / Azure), number of VMs, and approximate sizing. We'll assess your workloads and plan the migration.
