Migrate to Microsoft 365 Without Losing Data.

Published: 28 May 2026  |  By AOLC

Migrating to Microsoft 365 is one of the smartest IT decisions a South African business can make — but it is also one of the most commonly botched. Done right, the migration takes days, your team barely notices, and you end up with a faster, more secure, and fully cloud-based environment. Done wrong, you lose emails, corrupt mailbox data, leave staff locked out for days, and spend the next three months cleaning up the mess.

This guide covers the full process: from auditing your current environment, to choosing the right migration approach, to the post-migration checks that prevent headaches down the line. Whether you are moving from on-premises Exchange, an old hosting provider, or a Google Workspace account, the principles are the same.

Why Microsoft 365 Is Worth the Move.

For South African businesses still running on-premises Exchange servers or shared hosting, the benefits of Microsoft 365 are substantial:

• Integrated productivity suite — Email, Teams, SharePoint, OneDrive, and the full Office app suite in a single monthly subscription. No separate licensing headaches.
• Cloud resilience during load shedding — Your email and files live in Microsoft's data centres, not your server room. A power outage does not take your email offline.
• POPIA-friendly data residency — Microsoft has data centre regions in Johannesburg and Cape Town. You can keep your data on South African soil and satisfy your POPIA data residency obligations.
• Predictable monthly cost — No server hardware refresh every five years. No unexpected maintenance bills. Per-user, per-month pricing you can budget for.
• Security built in — Microsoft Defender, multi-factor authentication, data loss prevention, and advanced threat protection are all included or available as add-ons.

Choose the Right Migration Type.

Microsoft supports three main migration approaches. The right choice depends on your organisation's size and existing infrastructure:

• Cutover migration — Move everything in one go. Best for businesses with fewer than 150 mailboxes. Faster and simpler, but requires a planned cutover window where email may be in transit between systems.
• Staged migration — Move in batches over several weeks. Best for larger organisations (150+ mailboxes). Reduces risk but requires running two mail systems in parallel during the transition period.
• Hybrid migration — Keep on-premises Exchange running alongside Microsoft 365 indefinitely. Best for large enterprises with complex requirements. Most expensive to set up and maintain.

Most South African SMEs opt for cutover migration — it is the simplest approach and works well for businesses up to about 200 users. If you are migrating from Google Workspace or a third-party hosting provider, you will use an IMAP migration instead of an Exchange migration tool.

The Pre-Migration Audit: Do Not Skip This.

This is the step most businesses cut short — and the one most responsible for data loss. Before touching anything, run through the following:

• Inventory all mailboxes — Include shared mailboxes, distribution lists, resource mailboxes (meeting rooms, equipment bookings), and any service accounts used by applications such as your accounting software or CRM.
• Check mailbox sizes — Microsoft 365 Business Basic includes 50 GB per user, and Business Premium includes 100 GB. If any mailbox exceeds these limits, archive or clean up first. Oversized mailboxes are a common migration failure point.
• Document your DNS records — MX, SPF, DKIM, and DMARC records all need to be updated during the migration. Export these before you start so you have a reference.
• Map shared drives to SharePoint — If your team uses shared network drives (mapped drives, NAS storage), plan how these will map to SharePoint document libraries or OneDrive folders in the new environment.
• List all connected applications — Any software that connects to your email server — CRMs, helpdesk platforms, accounting tools, print-to-email setups — will need to be reconfigured with new server settings after the migration.
• Check your bandwidth — Migrating 100 mailboxes uploads a significant volume of data. If your internet connection is already under load, schedule your migration for off-peak hours or a weekend.

The Step-by-Step Migration Process.

Once the audit is done, the migration follows a consistent sequence:

• Step 1 — Create your Microsoft 365 tenant — Set up the tenant using your business domain. Do not create user accounts yet. Start with admin configuration only.
• Step 2 — Verify domain ownership — Add a TXT record to your DNS to prove ownership. This typically propagates within 15–60 minutes. Do not update your MX record at this stage.
• Step 3 — Create mailboxes and assign licences — Add all users and match their primary email addresses exactly to their existing accounts. Configure shared mailboxes, distribution lists, and resource calendars at this point too.
• Step 4 — Run a test migration — Migrate one or two low-risk mailboxes first. Verify that emails, folder structure, calendar items, and contacts have transferred correctly before proceeding.
• Step 5 — Migrate in batches — For cutover migrations, submit all mailboxes in a single migration batch. For staged migrations, work through batches of 20–50 users, starting with non-critical accounts.
• Step 6 — Let the sync run and review the report — Allow the initial sync to complete overnight. Review the migration status report for errors or incomplete mailboxes before proceeding.
• Step 7 — Update MX records — This is the cutover moment. Update your MX record to point to Microsoft 365. New email now flows into the new system. Communicate this to your team before you do it.
• Step 8 — Run a final sync — After MX records update, run a final migration sync to catch any emails that landed on the old server during the DNS propagation window.
• Step 9 — Decommission the old system — Only after you have confirmed that everything is working correctly should you cancel old hosting, decommission on-premises servers, and update all connected applications.

Getting Your Team Ready for the Switch.

The technical migration is only half the work. If staff are not prepared, you will spend the first week after go-live fielding support tickets instead of confirming success.

• Communicate the change in advance — Send a brief email to staff one week before and again one day before. Keep it simple: what is changing, when, and what they need to do.
• Explain OneDrive vs SharePoint — OneDrive is personal cloud storage (like a cloud-based My Documents). SharePoint is shared team storage (like a cloud-based shared network drive). This distinction causes more confusion than anything else in an M365 migration.
• Set up Teams separately from the email cutover — If you are adopting Teams for communication, deploy it and let staff use it for one to two weeks before the email migration. Mixing two changes at once increases support load.
• Prepare a quick-start guide — One page covering how to log in, where to find email, how to access files, and who to contact for help. Your IT provider should supply this as part of the migration.
• Enable self-service password reset before go-live — Staff will forget their credentials. Configure Azure AD self-service password reset so your helpdesk is not overwhelmed on day one.

Post-Migration Checks: Verify Before You Celebrate.

Within 48 hours of the MX cutover, run through these verification steps:

• Verify email delivery — Send test emails from external accounts (Gmail, personal email) and confirm delivery in Microsoft 365.
• Check calendar sharing and room bookings — Confirm that shared calendars and meeting room resources are accessible and booking correctly.
• Test distribution lists — Send a test email to each distribution group and confirm delivery to all members.
• Reconnect business applications — Update server settings in any CRM, accounting software, or helpdesk tool that connects to email. Test each one before closing the ticket.
• Review the migration report for errors — Any mailboxes flagged with errors need to be investigated and re-migrated if necessary.
• Enable Multi-Factor Authentication for all users — MFA should be active on day one. This is non-negotiable on a cloud platform exposed to the internet. See our guide on why MFA is essential in 2026.
• Review Microsoft 365 licence assignments — Confirm that all users have the correct licence tier and that any unused licences from the old system have been cancelled.

---

Get It Right the First Time.

A Microsoft 365 migration does not have to be stressful or risky. The businesses that have smooth migrations invest time upfront in the audit and planning phase — and they work with an IT provider who has done it before. Skipping steps to save time is where data loss and downtime come from.

The worst-case scenario is a forced migration: your on-premises server fails, your old hosting provider shuts down, or a ransomware attack takes out your local infrastructure. At that point, you are migrating under pressure with no time to plan. The businesses that have already made the move to cloud-based infrastructure are in a far stronger position — their email, files, and collaboration tools are simply inaccessible to attackers who target on-premises hardware.

If your business is still running on legacy email infrastructure or an ageing on-premises server, now is the right time to start planning the move — before a crisis forces your hand.

← Back to Blog