On-Premises to Cloud Migration: A Step-by-Step Blueprint

On-Premises to Cloud Migration

Moving from on-premises servers to the cloud can cut maintenance and add flexibility, but a rushed migration often costs more and performs worse than what you had. The best migrations are planned workload by workload, with a clear reason for each move, and many businesses end up with a hybrid setup rather than moving everything.

Quick answer: assess every workload, decide for each one whether to rehost, replatform, refactor, replace, retire or retain it on premises, estimate cloud running costs before moving, migrate in waves starting with low-risk systems, test thoroughly, and keep a rollback path. Steady, data-heavy workloads are often cheaper to keep on your own servers.

The migration strategies

StrategyWhat it meansBest for
Rehost (“lift and shift”)Move the VM or server as-is to the cloudQuick moves with little change
ReplatformSmall changes, such as moving a database to a managed serviceReducing admin effort
RefactorRe-architect the application for cloud servicesApplications that need to scale
RepurchaseReplace with a SaaS productEmail, CRM, collaboration
RetireSwitch it offSystems no longer needed
RetainKeep it on premisesSteady, data-heavy or latency-sensitive workloads
Selecting the Right Cloud Model

Step by step

  1. Inventory and assess: list servers, applications, dependencies, data sizes and usage patterns.
  2. Choose a model: public, private or hybrid cloud, and the strategy per workload.
  3. Estimate costs: compute, storage, bandwidth (especially outbound data), licences and support, compared with running on premises.
  4. Plan connectivity and identity: VPN or dedicated links, single sign-on and security controls.
  5. Migrate in waves: start with low-risk systems, learn, then move critical ones.
  6. Test and cut over: test with real users, schedule cut-over, keep the old system available for rollback.
  7. Optimise: right-size instances, switch off unused resources and review bills monthly.
Watch out: cloud costs scale with use, and data transfer out of the cloud is often charged. Model costs for a full month of real usage before migrating, and set budget alerts from day one.
Pro tip: check where your provider will store personal information. Under POPIA, moving data outside South Africa is a cross-border transfer that must meet section 72 conditions. See our guide to data privacy regulations in South Africa.

When to keep workloads on premises

  • Large file shares and databases used all day by local staff.
  • Systems that must keep working when the internet link is down.
  • Workloads with steady, predictable demand, where owning hardware is cheaper over several years.
  • Data with strict residency or control requirements.
Good to know: many businesses settle on hybrid IT: SaaS for email and collaboration, cloud for variable workloads, and refurbished servers on site for steady ones. Read hybrid IT with refurbished servers.

Frequently asked questions

What is the first step in a cloud migration?

An inventory and assessment of every workload, its dependencies, data and usage, so you can choose the right strategy for each.

Is moving to the cloud always cheaper?

No. Variable or short-lived workloads are often cheaper in the cloud, while steady workloads can be cheaper on your own hardware over time.

What is lift and shift?

Rehosting a server or virtual machine in the cloud with minimal changes. It is fast but may not reduce costs or admin.

Can I move back from the cloud to on premises?

Yes. Some organisations repatriate workloads when costs or performance favour their own hardware, which is easier if applications were kept portable.

Keeping some workloads in house? Configure a refurbished server or talk to our team.

Server Site