the number of workloads, and how many need more than lift and shift;

Cloud migration services for South African organisations
Cloud migration is the planned move of applications, data and servers from on-premises infrastructure, or from another cloud, to a cloud platform. Arke Technologies plans and runs cloud migrations for mid-sized and large organisations, public-sector bodies and schools across South Africa from Johannesburg: assessment, strategy, wave-by-wave cutover, security and handover, under one contract.
What is cloud migration?
By definition, cloud migration moves a workload (an application, a database, a file store, email or a whole server) onto infrastructure or software rented from a cloud platform. The platform runs the hardware; how much of the stack you still manage depends on where the workload lands: virtual machines, a managed service or a SaaS product. The migration is a project with an end date; running the estate afterwards belongs to our wider cloud services.
Cloud workload migration is rarely all or nothing: estates move in waves, and some systems rightly stay on site (see the project example below). Data cloud migration is usually the largest single task, run with the discipline of our data migration work.

Types of cloud migration
Types of cloud migration describe the direction of the move; the 7Rs below decide what happens to each workload. Most buyers mean on-prem to cloud migration (also written onprem), but enterprise estates usually combine several of these five.
| Type | What moves | Typical example |
|---|---|---|
| On-premises to cloud | Servers, applications and data leave your server room | A file server and a finance database move to Microsoft Azure |
| Cloud to cloud | Workloads move between platforms or tenancies | A Google Cloud project moves to AWS, or two Microsoft 365 tenancies merge after an acquisition |
| Hybrid | Some workloads move; others stay, linked securely | Email and files in the cloud; a latency-sensitive system on site |
| Cloud to on-premises (reverse migration) | Workloads come back from the cloud | A steady, heavy workload that costs less on owned hardware or in colocation |
| Application to SaaS | An installed application is replaced by a subscription service | Exchange Server to Microsoft 365; file shares to SharePoint or Google Drive |
Websites and mailboxes on an old hosting server move under website and email hosting.

The 6 R's of cloud migration, and the 7Rs
The 6 R's of cloud migration (also written 6 Rs or 6Rs) are the standard way to decide what happens to each workload. The model began as Gartner's five R's, AWS adapted it into six, and the 7Rs add relocate. Some vendors call them cloud migration patterns, methods or approaches; the decisions are the same.
| Strategy | Also called | What happens | When it fits |
|---|---|---|---|
| Rehost | Lift and shift | The server moves as it is, onto cloud virtual machines | A fast exit from a server room or an expiring contract; a first step before optimising |
| Replatform | Lift and reshape | Small changes, such as moving a database to a managed database service | Workloads that gain from managed services without a rewrite |
| Refactor | Re-architect | The application is rebuilt on cloud-native services | Systems that must scale, or that hold the business back as they are |
| Repurchase | Drop and shop | The application is replaced with a SaaS product | Email, files, CRM and other commodity systems |
| Retire | Decommission | It is switched off | Applications nobody uses, found during the assessment |
| Retain | Revisit later | It stays where it is, for now | Systems with licensing, latency, regulatory or end-of-life reasons to stay |
| Relocate (the seventh R) | Hypervisor-level move | Virtual machines move, unchanged, from your VMware environment to a cloud-hosted one | Large VMware estates that must leave a server room quickly without reworking each server |
In cloud migration planning, the 7Rs turn a broad ambition into one decision per workload that can be costed and signed off. Lift and shift is quickest and most often blamed for high bills, because servers sized for an office move unchanged. Refactoring costs most up front, so we reserve it, through our legacy system modernisation work, for applications that justify it.
How to choose a cloud migration strategy
Different cloud migration strategies suit different workloads. Planning cloud migration starts wide: a breadth analysis looks at every workload, then a depth analysis examines the critical ones. The main cloud migration considerations are:
Remaining life. A system due for replacement next year is a retire or repurchase candidate.
Dependencies. What each application talks to, and what breaks if they are separated.
Data volume and line speed. These set how long replication takes.
Licensing. Which licences transfer, and which do not.
Compliance. POPIA, regulator rules and client contracts that say where data may live.
Deadlines. A lease ending or a server near the end of support.
Cloud migration benefits, and when companies move back
Companies moving to the cloud usually want these benefits, none of them automatic:
Capacity on demand. Add servers or storage in minutes and pay for what runs, instead of buying for peak years ahead.
Resilience. Workloads leave an office server room exposed to load-shedding for a region with its own power and cooling; see backup and disaster recovery.
A stronger security baseline. Identity, encryption and logging are built into the platform.
When a steady workload costs more to rent than to own, a cloud to on-premises migration makes sense: we design private cloud and virtualisation or place your equipment in a South African colocation data centre.
Choosing the cloud migration platform
Microsoft Azure, AWS and Google Cloud all run South African regions, which helps with latency and data residency. We work across all three; the platforms we build, such as ISOcore, run on Google Cloud, and we run our own servers in Johannesburg.
| Platform | Usually fits | South African regions |
|---|---|---|
| Microsoft Azure | Organisations standardised on Microsoft 365, Entra ID, Windows Server and SQL Server | Johannesburg, with Cape Town as its paired region |
| Amazon Web Services | Teams already building on AWS; a broad catalogue of services | Cape Town |
| Google Cloud | Data and analytics (BigQuery), AI through Vertex AI, containers and serverless (Cloud Run) | Johannesburg |
| Private cloud or colocation | Steady workloads; data that must stay on hardware you control | Your server room or a South African colocation facility |
More on Microsoft Azure, AWS and Google Cloud. We run cloud migrations for organisations across South Africa, and take engagements beyond it, scoped and quoted per project.
Our cloud migration process in 7 steps
Our cloud migration framework runs as a life cycle of seven steps. Each ends in a decision you sign off before the next begins, so every stage of the cloud migration journey has an owner and a record.
01.
Discovery
We inventory servers, applications, data, licences and integrations, using cloud migration assessment tools such as Azure Migrate alongside interviews with system owners and users.
02.
Assessment
Each workload is checked for dependencies, performance, data volume, compliance and licensing.
03.
Strategy and business case
One of the 7Rs per workload, a target platform, and a costed case covering run cost, project cost and dual running.
04.
Target architecture and security
The landing zone (identity, networking, encryption, logging, backup and cost controls) is built first and recorded in a cloud migration architecture diagram.
05.
Wave planning and roadmap
Cloud migration wave planning groups dependent workloads and orders the waves from low risk to high, with dates, owners and change windows.
06.
Pilot and migration waves
A pilot proves the method. Each wave then moves with cloud migration automation: replication copies data until cutover, a rehearsed runbook drives the change, and rollback stays open until you sign off, so nobody holds their breath at cutover.
07.
Optimise and hand over
Right-sizing and budgets, then documentation and training, or a move into our managed IT services.
A cloud migration project example
This illustrative example, not a client engagement, shows how a mid-sized organisation with a small server room might apply the 6 R's across three waves.
| Workload | Strategy | Wave |
|---|---|---|
| An old intranet nobody updates | Retire | 1 |
| File shares | Repurchase: SharePoint and OneDrive | 1 |
| Exchange Server email | Repurchase: Exchange Online in Microsoft 365 | 2 |
| Finance system on SQL Server | Replatform: a managed database on Azure | 3 |
| In-house line-of-business application | Rehost now, refactor later | 3 |
| CCTV video recorder and door access | Retain on site | None |
Wave 1 builds confidence on low-risk workloads. The finance system moves last, outside month-end, on dates agreed with the finance team. Email and files follow our Microsoft 365 or Google Workspace migration method.
SAP, Oracle, Atlassian and other business applications
Business applications need their own plan, because the vendor's licensing and tooling shape the options.
- SAP. An SAP cloud migration strategy starts with the edition and licence. SAP Business One, which we administer, is usually rehosted on cloud virtual machines.
- Oracle. Oracle databases can move to Oracle Cloud Infrastructure, onto another platform, or stay put. Oracle's licensing often decides, so cost the licence position before choosing an Oracle cloud migration service.
- Atlassian. An Atlassian cloud migration moves Jira and Confluence to Atlassian's cloud with the vendor's migration assistants. A Confluence cloud migration then succeeds or fails on users, single sign-on, apps and permissions.

Cloud migration security and POPIA
Cloud migration security starts before the first byte moves.
Data encrypted in transit and at rest, with keys and access documented.
Multi-factor authentication and least-privilege access; administrator accounts named, never shared.
Logging from day one, with alerting through Microsoft Sentinel or the platform's equivalent where agreed.
Controls aligned with the CIS Controls, Cloud Security Alliance guidance and ISO/IEC 27001.
POPIA: data kept in South African regions where your policy requires it, a record of which personal information moved where, and the section 72 conditions checked before any personal information leaves the country.
Every remote session approved and logged, and everyone with access bound by confidentiality.
What does cloud migration cost?
R550–R750 ex VAT
published hourly rates for IT project work (matnet.co.za, September 2026)
The cost of cloud migration has two parts: the one-off project, quoted in writing after the assessment, and the monthly bill that follows. What drives the cloud migration cost:


data volume, line speed and integrations to re-test;

dual running, when you pay for old and new environments at once;

licences that do not transfer, and after-hours cutover windows.
A cloud migration cost calculator from Microsoft, AWS or Google estimates the target's monthly run cost. None prices the project itself, the months of dual running or exchange-rate exposure when a platform bills in US dollars, and egress fees are easy to underestimate. Our business case sets them side by side, and cloud cost optimisation keeps the run cost in check afterwards.
Last reviewed: September 2026.
Cloud migration challenges and failures, and how we prevent them
Most cloud migration failures are planning failures that surface at cutover.
| Challenge | What goes wrong | How we prevent it |
|---|---|---|
| Hidden dependencies | An application breaks because a server it relied on stayed behind | Dependency mapping in the assessment; systems that talk to each other move in the same wave |
| Data loss or corruption | Records go missing or arrive incomplete | Verified backups before cutover, reconciliation checks after, rollback kept open |
| Downtime overruns | A cutover window runs into the working day | Rehearsed runbooks, go/no-go criteria and a rollback path |
| Run-cost surprise | The first cloud bill exceeds the business case | Budgets and alerts from day one |
| Security gaps | Public storage, over-privileged accounts, no logging | A security baseline in the landing zone before any workload moves |
Governance, procurement and handover
Boards, CFOs and procurement officers need a migration governed, not just done.
A named lead and a cloud migration team. One accountable lead, the engineers doing the work, and your owner for each system, listed in the plan.
Reporting and change control. Status reports at an agreed cadence, a risk and issue log, and every cutover through change control with a recorded go/no-go decision.
Cloud migration documentation. The assessment, business case, architecture diagram, runbooks and as-built records are yours, and the roadmap doubles as a template for later waves.
Compliance. POPIA throughout; King IV Principle 12 reporting for boards; PFMA or MFMA disciplines, audit-ready records and a check against the National Data and Cloud Policy (2024) for public-sector clients.
Procurement. Arke is a Level 1 B-BBEE contributor (sworn affidavit available on request), which gives buyers 135% procurement recognition. Company documents, our CSD supplier number and tax compliance status are available on request, and you can buy by proposal and purchase order or through a tender. See supplier compliance for the public sector.
Continuity and exit. The tenancy, subscriptions and credentials are held in your name. If you move on, we hand over everything needed to run the estate without us.
How to choose a cloud migration service provider
Cloud migration companies range from the platforms' own teams to global consultancies and local cloud migration specialists such as ours. When comparing leading cloud migration service providers, ask:
Will they recommend retain or retire where it fits, or cloud for everything?
Will they show a costed business case for each workload?
Who is accountable when something breaks, and is there a rollback plan for every cutover?
Our cloud migration consulting and delivery sit with one team: the consultant who assesses your estate works beside the cloud migration experts who move it, so every cloud migration solution we recommend is one we carry out. Afterwards we can run the estate, with business fibre and LTE from Fibre Boyz and server hardware from Server Hub, both Arke divisions.
Frequently asked questions
What are cloud migration services? Show answer Hide answer
Cloud migration services are the planning and engineering work that moves an organisation's applications, data and servers to a cloud platform safely: assessment, strategy, target architecture, wave planning, cutover and handover. Our cloud application migration services come as one project under one contract, with documentation you keep and an optional managed service afterwards.
What are the 7 types of cloud migration? Show answer Hide answer
The seven types are the 7Rs of cloud migration: rehost (lift and shift), replatform, refactor, repurchase, retire, retain and relocate. The first six are the 6 R's; relocate moves VMware virtual machines to a cloud-hosted environment unchanged. Each workload gets one R, so most migrations use several, alongside a direction such as on-premises to cloud.
How long does cloud migration take? Show answer Hide answer
A small, simple estate can move in a few weeks; a complex enterprise estate moved in waves usually takes several months. The timeline depends on the number of workloads, data volume, line speed, dependencies and the change windows your business allows. We set dates in the roadmap after the assessment, not before it.
How much does cloud migration cost in South Africa? Show answer Hide answer
The migration is quoted per project after an assessment, and the cloud bill that follows depends on what you run. For market context, published hourly rates for IT project work run from about R550 to R750 ex VAT (matnet.co.za, September 2026). Budget also for dual running, licences and egress fees.
What are the big 3 cloud services? Show answer Hide answer
The big three cloud platforms are Microsoft Azure, Amazon Web Services (AWS) and Google Cloud. All three run cloud regions in South Africa: Azure in Johannesburg and Cape Town, AWS in Cape Town and Google Cloud in Johannesburg. We work across all three and choose a platform for each workload on its merits.
Does Microsoft have a migration tool? Show answer Hide answer
Yes. Azure Migrate is Microsoft's hub for discovering, assessing and moving servers, databases and web applications to Azure, and Microsoft provides separate tools for moving mail and files into Microsoft 365. The tools move workloads; they do not choose the strategy, test dependencies or plan the cutover, which is the work we add.
Plan your cloud migration with one accountable team
Tell us what you run today and where you want it to be. We will assess it, recommend a strategy for each workload and quote the project in writing. Call 010 447 2445 or email info@arketechnologies.com.