A guide to moving from VMware to a cloud-native cloud

Many companies have run their business on virtual servers in VMware or Hyper-V for years. These environments work, but they hit limits when it comes to the flexibility, automation and cost model that SaaS products need. In this post we walk through moving from traditional virtualization to a cloud-native cloud platform, step by step.

Traditional versus cloud-native applications

Our infrastructure partner RNG Technology sums up the difference between the two approaches like this:

• In the traditional approach, systems are installed by hand, processes depend on individuals and every environment is rebuilt manually. Capacity is planned as a fixed amount, and growing demand requires manual intervention. Traffic balancing needs separate physical appliances or software.
• In the cloud-native approach, infrastructure is defined as code and becomes repeatable and automated. Resources scale up and down with traffic automatically. The load balancer is built into the platform, with no extra hardware or licenses.

What changes when you move to Edge Cloud

• You manage resources yourself through a user-friendly interface and wizards.
• Virtual servers are created in seconds, and bulk deployment is possible.
• Auto-Scale, L3/L7 Load Balancer and Kubernetes live on the same platform.
• Block, file and object storage are offered on one platform.
• The resources you use are billed by the hour.
• In Türkiye regions, data stays within Türkiye.
• Infrastructure as code is supported with Terraform.

Migration methods

RNG Technology's migration approach includes several methods. Which one fits depends on the workload:

• Direct transfer with Zadara V2Z: virtual servers are moved directly from VMware or Hyper-V to Edge Cloud.
• Restore from backup: backups taken with your existing backup method are restored in the new environment.
• Hybrid migration with a new release: the new version of the application is deployed on Edge Cloud and runs alongside the old environment for a while.
• Microservice migration: container-based applications are moved to the Kubernetes service.

A step-by-step migration plan

1. Inventory and dependencies

List the servers to move, their operating systems, disk sizes and how they depend on each other. Knowing which server talks to which database or external service is the basis for deciding the migration order.

2. Design the target architecture

Plan your VPC, subnet and firewall layout on Edge Cloud. For storage, consider VPSA All Flash or VPSA Hybrid depending on the workload. Choose server profiles based on actual usage data; migration is a good opportunity to shrink servers that were oversized.

3. Set up network connectivity

During migration, the old and new environments need to reach each other. Connect them with IPSec, SSL VPN and Layer 2 or Layer 3 connectivity options.

4. Run a pilot

Start with a non-critical workload. Use the pilot to validate migration time, performance and rollback steps.

5. Migrate in waves and validate

Apply the lessons from the pilot and move workloads in groups. After each group, run application tests and collect user feedback.

6. Modernize

Once the move is complete, strengthen workloads with cloud-native capabilities: put the web tier behind Auto-Scale and a load balancer, move environment setup into Terraform, and shift suitable services to Kubernetes.

Common mistakes

• Moving everything at once: large one-shot migrations make it hard to find the cause when something breaks. Move in waves.
• Copying sizes as they are: server sizes in the old environment are often above real usage. Use the migration to pick profiles based on usage data.
• Skipping the rollback plan: write down how you will return to the old environment for each migration group before you start.
• Forgetting licenses: plan early how Windows Server, SQL Server and similar licenses will be covered in the new environment. These licenses are available monthly in the Bulutlan price list.
• Leaving backups for later: turn on the backup routine for each workload on the day it moves.

The hybrid period

Migration does not always finish in one go. Some workloads may stay on-premises for a while. Edge Cloud supports hybrid scenarios where VMware and Edge Cloud are used together. The Federated Edge architecture lets you manage multiple data centers from a single point. Where data has to stay on-premises, On-Premises Edge Cloud is an option, rented monthly with zero upfront investment.

Support during migration

According to RNG Technology, the migration process is run by experts: virtual servers and any microservice architectures are moved, and Layer 2 and Layer 3 connectivity is provided. At Bulutlan, we stay with you to coordinate the process from the planning stage onward. In the first meeting, we review your inventory, critical workloads and acceptable downtime windows together to choose the right migration method for you.

To discuss your migration plan, talk to one of our experts, or review Managed Virtual Server and On-Premises Cloud for the target environment.