Microsoft 365 migration plan: moving a Dubai office without a chaotic Monday
Copy first, switch second: the phases, DNS records and weekend cut-over behind a calm move to Microsoft 365.
Part of our guide to Microsoft 365 & Cloud.
A good Microsoft 365 migration plan copies everything before switching anything. Set up the tenant and security first, inventory mailboxes and file shares, design SharePoint and Teams, then sync mail and files in the background while staff keep working. Change DNS over a weekend, run a final delta sync, and support people closely through the first weeks.
Key takeaways
- Pre-stage mail and files for days before cut-over so the weekend switch only moves recent changes.
- Turn on MFA and limit Global Administrator accounts before any company data enters the tenant.
- Design SharePoint sites and Teams around how departments work, not around the old folder tree.
- At cut-over you change MX, Autodiscover and SPF, then add DKIM and DMARC for the new platform.
- Microsoft keeps the service running, but backing up your own mail and files remains your job.
What are the phases of a Microsoft 365 migration plan?
A calm migration has six phases: planning, tenant and security setup, background sync, a weekend cut-over, hypercare, and decommissioning. The principle behind all of them is simple: copy first, switch second.
The migrations that go wrong are the ones done live. Someone repoints the domain, hopes the mail arrives, and discovers on Monday that half the folders are missing. The migrations that go smoothly copy data into Microsoft 365 over several days, check it against the source, and only then move the domain. Staff sign in on Monday with the same email address and find their mail where they left it. If you would rather hand the mailbox move to an engineer, our email migration services in Dubai run it as a fixed-scope project.
| Phase | What happens | Who is affected |
|---|---|---|
| Planning | Inventory, licence choice, SharePoint and Teams design, cut-over date agreed | Management and IT only |
| Tenant and security setup | Domain verified, MFA and admin roles configured, accounts created | IT; staff register MFA |
| Background sync | Mail and files copied and verified while the old system stays live | Nobody notices |
| Weekend cut-over | DNS records changed, final delta sync, spot checks | Staff asked not to work Saturday and Sunday |
| Hypercare | Outlook profiles, phones, OneDrive and Teams questions resolved quickly | Everyone, for the first days |
| Decommissioning | Old system kept read-only, then retired once nothing depends on it | Finance and IT |
Where Dubai offices usually start
The source system decides which tools you use and what can be copied automatically.
- Google Workspace: mail, calendars and contacts can move with Microsoft's own migration tooling; Google Drive files need a separate file migration step.
- On-premises Exchange: a cutover or hybrid migration, depending on the Exchange version and how many mailboxes you have.
- IMAP or cPanel hosting mail: IMAP migration copies email folders only, so contacts and calendars must be exported and imported separately.
- A file server, NAS or shared drive: files move into SharePoint and OneDrive, and permissions have to be rebuilt deliberately.
Which Microsoft 365 licence does your office need?
Most small offices choose between Business Basic, Business Standard and Business Premium, and the Business plans are capped at 300 users. The right choice depends on whether staff need desktop Office apps and how much device and security control you want.
Business Basic gives each user an Exchange mailbox, Teams, OneDrive, SharePoint and the web and mobile versions of Word, Excel, PowerPoint and Outlook. Business Standard adds the installable desktop apps, which most finance and admin teams expect. Business Premium includes everything in Standard plus advanced security and device management, such as Intune, Defender for Business and Conditional Access. How Teams, SharePoint and Exchange fit together is documented in the Teams overview.
You can mix plans in one tenant. A reception desk or warehouse user who only reads email may be fine on Basic while the accounts team runs Standard or Premium. Decide this during planning, because licences must be assigned before mailboxes can receive migrated data. What each plan includes is set out in the Microsoft 365 platform service description.
How do you set up the tenant and security before data moves?
Create the tenant, verify your domain and lock down sign-in before a single mailbox is copied.
Domain verification is done by adding a TXT record at your DNS host, often the registrar or the company that built your website. Verifying the domain does not move your mail. It only proves ownership so you can create users with their real addresses, which lets the migration run in the background with no disruption.
- Require multi-factor authentication for every account, starting with administrators. Our guide to MFA for small businesses covers rollout without a flood of calls.
- Keep Global Administrator to a small number of named accounts, and give day-to-day staff narrower roles such as User Administrator or Exchange Administrator.
- Create an emergency access account with a long password stored offline, so a lost phone cannot lock you out of your own tenant.
- Ask staff to register MFA the week before cut-over, not on Monday morning.
What should you inventory, and how should SharePoint and Teams be structured?
List every mailbox, shared mailbox, distribution list, shared calendar and file share before you migrate. Anything missing from the inventory is usually what someone asks for on Monday.
Offices collect more mail objects than they realise: an info@ address several people read, a careers@ alias forwarding to a former manager, a meeting room calendar, a finance share mapped as drive S on only three laptops. Record who owns each one and who needs access.
Plan SharePoint before you move files
A SharePoint migration is the moment to fix years of folder sprawl, not copy it. Map departments or functions to SharePoint sites, and give each team that collaborates daily a Team connected to its site. Keep permissions at site or library level wherever possible, because permissions set on individual folders become impossible to audit.
Personal working files belong in each user's OneDrive. Shared company records belong in SharePoint. Agree that rule with department heads in writing, then map every old share to its new home before any sync starts.
How do you migrate email and files while staff keep working?
Run the bulk copy days ahead of cut-over while the old system stays in use. The first pass moves the heavy history; later passes only pick up what changed.
For an email migration to Microsoft 365, mailboxes are copied in batches and checked: folder counts, a sample of old messages, calendar entries and contacts. For Google Workspace to Microsoft 365 moves, confirm calendars and shared calendars arrived, since that is where people notice gaps. IMAP sources need either each user's mailbox password or admin access from the host, so arrange that securely rather than collecting passwords by email.
Files follow the same pattern. Microsoft's migration tools copy file shares into the planned SharePoint libraries and flag files they cannot move, such as names with unsupported characters or paths that are too long. Fix those in the source during the sync window. Schedule large first passes on your du or e& line for evenings, so daytime calls are not affected. Microsoft provides bulk tooling for the file move in Migration Manager.
Which DNS records change at cut-over, and why a weekend?
On cut-over you repoint MX so new mail flows to Microsoft 365, then update Autodiscover and SPF and add DKIM and DMARC. In Dubai the Saturday and Sunday weekend gives you two quiet days to switch, sync and test.
Lower the TTL on your mail records a few days before, so changes take effect quickly. On Friday evening, change the records, then run a final delta sync to catch anything that reached the old system while DNS was updating.
- MX: points to the Microsoft 365 mail host shown in your admin portal, replacing the old provider.
- Autodiscover: a CNAME that lets Outlook and phones find the new mailbox automatically.
- SPF: one TXT record listing Microsoft 365 plus any other service that sends as your domain, such as a website form or accounting system.
- DKIM: two CNAME records, then signing switched on so receiving servers can verify your mail.
- DMARC: a TXT record at _dmarc, starting in monitoring mode before you tighten the policy.
What do staff see on Monday, and what happens after go-live?
Staff sign in with their usual address and the MFA they registered the week before, and their mail, calendars and files are already there. A one-page guide covers how to sign in, where each old drive now lives in SharePoint, how to add the Outlook app on a phone, and who to call.
Plan a hypercare period for the first week or two, with an engineer on hand in the office on Monday morning. Typical requests are desktop Outlook needing a fresh profile, phones still pointing at the old server, and people looking for a folder that moved.
Decommissioning the old system
Keep the old system read-only for an agreed period before cancelling it. Check nothing still sends through it: scan-to-email on multifunction printers, website contact forms and line-of-business software are the usual stragglers. Then remove old DNS entries and close the hosting or Google subscription.
Back up Microsoft 365 separately
Microsoft runs a shared responsibility model: it keeps the platform available, while your data remains yours to protect. Recycle bins and retention are time-limited and will not save you from a deletion noticed months later or a compromised account. A separate backup of Exchange, OneDrive, SharePoint and Teams closes that gap; see how to set up backup that actually restores.
How do you migrate shared mailboxes, distribution lists and aliases cleanly?
User mailboxes get the attention in a migration, and they are the straightforward part. The addresses that break on Monday morning are the other ones: the sales@ mailbox three people watch, the alias the website form sends to, the distribution list the finance team uses for invoices, and the old address of someone who left two years ago that a supplier still writes to. Each needs a deliberate decision, and a migration plan that lists only people will miss them all.
Inventory every address that exists on the old system, not just every person, and mark what each one is. Shared mailboxes become true shared mailboxes in Microsoft 365, with the right people given access, rather than licensed accounts with a password on a sticky note. Distribution lists become either distribution groups, which simply forward, or Microsoft 365 groups, which add a shared calendar and files; the choice depends on how the list is used and is worth a minute's thought per list. Aliases attach to the mailbox they belong to, and the addresses of former staff are either forwarded to a manager or turned into shared mailboxes for a defined period so nothing arriving there is lost.
Check the things that send mail without being people: the website contact form, the scanner, the accounting software, the alarm system. Each needs its sending method updated at cut-over. Then test every address on the list with a real message before staff arrive, and keep the inventory as the starting point for the documentation, because the list of who receives what is exactly the thing the next office manager will need.
- Inventory every address, not every person, and mark what each one is.
- Shared mailboxes as true shared mailboxes; distribution lists as the right kind of group.
- Aliases attached to the correct mailbox; former staff addresses forwarded or preserved.
- Forms, scanners and applications that send mail updated at cut-over.
- A test message to every address before Monday morning.
How Listonics helps with a Microsoft 365 migration
Listonics plans and runs Microsoft 365 migrations for Dubai offices of roughly 5 to 200 staff, from Google Workspace, on-premises Exchange, hosting mail and file servers. We start with a free office IT assessment, then send a fixed-scope, itemised proposal covering tenant setup, security baseline, SharePoint and Teams design, the weekend cut-over and hypercare.
Engineers are on site across the UAE for go-live, and remote support covers the rest of the UAE. You receive an account list at handover. If you want ongoing care afterwards, Microsoft 365 support in Dubai is available under a managed plan at a fixed monthly fee per user. See our Microsoft 365 and cloud services or book a free assessment. What the project costs, and how licences are quoted separately, is on our Microsoft 365 migration cost page.
Frequently asked questions
It depends on the number of mailboxes, the volume of files and the source system. The pattern is consistent: a planning and tenant setup stage, several days of background sync while staff work normally, then a weekend cut-over followed by hypercare. Large file shares take longer to copy than mail, so start them first.
No. Your existing domain is verified in Microsoft 365 and every user keeps the same address. Old messages are copied into the new mailboxes before cut-over, and once the MX record changes, new mail simply starts arriving in Microsoft 365 instead of the old system.
Yes. Mail and files are copied in the background while everyone uses the old system as usual. The only pause is the cut-over weekend, when staff are asked not to work in the old system so the final delta sync can capture every last change.
It can be for staff who work mainly in a browser or on phones, since it includes email, Teams, OneDrive, SharePoint and web versions of the Office apps. Teams that rely on desktop Excel or Word usually need Business Standard, and offices wanting device management and stronger security controls look at Business Premium.
Yes. Microsoft keeps the service running, but protecting your data is your responsibility under its shared responsibility model. Deleted items are only recoverable for a limited time, and a compromised account or ransomware can damage mail and files. A separate backup lets you restore mailboxes, sites and files independently.
Anything that sends as your domain needs checking before the old system is switched off. Multifunction printers with scan-to-email, website forms and accounting or CRM software often use the old mail server settings. Each needs reconfiguring for Microsoft 365, and legitimate senders should be included in your SPF record.
Yes, if they are in the plan. Each list is recreated either as a distribution group that simply forwards or as a Microsoft 365 group with a shared calendar and files, depending on how it is used. Lists that were not inventoried before cut-over are the ones that silently stop, so list every address, not just every person.
Written by Srinivasan Ramachandran, Founder, Listonics · Published Jul 16, 2026 · Last reviewed October 29, 2026 · 2291 words
