Phases and typical durations
These ranges reflect our completed engagements and assume your team can dedicate time to the migration.
- Briefing and planning. Two to four weeks, including the control responsibility matrix and network plan.
- Capacity and provisioning. Two to six weeks, depending on capacity year and hardware profile.
- First workload migration. Four to eight weeks. The first migration takes longer because this is where dependencies are identified.
- Subsequent workloads. One to three weeks each, once the process is established.
- Decommissioning the original environment. One to two weeks after the final migration, plus any period required by your retention policy.
Steps that often take longer
First, identifying outbound dependencies. Teams often underestimate how many outbound destinations an established workload uses, particularly where outbound traffic was previously unrestricted. Allow sufficient time, and complete this work while the original environment is still running.
Second, collecting evidence for your assessor. If your authorization must be updated to reflect the new hosting environment, the timing depends on your assessor's schedule. Begin that conversation during planning rather than at migration.
If a specific date drives your program, such as a contract option or an authorization expiry, let us know during the briefing so we can schedule capacity accordingly.