Download template: Microsoft 365 Migration Scope of Work (.pdf)

Server-to-server mail migration tools are fairly predictable at this point. When an Office 365 cutover turns into a rough Monday morning, the bulk data copy is rarely what went wrong.

More often, the trouble comes from what was left vague in a one-page quote—or rather, what different people assumed "email migration" included. Maybe an accounting copier or ERP invoice mailer starts bouncing right after the MX switch because nobody knew it sent mail as your domain. Maybe an executive assistant opens Outlook and discovers calendar delegate permissions vanished during import, or half the sales team keeps replying from mobile profiles pointed at the retired server. And it is not unheard of for leadership to assume ten years of Google Shared Drives or local desktop .pst archives were part of the deal while the person running the project scoped mailboxes only.

Writing those boundaries down before anyone touches DNS spares everyone that Monday-morning surprise. Whether you are moving off Google Workspace, hosted Exchange or IMAP, a GoDaddy federated Microsoft 365 setup, or an acquired company's tenant, you can adapt the downloadable PDF above and the sections below to scope the work cleanly.

Recipient, Alias, and SMTP Relay Discovery

Before ordering licenses or putting a cutover weekend on the calendar, pull a full inventory from the current mail server and DNS zone so nothing shows up unannounced on Friday night:

  • Check active mailbox sizes and archive tiers first, flagging any mailbox above 45 GB so target licensing (50 GB Exchange Online Plan 1 / Business Basic-Premium versus 100 GB Plan 2 / E3 with auto-expanding archive) is sized properly before sync starts.
  • Export shared mailboxes, distribution lists, secondary smtp: aliases, public folders, room and equipment calendars, and every FullAccess, SendAs, and SendOnBehalf permission.
  • Track down non-human SMTP senders and inbound mail pipes, including multifunction office copiers and scanners, website contact forms, helpdesk intake addresses (Zendesk, Jira Service Management, Freshdesk), and ERP or accounting invoice mailers.
  • If the source environment sits on GoDaddy federated Microsoft 365, schedule tenant defederation or cross-tenant migration steps explicitly so custom domains do not stay locked mid-weekend.

Destination Tenant Setup and Domain Verification

Stand up and test the destination Microsoft 365 and Entra ID tenant days ahead of cutover rather than building security rules live on Friday evening. Provision user and shared mailboxes, assign right-sized SKUs (our Microsoft 365 license audit guide covers common over-licensing traps), and verify custom domains via TXT records without touching MX routing yet.

With the tenant live, put your Entra ID Conditional Access baseline in place early: block legacy POP, IMAP, and basic SMTP authentication, enroll hardware-key break-glass accounts, and prepare employee MFA so staff do not run into surprise lockouts on Monday morning. At the same time, publish 2048-bit DKIM CNAME selectors (selector1._domainkey and selector2._domainkey) and add include:spf.protection.outlook.com to your existing SPF record while keeping total lookups under the 10-DNS-lookup ceiling (see how to set up DMARC).

Lowering DNS TTLs and Pre-Staging Historical Mail

What happens if you wait until Friday at 6:00 PM to start copying several terabytes of old mail? Usually Exchange Online or the source server throttles the connection, and Sunday evening arrives with half the company's mail still in flight.

A two-pass pre-stage setup avoids that crunch. At least 72 hours before cutover, drop DNS TTLs to 300 seconds (5 minutes) on your MX, SPF TXT, autodiscover CNAME, and webmail records, and check authoritative propagation with dig +nocmd +noall +answer MX example.com. One to two weeks ahead of the switch, sync everything older than 30 days—mail, contacts, and calendars—during normal business hours while people keep working in the old system. If a mailbox hits oversized attachments, corrupt MIME items, or folder path-length errors, you can sort them out calmly on a Tuesday afternoon instead of at two in the morning on Sunday.

Running the Cutover Weekend in Order

Once historical data is staged, cutover weekend comes down to switching routing, catching the final 30 days of changes, and testing every step before moving to the next. Here is what a typical Friday-to-Sunday schedule looks like:

Cutover Window Engineering Action Verification Gate
Fri 18:00 (T-0) Switch authoritative MX to <tenant>.mail.protection.outlook.com and autodiscover CNAME to autodiscover.outlook.com dig +short MX example.com @1.1.1.1 resolves to Exchange Online; external test messages land in target OWA
Fri 18:30 (T+30m) Point copiers, website forms, and ERP relays to authenticated Microsoft 365 SMTP or scoped TLS connectors Send live test scan and invoice; confirm headers show spf=pass and dkim=pass
Fri 20:00 (T+2h) Run first delta sync pass across all mailboxes (final 30 days of mail, calendar changes, contacts, folder states) Verify zero credential or throttling errors across batch logs; compare item counts per mailbox
Sat 10:00 (T+16h) Apply shared-mailbox permissions (FullAccess, SendAs) and executive calendar delegate permissions Log into OWA with delegate test account to confirm shared folder visibility and calendar edit rights
Sun 12:00 (T+42h) Run final sweep delta pass for straggler mail delivered to old MX before remote MTA caches expired; disable source user logins 100% of mailbox batches report completed with documented exception log under 0.05%

Endpoint Profiles, Monday Support, and Scope Boundaries

Finishing the server sync does very little good if people open their laptops at 8:30 AM Monday and Outlook is still trying to talk to the old server. Make sure the Scope of Work covers desktop Outlook profile cutover, autocomplete cache migration where needed, mobile Outlook setup guides, dedicated deskside or remote support on Monday morning, and a 14- to 30-day read-only hold on the retired mail server before anyone cancels the old subscription.

Just as important, spell out what belongs in the core email migration and what gets quoted separately so finance and IT are reading from the same page:

Deliverable Area Included in Core Email Migration SOW Scoped Separately When Needed
Mail, calendars, and contacts Server-hosted user mailboxes, shared mailboxes, room calendars, aliases, and distribution groups Local workstation .pst / .olm file discovery across unmanaged laptops or legacy NAS shares
Cloud file collaboration Target OneDrive provisioning and baseline tenant sharing controls Google Shared Drives / Dropbox / file-server permission restructuring and SharePoint information architecture
Endpoints and Office apps Supported Windows/macOS Outlook profile cutover, OWA verification, and iOS/Android mobile setup Unsupported OS upgrades, Office 2013/2016 replacements, or custom VBA/COM add-in refactoring
Authentication and security SPF, 2048-bit DKIM, baseline DMARC alignment, and standard Conditional Access MFA policies Third-party SaaS DKIM remediation across external marketing vendors or full Intune Autopilot enrollment

If you are planning a move off Google Workspace, hosted Exchange, IMAP, or an acquired company's tenant, take a look at our managed email and Microsoft 365 migration service along with our post-merger IT integration checklist.