1. Name the business outcome
Describe why the organization is changing now and what improved operation should look like: easier collaboration, support for new locations, retirement of aging infrastructure, more dependable access, clearer recovery, simpler administration, or another specific result. Define how the outcome will be observed.
2. Discover the application and data estate
Inventory applications, owners, users, data, interfaces, authentication, infrastructure, performance needs, retention, backup, support, costs, and lifecycle status. Classify what can move, what must change first, what may remain, and what can be retired.
3. Map identity, access, security, and obligations
Define authoritative identity, joiner-mover-leaver processes, privileged access, device assumptions, logging, data handling, provider responsibilities, and incident procedures. Requirements vary by organization and workload; a migration does not by itself guarantee security or compliance.
4. Test network, integration, and recovery assumptions
Confirm capacity, latency, name resolution, remote and site access, integrations, data movement, backup, restore, continuity, and rollback. Test the riskiest assumptions before broad rollout and document acceptance criteria for critical workflows.
5. Model total cost and operating ownership
Include subscription or consumption charges, implementation, migration, integration, security, network changes, training, internal labor, support, backup, compliance-related work, growth, and exit costs. Define who will monitor usage, approve changes, manage licensing, coordinate support, and optimize the environment.
6. Plan adoption and staged change
Identify how each role will work differently, what training and communication are needed, how exceptions will be handled, and where questions will go. Use pilots and rollout waves that expose real workflows without placing the whole operation at risk.
Frequently asked
Questions this guide should not leave vague
Does everything need to move to the cloud?
No. The appropriate target may be cloud, on-premises, colocation, SaaS, hybrid, or a phased combination based on the workload and business requirements.
Can AMD help compare Microsoft 365, Google Workspace, infrastructure, or other options?
AMD can help assess needs, compare applicable options, coordinate migration and implementation, and support the environment after launch. The shortlist depends on the organization’s requirements.