Migrate from VMware to Optidata

VMware workloads move to Optidata in one of two ways. VMs that fit standard sizes move to Cloud Compute, self-serve in Miami (US1) and priced per plan. Estates that need dedicated hosts, data kept in Brazil, SQL Server or a managed ERP move to Optidata Private Cloud, in Optidata-owned data centers in Brazil and the United States.

Either way, Optidata engineers can run the move: assessment, migration plan, replication, cutover inside a window you approve, and validation before sign-off.

Each vSphere building block and the Optidata product that takes its place. The assessment confirms the mapping for every VM and every feature you rely on.

• The assessment lists the vCenter and NSX features you rely on, each with its Optidata equivalent or a plain statement that there is none.
• The self-serve platform runs in one region, Miami (US1). Workloads that must stay in Brazil go to Private Cloud.
• Oracle is not offered as a managed database.

The same method Optidata engineers use on every migration. Each stage ends with something you can read and approve before the next one starts.

Assessment

Inventory what runs today: VMs with their vCPU, RAM, disks, operating systems and licences, the dependencies between them, port groups and NSX segments, firewall rules, and which workloads need dedicated hosts or data in Brazil. Map every item with the table above and price the target in the calculator before deciding anything.

Optidata engineers can run the assessment with you. You get a map of what you run today and what it will cost to run on Optidata, before any commitment.

Migration plan

A named architect designs the target architecture, the move sequence, the rollback plan and the cutover window. Nothing moves until you have read and approved it.

Data transfer

Data is replicated to the target ahead of the cutover and kept in sync, so the final switch is short. How each VM is carried over, moved as an image or rebuilt with its data copied, is decided per workload in the migration plan.

Cutover

Inside the window you approved: final sync, the DNS change, and traffic moving to the new environment. Because data was replicated ahead of time, the window covers the final switch only, usually minutes to a few hours rather than days.

Rollback stays armed until you sign off on the new environment.

Validation and sign-off

Integrity is verified on both sides, the application is tested against the new environment, and the source stays untouched until you sign off.

The migration ends when the workload is stable in production, not when the cutover finishes: the same team stays after go-live for monitoring and tuning, with the NOC and SOC on shift 24/7.

A small vSphere cluster moved to Cloud Compute in Miami (US1): 3 application VMs and one database VM, each with OPTI-FLASH-NVME block storage and a backup schedule, behind one load balancer. Linux, Optidata list prices from the console catalog of September 22, 2026.

• Outbound traffic is included in every plan; past the allowance it bills per GB at the rate on the price list.
• Backup storage is approximated by the attached disk size, as the calculator does. What you actually store depends on retention and change rate.
• Windows Server adds a per-vCPU licence. Dedicated hosts, data in Brazil and SQL Server are Private Cloud, priced with an architect.

Your stack will differ. Price it in the calculator, which uses the same catalog as the console, or read every rate on the price list.

Can Optidata replace VMware vSphere?

For running the workloads, yes: VMs move to Cloud Compute or to Private Cloud, with block storage, private networks, firewall rules and load balancers as platform products. The assessment lists every vSphere feature you rely on and names its Optidata equivalent, or says plainly where there is none.

Do I have to change my applications to leave VMware?

In most cases, no. Workloads rehost onto Optidata compute, storage and networks without code changes, and the migration plan covers anything that needs a different approach.

Where will my VMs run after the migration?

Self-serve Cloud Compute runs in Miami (US1). Private Cloud runs in Optidata-owned data centers in Brazil and the United States, which is the option for data that must stay in Brazil.

How much downtime does moving off VMware cause?

Minutes to a few hours, inside a window you approve. Data is replicated and kept in sync ahead of the cutover, so the window covers the final switch only, and rollback stays armed until you sign off.

What happens to Windows Server and SQL Server licences?

On Cloud Compute, the Windows Server licence is billed per vCPU on the Optidata monthly bill. SQL Server runs on Optidata Private Cloud, with licensing on the monthly bill.

Who runs the migration?

Optidata engineers, if you want them to: assessment, migration plan, cutover inside an approved window, and post-migration support. You can also rebuild standard workloads on Cloud Compute yourself from the console.