First Mover

In cloud migration, a first mover is a workload selected for an early move, with attention to what the team can learn at acceptable risk. The term here is distinct from market first-mover advantage. Google’s assessment guide recommends candidates that teach patterns useful elsewhere in the estate. AWS’s discovery guidance gives three to five initial candidates as an example; its portfolio overview describes early migrations as opportunities to gain experience and establish cloud foundations. Candidate count is not a fixed rule.

The criteria

Compare learning value with the consequences of failure. Google favors less critical, representative workloads that are used often enough for problems to be observed, with manageable or loosely coupled dependencies, little refactoring, and fewer licensing or compliance constraints. These preferences reduce competing sources of difficulty while the team learns. Stateless candidates can simplify local data transfer, but their external stateful dependencies still need checking. A motivated team also needs sponsorship, clear learning goals, capacity, and an acceptable recovery plan. An unusual workload may teach useful lessons about access or operations even if its application pattern is not reusable. Document why an exception is justified and what learning can transfer, rather than treating every criterion as part of the term’s definition.

A fictional hospital initially chose its pharmacy system partly for its importance and an eager team, but missed a batch consumer that broke after the move. After that failure, the first wave of its revised plan used a staging environment and two internal reporting services. Five weeks of work produced migrated workloads, test results, a runbook, and a list of unresolved questions. Six later waves reused the runbook as a starting point and repeated checks for their own scale, data, interfaces, and failure modes. A first mover is a candidate workload; a migration wave is a coordinated group that may contain several candidates. Early success supports a procedure within the tested conditions, not a guarantee for the rest of the estate. The assessment supporting that choice is explained in The Inventory Said Two Hundred Systems and the Network Said Three Hundred and Forty.

References:

• Google Cloud Architecture Center, Migrate to Google Cloud: Assess and discover your workloads, last reviewed 2 August 2024 (CC BY 4.0).
• AWS Prescriptive Guidance, Application portfolio assessment guide for AWS Cloud migration.
• AWS Prescriptive Guidance, Discovery acceleration and initial planning.