Skip to main content

Operational guide · ngo · Global

Mailbox migration acceptance checklist

Verify mailbox scope, access, folder samples, delivery and exceptions before retiring old mail service. Separate copied mail from calendars and contacts.

This is an educational operational guide, not a customer testimonial or a report of measured customer results. Editorial review: .

A mailbox migration is complete when the organization verifies the agreed data and working mail flows, not when a transfer tool displays a green progress bar. Define what will move, how exceptions will be handled and who can approve retirement of the old service. This guide describes acceptance checks; it does not claim that a particular organization moved a measured volume without loss.

Establish the migration inventory

List active people, shared addresses, aliases, groups, forwarding rules and application senders. Identify former staff accounts that remain subject to a retention decision. Record which service owns each address and who can authorize changes.

Separate email messages from contacts, calendars, tasks, permissions and archives. A method that copies mail does not necessarily transfer every collaboration feature. The Microsoft mailbox migration documentation distinguishes migration approaches and prerequisites; choose the destination's supported process for your actual source.

Estimate data volume and identify large items, unusual folders, unavailable credentials and access restrictions. Treat these as scoped exceptions rather than discovering them after a public cutover date has already been promised.

Agree what counts as accepted

Define representative checks before starting. Include older and recent messages, attachments, sent mail, folder hierarchy and shared workflows. Establish how the team will investigate discrepancies and who signs off each mailbox.

Message counts can be useful signals, but a single count is not a complete integrity proof: tools may handle folders, duplicates or excluded items differently. Preserve migration logs and check the actual items that matter to the agreed scope. Do not claim "zero loss" without a defensible reconciliation method.

Protect accounts during the move

Use the least access needed for the selected migration method. Keep credentials and recovery details out of spreadsheets distributed to the whole organization. Decide when temporary access will be revoked and which logs the technical team may retain.

Keep destination administrative recovery under organizational control. Confirm that staff can use the intended clients and that shared access does not require circulating one person's password. Have an explicit route for reporting missing information or unexpected delivery.

Validate delivery separately from copied history

Historical copying and new-message routing are different tasks. Before changing MX records, create the destination accounts and configure the provider's required domain and authentication records. Preserve the existing DNS configuration and document the authority responsible for changing it.

Test sending and receiving with controlled accounts, including an external recipient and an external sender. Check replies, aliases and application-generated messages. The Google email sender guidelines explain authentication and delivery expectations for mail sent to Gmail; satisfying authentication does not guarantee inbox placement everywhere.

Allow for DNS caching and messages still arriving at the old service. A documented synchronization and exception window is safer than assuming every sender changes destination immediately. Monitor both services according to the agreed plan.

Retire the old service deliberately

Do not cancel the old account merely because DNS now points elsewhere. First resolve transfer exceptions, verify critical mailboxes, confirm user access and retain required records in an approved location. Establish whether the old service contains data outside the migration scope that still needs a decision.

Record acceptance by mailbox or accountable group, outstanding limitations, the final synchronization time and the retirement authorization. A technical operator should not independently decide the organization's retention or legal obligations.

Choose the next action

Use the business email setup guide for domain ownership and authentication planning, and compare current email services for the actual available products and scope. Request migration scoping before scheduling a move whose data, permissions or retention requirements remain uncertain.