Common reasons for a cloud migration are aging hardware, the end of support for an operating system, a new site or the wish to work from anywhere. A migration is more than a technical move. It changes the cost structure, responsibilities and often workflows as well: instead of investing in your own hardware, you have ongoing costs, and part of the operations lies with the provider.
How a cloud migration works
- Inventory: Which servers, applications, data volumes, interfaces and licenses exist, and which systems depend on each other.
- Strategy per application: The options are often described as R strategies. An application can move unchanged (rehost, also known as lift and shift), switch to platform services with minor adjustments (replatform), be redeveloped (refactor), be replaced by a software-as-a-service solution (repurchase), stay on-premises for now (retain) or be shut down (retire).
- Prepare the target environment: Identities, network, security rules, monitoring and backup are set up before the first systems move.
- Migrate in stages: After a pilot, the remaining systems follow in planned waves, each with testing and a fallback plan. Large data volumes are transferred in advance and only synchronized shortly before the switchover.
- Optimization: After the move, sizes, costs and operating procedures are adjusted to actual usage.
The entry IaaS, PaaS and SaaS explains which service model fits in each case.
Typical examples
- Network drives move from the file server to SharePoint and OneDrive.
- The company's own Exchange server is replaced by Exchange Online.
- A line-of-business application moves as a virtual machine to a cloud provider's data center.
- Self-hosted software is replaced by the vendor's cloud solution.
What companies should keep in mind
- Check the internet connection: After the migration, day-to-day work depends on the line. Sufficient bandwidth and a second connection as a backup are part of the planning.
- Compare costs realistically: The cloud is not automatically cheaper. Compare ongoing costs over several years with continuing on-premises operations.
- Clarify data protection and contracts: Check the storage location, data residency and the data processing agreement (DPA) before the move.
- Rethink backup: Data in the cloud also needs a backup and an emergency plan.
- Bring employees along: Explain new storage locations and tools early and provide training.