M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Migration factory

Concept

A migration factory is a repeatable delivery model for large cloud migrations that moves workloads in waves using shared standards, runbooks, validation gates and rollback patterns instead of one-off projects.

✦ CONCEPTMigration factoryM365.FM
Title graphic: Migration factory (Concept)

Also discussed

The episode about Migration factory also covers Cloud Center of Excellence, Rehost (lift and shift), Azure Virtual WAN, Hub-and-spoke network topology, Identity drift and Subscription vending.

Description

A migration factory is a repeatable delivery model for large cloud migrations. Instead of treating each move as a one-off project, it moves workloads in waves and applies shared standards, runbooks, validation gates and rollback patterns to every wave. The idea is to turn migration into a production line: the same steps are executed in the same order, so effort, risk and duration become more predictable as the number of workloads grows.

The model is typically considered when an organization has many applications or servers to move and cannot afford to design the approach from scratch each time. Standardization is the central element. Runbooks describe the individual tasks, validation gates define what must be true before a workload advances to the next stage, and rollback patterns define how to return to a known state if a step fails. Because these artifacts are reused, lessons from earlier waves feed directly into later ones.

A concrete example of the concept is described in AWS Prescriptive Guidance for the Cloud Migration Factory solution, which automates large-scale server migrations to AWS. That page covers one vendor's implementation rather than the generic term, but it illustrates how a factory can be structured. The workflow has three phases. In pre-migration, the team prepares the implementation environment by deploying the factory, building a migration execution server and setting up the migration tooling. In migration implementation, predefined tasks automate the work: verifying prerequisites, pushing the replication agent to the source machines of a wave, checking replication status, launching servers for boot-up testing and scheduling a window for application cutover. Post-migration tasks depend on the scenario and may include removing servers from the source configuration database, decommissioning source machines and tuning performance on the target instances.

Waves are the unit of organization in this example. A wave is a group of applications and servers that share the same cutover date. The documented example schedule is a three-week cycle: a build stage in week one, validation and boot-up testing in week two, and cutover in week three. All waves run in parallel, so several groups can be in different stages at the same time. This overlap is what allows throughput to scale without restarting the process for each group.

The M365.FM episode "Move Legacy Systems to Azure Without Disrupting Work" places the migration factory inside a wider sequence. The episode argues for an order of platform first, then a repeatable migration factory, then modernization that compounds instead of fragments. It says that every exception approved during migration becomes permanent debt and that governance throughput can collapse quickly, which is why policy, networking, logging and subscription boundaries need to be settled before waves begin. According to the episode, cloud success is less about where workloads run and more about whether the enterprise can change safely, predictably and under control. It also notes that many organizations underestimate costs and overlook application dependencies when planning an enterprise migration strategy.

In practice, decisions around a migration factory include how to define waves, which validation gates are mandatory, who approves exceptions, and how rollback is rehearsed before cutover. The factory approach does not remove the need to assess individual applications, but it separates the repeatable mechanics of moving workloads from the case-by-case decisions about how each one should eventually be modernized.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept

Episodes about Migration factory

Episodes in which Migration factory is discussed:

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What is a migration factory? (AI)

A migration factory is a repeatable delivery model for large cloud migrations. It moves workloads in waves and relies on shared standards, runbooks, validation gates and rollback patterns instead of one-off projects.

What is a wave in a migration factory? (AI)

In the AWS Cloud Migration Factory example, a wave is a group of applications and servers that share the same cutover date. The example schedule runs a three-week cycle of build, validation and cutover, with waves running in parallel.

What does the M365.FM episode recommend about the order of work? (AI)

The episode "Move Legacy Systems to Azure Without Disrupting Work" recommends platform first, then a repeatable migration factory, then modernization. It warns that exceptions approved during migration become permanent debt.

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: