VirtaMove Application Migration Methodology

VirtaMove uses a repeatable Field Methodology to ensure successful movement of legacy applications. Our migration methodology leverages automated migration best practices, is proven in customer production environments around the world, and is adaptable to each unique IT environment.

What does a migration flow look like?


Our migration methodology includes 4 phases for each migration, with best practices, check points, and automation at each stage to ensure timely and successful movement of apps from your legacy source servers to new target servers.

migration methodology

How long does it take?


Our productivity metrics are based on more than 5 years experience moving legacy applications for leading clients in Banking, Telecom, and Pharma around the world. The proof of our metrics are in production, not theory.

The greater the operational preparedness, flexibility, and responsiveness of the IT environment, coupled with use of migration best practices and availability of skilled app movers, the shorter the wait states and the greater the migration productivity. Each IT environment is unique: application stacks are unique, how Microsoft Server products are used, maintained, secured, and hardened is never the same from one environment to another. These variables also affect migration productivity. VirtaMove can help assess your unique IT thumbprint and adapt our migration methodology to your environment.

Generally, app movers become more skilled over time.

Productivity estimates, using VirtaMove Migration Intelligence

In 1 week…
→ One experienced Application Mover can move approx. 2 servers.

In 1 month…
→ One experienced App Mover can move approx. 8-10 servers into production.

In 1 year…
→ One experienced App Mover can move 100 servers.
→ If you have 400-500 servers to move and migrate, you’ll need 4-5 App Movers for one year.

VirtaMove Methodology

Migration productivity: VirtaMove vs alternative, traditional methods


Stateful re-install using VirtaMove Migration Intelligence Suite :
2 servers per week

Vs. alternative, tradition migration methods:

Hand migration and new install of the same application stack on a modern server:
2-3 months per server

Application stack re-development, remediation, and re-licensing:
More than 6 months per server

Traditional migration methods, like manual migration, take too long, cost too much, and require too many internal resources.

Using automated migration software to move applications from legacy Windows Servers will save over 80% of the time and over 70% of the cost compared to traditional manual migration or app re-development efforts.

How do you maintain application migration productivity?

Productivity of 2 server migrations per week doesn’t mean that a migration will be completed in 2.5 days. While some migrations may take a couple of days, many take 2 or 3 weeks to complete because of unavoidable operational wait states.


Maintaining migration productivity is achieved with multitasking: working on many migrations at once.

If the average migration completion time is 3 weeks…
→ An Application Mover will need to work on 6 simultaneous migrations to achieve 2 migrations per week.

If the average migration completion time is 2 weeks…
→ An Application Mover will need to work on only 4 simultaneous migrations to achieve 2 migrations per week.

Factors that affect application migration productivity


Many factors impact application migration productivity. The more operationally nimble an organization is, the shorter the wait states. Shorter and fewer wait states lead to greater migration productivity and less time and lower cost for each server migration. An adaptable operations team can support approximately 10 server migrations per application mover per month; a less adaptable team may only support 2-3 server migrations per application mover per month.

Productivity factors include:

  • The OS version of the source legacy Windows server and new target server
  • The number and nature of the applications on each legacy server
  • Commonality between applications
  • Knowledge about each application
  • Application licensing and security requirements
  • The amount of data
  • The dependency between applications on each server, and the tiered dependency between applications that work across many servers
  • Available network bandwidth
  • The sizing and provisioning of target servers
  • The hardening process and security standards on the target servers
  • The availability of skilled users for acceptance testing
  • The response rate and adaptability of the operations team when wait states happen
  • The production cut-over process and the server decommissioning process

How much does it cost?