Agree what must arrive
Silent video.

[0–6]
Inventory the work • Mail, calendars, contacts and shared access are separate. • Messages • Calendar • Contacts • Acceptance • Shared access • Name the task owner
Mail, calendar and contact paths lead to a separate human acceptance decision in the approved illustration. Shared access is a separate requirement: an alias, group, delegated account and shared inbox may behave differently. Name the business task owner and source-to-target arrangement rather than counting visible addresses as separately licensed mailboxes. Record administration, data, client, sender and retention needs without exposing passwords or message contents.

[6–12]
Check the chosen method • A mail-only path does not move every object. • Messages • Mail-copy route • Calendar events • Check supported path • Contacts • Check required fields • Mail-only coverage leaves other requirements open
Only the message row traverses the illustrated mail-copy path. Calendar and contact requirements remain open until their actual source-to-target method and required fields are checked. A mail-only method does not move calendars, contacts, permissions or every setting. Agree a supported alternative, explicit recreation or an owner-accepted exclusion; prepare destination users and the authorised access path separately.

[12–18]
Run a representative pilot • Example: 8 messages, 2 events and 2 contacts. • 8 messages • 2 events • 2 contacts • 12 agreed objects • 8 copied messages • 4 non-mail objects still open
The article’s invented pilot contains exactly eight messages, two events and two contacts. The approved picture marks only the eight messages copied; the four non-mail objects and overall acceptance remain open. This is a representative planning sample, not a provider report, client result or proof that a whole mailbox is complete. Check the specified objects in the actual clients and required fields.

[18–24]
Review exceptions and tasks • Completed import status is not final acceptance. • Import complete • Item exceptions • User tasks • Accept or resolve • Read each exception • Try the agreed user tasks
A completed import branches to item-level exception review and observable user tasks before accept-or-resolve. A skipped item is not automatically lost mail: use the chosen tool’s definitions and investigate relevant errors, warnings and differences. Find agreed old messages, open attachments, reply from the correct address, inspect invitations and verify contact fields. Do not suspend required retention merely to match totals.

[24–30]
Close on evidence • Verify late mail, access and agreed closure conditions. • Keep source access • Named closure reviewer • Late-mail evidence • Late mail · shared access · retention · agreed closure
The source remains accessible while late-arrival evidence reaches a named closure reviewer. Verify late mail, shared access, connected senders, retention and operating responsibilities against agreed conditions. MX directs new incoming mail and does not copy history. Keep a method-specific reconciliation record; one test message or a generic waiting period does not authorise deleting the source.