Migration guides

Leave AWS or VMware with a plan you can read first.

Each guide maps the services you run today to the Optidata product that replaces them, walks through assessment, data transfer, cutover and validation, and prices an example stack.

The guides

Start from where your workloads run today.

Self-serve Optidata runs in Miami (US1). Workloads that must keep data in Brazil, or that need dedicated hosts or SQL Server, land on Private Cloud. Both guides say which is which.

Updated October 1, 2026

Migrate from AWS to Optidata

How to move from AWS to Optidata Cloud: EC2, EBS, S3, EKS, RDS, ELB and Route 53 mapped to Optidata products, a five-step plan, and a monthly cost example at list prices.

  • EC2
  • EBS
  • S3
  • EKS
  • RDS
  • ELB
  • Route 53
Read the AWS guide
Updated October 1, 2026

Migrate from VMware to Optidata

Moving off VMware vSphere: where VMs, vSAN datastores, NSX networks and vCenter land on Optidata Cloud Compute or Private Cloud, a five-step plan and a monthly cost example.

  • vSphere VMs
  • vSAN
  • NSX
  • vCenter
  • Windows and SQL Server
Read the VMware guide

Next steps

Rather not run it yourself?

The guides are the plan. The migration service is the team that executes it, and the comparisons are the numbers to check before you commit.

Have Optidata run the move

Assessment, migration plan, cutover inside an approved window, and post-migration support, executed by Optidata engineers.

See the migration service

Compare before you move

Optidata against AWS, Google Cloud, Oracle, DigitalOcean, Vultr and Magalu, plan for plan at list price.

Open the comparisons