Most IT teams treat Office 365 migration as a software problem. It isn't. It's a hardware conversation, a network conversation, and a human conversation all layered on top of each other. When load shedding hits your office or a MacBook hasn't received a security update since 2021, your migration plan falls apart. That's why we're writing this from the workshop floor, not from a marketing script.
Why Office 365 Migration on Apple Devices Requires Different Planning
The Microsoft ecosystem assumes Windows. Outlook for Mac has different sync behaviour than Outlook for Windows. OneDrive on macOS caches differently. Exchange Web Services work, but not identically. We've seen more than 14,000 devices pass through our workshop in Johannesburg, and the ones that migrate smoothly are the ones where someone understood these differences before day one.
Your Apple devices also carry institutional friction. Some MacBooks are five years old. Others are M3 chips released last quarter. A migration plan that works for a 2019 Intel MacBook Air will fail for an M1 Pro with insufficient storage. You need to know your fleet's actual age, capacity, and update status before you commit to a cutover date.
The other issue is unique to Johannesburg: load shedding. We've watched migrations fail at stage four when loadshedding dropped the office network for forty minutes. Eskom's schedule becomes your project risk. You plan around it or you schedule your cutover for weekend, when the grid is more stable.
Step One: Audit Your Fleet Before You Touch Anything
Before you migrate a single mailbox, you need three things: a hardware inventory, a software baseline, and a network map.
First, audit your devices. Run Apple's Remote Management or use a mobile device management solution to pull exact macOS versions, storage capacity, and RAM for every Mac in your fleet. We typically recommend that every device migrating to Office 365 runs at least macOS 12 (Monterey), preferably 13 or 14. If you have devices older than that, they may require hardware upgrades or replacement before they can support modern Outlook performance.
Second, check your network. Office 365 requires consistent, reliable bandwidth for initial mailbox sync. In Johannesburg, that means understanding your ISP's performance during peak hours and planning your cutover window accordingly. If you're in an area prone to loadshedding congestion, schedule your migration for a weekend or a public holiday when traffic is lower.
Third, know your storage. Outlook for Mac caches mail locally. If your users have fifteen years of email history and a MacBook with only 128 GB of storage, you'll have a problem. We've seen this in our workshop dozens of times: a migration stalls because Outlook can't complete its initial sync without crashing the device. We offer an R599 assessment service that covers this exact audit—hardware, software, network readiness, and storage planning. Book online at zasupport.com/book if you'd like us to audit your fleet before you commit to a cutover date.
Step Two: Phase Your Cutover by Device Cohort, Not All At Once
Never migrate your entire fleet on the same day. That's the lesson we've learned with more than 12,000 devices over eight years.
Instead, phase your cutover into cohorts of 10–20 devices per day, prioritising early adopters and technical users first. Day one might be your IT team and finance department. Day three might be marketing. Day six might be your most resistant users, once you've documented the new workflows and can answer their questions with experience.
For each cohort, the sequence is:
Only after a full day of validation do you move to the next cohort.
Step Three: Handle Hardware and Network Issues Before They Kill Your Timeline
Office 365 migration often surfaces hardware problems that were dormant. A MacBook with a failing solid-state drive will perform terribly during mailbox sync. A device with liquid damage may have intermittent network connectivity. We've seen this pattern repeatedly at our workshop.
We recommend a light hardware assessment for any device that's more than four years old. If you identify a device with issues—failed logic board repair cases, liquid damage history, or critically low storage—either repair it before migration or defer that user to a later cohort.
For network, test your bandwidth during the planned cutover window. Office 365 expects at least 10 Mbps sustained for initial sync. If your office is on a congested shared connection or your ISP has documented issues during certain hours, move your cutover to a quieter window. In Johannesburg, that often means Friday evening or Saturday morning to avoid peak business hours and loadshedding schedules.
Step Four: Support Your Users During the First Week
The first week after cutover is where most migrations stumble. Users are confused about where their old emails are. They don't know how to move messages between folders in Outlook for Mac. They've forgotten their MFA codes.
Have a dedicated support person or team available for the first five days after each cohort's cutover. We recommend a shared Slack channel or WhatsApp group where users can ask questions in real time. Most issues resolve in minutes with a screenshot or a quick screen share.
For users who are struggling, WhatsApp us on 064 529 5863 if you're in the Johannesburg area. We can do a remote troubleshooting session or bring the device to our Hyde Park workshop for a full assessment.
Step Five: Document Your Cutover and Archive Your Data
After each cohort migrates successfully, back up the old Exchange account data. We recommend exporting old mailboxes to PST or using a third-party tool like Mimecast or Commvault to archive the old environment. This is your insurance policy if anything goes wrong and you need to revert a user's data.
Also document what worked and what didn't. Did OneDrive sync stall on certain devices? Did any user experience mailbox corruption? Did load shedding affect your timing? These notes become your playbook for the next cohort and for future projects.
---
Frequently Asked Questions
Q: How long does it take to migrate one MacBook to Office 365?
For a device with a typical mailbox (under 30 GB), plan four to six hours from account disconnect to full validation. For larger mailboxes or older devices with slower storage, plan eight to twelve hours. The actual cutover itself takes about two hours, but the subsequent sync and validation are where time sits.
Q: Do we need to buy new MacBooks for Office 365?
No, but your devices need to be recent enough to run modern Outlook. We recommend macOS 12 or later. If you have 2015 MacBook Airs still in use, those can run Monterey and migrate fine. If you have 2012 models, they're probably at end of life anyway. That's when a hardware refresh makes financial sense.
Q: What happens to our old Exchange server?
You can decommission it after all users have been migrated and you've confirmed there are no dependencies (like shared mailboxes or distribution lists that haven't been migrated to Office 365). Plan a six-week retention period before you shut it down completely.
Q: Can we migrate during working hours, or should we do it overnight?
Phase your migration so that each user's cutover happens outside their peak working hours. If you migrate someone's mailbox at 9 AM on a Monday and their inbox doesn't finish syncing until 2 PM, they've lost a half day of productivity. Schedule cohorts for Friday evening or Saturday morning instead.
Q: What if load shedding disrupts our migration?
If Eskom's loadshedding schedule conflicts with your planned cutover window, move it. We recommend checking the schedule at least two weeks ahead and building a buffer. A migration that survives loadshedding intact is worth postponing for.
Q: Do we need to replace OneDrive or can we use a different cloud storage?
Microsoft makes Outlook and OneDrive work together smoothly. If you use Google Drive or Dropbox instead, you'll lose some integration features and you'll be managing two separate sync engines. We recommend OneDrive as the primary cloud storage for any Office 365 tenant. If you need hybrid cloud, that's a more complex architecture conversation—contact us for a consultation.
