Most Microsoft 365 migrations that go wrong do not fail on the day. They fail quietly: a shared mailbox nobody listed, an archive PST on one laptop, a calendar that arrives without its meeting rooms, or a week of email that landed in the old system after the MX record changed. Losing data in a migration is almost always a planning problem, not a tooling problem.
This guide is the method our engineers use when moving companies in Egypt to Microsoft 365 from Gmail and Google Workspace, from on-premises Exchange, or from a hosting provider’s mail server. It is written for the IT manager or business owner who wants to know what a careful migration looks like before signing anything.
1. Inventory before you plan
You cannot migrate what you have not counted. Before choosing a method, list:
- Every mailbox, including shared mailboxes (info@, sales@, accounts@), resource mailboxes (meeting rooms) and mailboxes of people who have left but whose mail must be kept.
- Mailbox sizes and item counts, so you can estimate copy time and spot anything that will not fit the target licence.
- Archives outside the server: PST files on laptops, old IMAP folders, exported backups.
- Aliases, distribution lists and forwarding rules. These are the things users notice first when they disappear.
- Files: shared drives, Google Drive, file servers and personal folders that are moving to OneDrive, SharePoint or Teams.
- Everything that sends email as your domain: the website contact form, the ERP, scanners, the CRM. Each one needs to keep working after the switch.
2. Choose the right migration method
| Moving from | Usual method | Notes |
|---|---|---|
| Google Workspace / Gmail | Google Workspace migration in the Exchange admin center | Moves mail, calendar and contacts; Drive files move separately with Microsoft’s migration tools. |
| On-premises Exchange (small) | Cutover migration | All mailboxes in one batch; suitable for smaller organisations. |
| On-premises Exchange (larger, or staying hybrid) | Hybrid / staged migration | Mailboxes move in batches while both systems share the address book. |
| Hosting provider or other IMAP server | IMAP migration | Moves email only; calendars and contacts need to be exported and imported separately. |
The method decides what moves automatically and what has to be handled by hand. Writing that list down is how you avoid the “we assumed it would come across” conversation.
3. Prepare the tenant first
- Verify your domain in Microsoft 365 and assign the right licences, so every user has a mailbox ready before any data moves.
- Lower the TTL on your MX record a day or two before the switch, so the change takes effect quickly when you make it.
- Turn on multi-factor authentication and decide on retention and backup before users log in, not after the first incident.
- Prepare SPF, DKIM and DMARC for the new service so your mail is trusted from day one.
4. Pilot, then pre-stage
Move a small group first: a few people from different departments, including one heavy user and one shared mailbox. Let them work for a few days and collect what broke. Then copy the bulk of everyone’s mail in the background while people keep working in the old system. By switch day, only the most recent changes are left to move.
5. Switch over, then sync the gap
Change the MX record (and Autodiscover) outside working hours, run a final incremental sync to pick up anything that arrived during the change, and keep the old system readable for a while. Mail that lands in the old server during DNS propagation is the classic source of “lost” email; the final sync and a short overlap period close that gap.
6. Check, do not assume
- Compare item counts per mailbox between source and target.
- Open shared mailboxes, calendars and meeting rooms from a user’s account, not an admin’s.
- Send test mail from the website, the ERP and the scanners.
- Confirm that phones and Outlook profiles connect to the new service.
- Check SPF, DKIM and DMARC results on real outgoing mail.
7. Decommission last
Do not cancel the old service the day after. Keep it, read-only, until every check above is signed off and users have confirmed nothing is missing. Then export a final archive and cancel.
Questions we are asked most
Will users lose email during the migration?
Not if mail is pre-staged, the MX change is planned, and a final sync runs after the switch. Most “missing email” cases come from skipping that last step.
How long does it take?
It depends on the number of mailboxes, their size and the source system. Pre-staging means most of the copying happens while people keep working, so the visible switch is usually a single evening.
Do we need new licences before we start?
Yes. Users need a Microsoft 365 licence with a mailbox before their data can be moved. We supply and invoice Microsoft 365 licences in Egypt and help choose the right plan, so you do not pay for features you will not use.
What about our files?
Files move to OneDrive, SharePoint or Teams with Microsoft’s migration tools. The important part is deciding the structure and permissions first, so the new layout is better than the old one, not a copy of its problems.
Planning a move to Microsoft 365, or a renewal coming up? Tell us how many users you have and where your email lives today, and our engineers will tell you the method, the timeline and what you should be paying.
See our Microsoft 365 services, read about our Microsoft partnership, or contact us. Call +20 122 224 9390.



