Why South African businesses are still moving in 2026
Three-quarters of SA SMEs we onboard still run a physical Windows Server in a cupboard — usually Exchange 2016/2019, a file share and Active Directory. That server is now the single biggest risk in the business: unpatched firmware, no offsite backup, and a UPS that lasts 12 minutes on load-shedding stage 6.
The move to Microsoft 365 and Azure isn't fashion. It removes the single point of failure, cuts capex, gives you enterprise-grade security you could never afford on-prem, and — crucially for load-shedding — makes your business location-independent overnight.
The five phases of a proper migration
- Discovery (1–2 weeks). Full inventory: mailboxes, distribution lists, shared calendars, public folders, file shares (with permissions), line-of-business apps, printers, VPN users, service accounts. Nothing gets migrated that isn't documented.
- Design & licensing (3–5 days). Pick the target tenancy layout, licence mix (Business Standard vs Business Premium vs E3/E5), identity model (cloud-only vs hybrid Entra Connect), and conditional access baseline.
- Build (1–2 weeks). Stand up the tenant, apply security baseline, configure Exchange Online, SharePoint sites, Teams, Intune enrolment profiles and backup (Datto / AvePoint / Barracuda). Zero users touched yet.
- Cutover in waves (2–4 weeks). Migrate 10–25 users per weekend batch, verify each wave, communicate obsessively. See next section.
- Hypercare & decommission (1–2 weeks). Extra help-desk cover, daily standups, then the old server is powered down (never immediately deleted — we snapshot and retain for 90 days).
Wave-by-wave cutover — the only method that works
Big-bang cutovers ("everyone moves this weekend") are the reason cloud migrations have a bad reputation. Waves are boring, predictable, and safe:
- Wave 0 — IT team. Migrate yourselves first. If your own mailbox breaks, you'll find out before a client does.
- Wave 1 — friendly pilot (5–10 users). Pick tolerant, tech-comfortable staff across departments. Two weeks of soak time.
- Waves 2–N — production batches. 15–25 users per weekend. Always finish on a Sunday afternoon; Monday morning is not a migration window.
- Wave Final — the CEO and the finance team. Move them last. They have the least tolerance for disruption, and by now every kink is out of the process.
Between every wave: a written go/no-go, backups verified, mail flow tested from three external domains, MFA re-enrolment confirmed.
Where migrations actually fail
- Undocumented dependencies — the accounting server that quietly SMTP-relays through Exchange, the multifunction printer scanning to a mapped drive.
- Shared mailboxes and delegates — always the messiest part of Exchange. Audit every one during discovery.
- DNS & SPF/DKIM/DMARC — miss one record and legitimate mail goes to spam for a week.
- User training — Outlook profile rebuild, new MFA prompt, OneDrive first-run. A 30-minute drop-in per wave prevents 90% of help-desk tickets.
- Line-of-business apps — Sage, Pastel, industry tools that expect a local server. Sort the plan for these BEFORE Wave 1, not after.
Realistic cost in South Africa (2026)
- Discovery & design: R15,000–R30,000 (waived by 1ICT if you sign the migration).
- 25-user M365 migration, greenfield tenant: R55,000–R95,000 professional services.
- Add Entra Connect hybrid identity: +R15,000–R25,000.
- Lift-and-shift one Windows LOB server to Azure IaaS: R25,000–R60,000 + Azure consumption (typically R2,500–R6,000/month for a B2ms-class VM).
- Third-party M365 backup (Datto/AvePoint): R60–R120 per user per month, non-negotiable.
Payback is usually 8–14 months when you factor in the retired server, UPS, air-con, downtime and after-hours support calls the old setup was silently costing you.
Frequently asked questions
How long does a typical cloud migration take?
For a 20–80 user SA business with on-prem Exchange, a file server and one line-of-business app, plan on 6–10 weeks end-to-end: 2 weeks discovery, 2–4 weeks build, 2–3 weeks staged cutover, 1 week hypercare.
Will email break during the migration?
Not if it is done in waves with hybrid coexistence. We keep both mail systems live in parallel, migrate mailboxes in batches of 10–25, and only decommission the old server after every user is stable for at least 14 days.
Do we have to move everything to the cloud?
No. About 80% of workloads (email, files, identity, collaboration) belong in Microsoft 365. Specialist apps — SQL-heavy accounting, industry compliance systems, low-latency CAD — often stay on Azure IaaS or a small on-prem remnant. Hybrid is normal, not a failure.
What does a cloud migration cost in South Africa?
A 25-user greenfield M365 migration typically runs R55,000–R120,000 professional services + licence uplift. Azure lift-and-shift of a single line-of-business server adds R25,000–R60,000. We fix-price after discovery so there are no surprises.
What is the biggest reason migrations fail?
Skipping discovery. A rushed migration always breaks on the one shared mailbox, distribution list, printer script or Sage integration that nobody documented. Two weeks of discovery pays back tenfold.
Do we need Azure, or is Microsoft 365 enough?
For most SA SMEs, M365 covers 90% of needs. You only need Azure when you have server workloads (line-of-business apps, SQL, custom software) that can't move into SaaS.