ALLMSP Blog

Prepare a Microsoft 365 Migration: Source, Method, and Pilot

Inventory mail, files and identities, check migration eligibility, prepare the target correctly, and test a representative pilot before scheduling cutover.

Employees validating Microsoft 365 email calendar identity and mobile authentication during rollout

Choose a Microsoft 365 migration method from the source and the work that must survive the move. An IMAP copy, an Exchange move and a cross-tenant move do not prepare recipients or transfer the same data in the same way. A mailbox migration is also not a promise that files, Teams, device profiles and application integrations have moved.

Use this guide to build the inventory, confirm method eligibility and target preparation, and accept a representative pilot. It ends with a readiness handoff. The separate Microsoft 365 cutover, validation and ownership guide covers the live change window, pause and rollback decisions, reconciliation and retirement.

Define what will move before choosing a migration tool

For each workload, answer these questions before buying a migration tool or promising a date. Microsoft’s setup guidance provides the tenant and service foundation; the source-specific procedure determines how the migration is prepared. [1]

  • Source and authority: Which tenant, server, account or file location actually holds the records, and who is authorized to administer and approve the move?
  • Required data: Which mail, calendars, contacts, archives, files, versions, permissions and history must remain usable? Record retained or excluded material explicitly.
  • Identity and recipients: Which identity source, addresses and target recipient objects does the method require? Check collisions before provisioning.
  • Business dependencies: Include delegated calendars, shared mail, app senders, scanners, external collaborators, mapped file paths and device profiles.
  • Constraints: Check current source support, tenant/cloud applicability, required licenses, permissions, holds, capacity and coexistence needs.
  • Acceptance: Name the tester, ordinary task, expected result, evidence and owner who can accept an exception.

Keep domain verification separate from the production routing change. Microsoft’s domain setup instructions call for users and mailboxes to be ready before MX is changed; confirm how the chosen method produces those valid recipients rather than creating a new mailbox indiscriminately. [2]

Choose the source-specific method and recipient preparation

Use the current detailed Microsoft procedure for the exact source and target. A general migration overview contains multiple paths and historical source examples; a listed source version is not a statement of its present support lifecycle. Do not pick a method solely from company size or a generic checklist. [3]

Source-specific method decisions to resolve before the pilot
Source or workloadPreparation decisionScope boundary to record
IMAP emailPrepare the supported source connection and existing target mailboxes using the IMAP procedure.Email-folder items are in scope; calendars, contacts and tasks need another approved path.
On-premises ExchangeConfirm the currently applicable move or hybrid prerequisites, identity design, recipient mapping and coexistence.Do not turn an old overview's server example into a supported-version recommendation.
Google WorkspaceUse the Google Workspace migration procedure and its target recipient and source permission requirements.Check the published mail, calendar and contact limitations; Drive files and other workloads are separate scope.
Another Microsoft 365 tenantCheck cross-tenant licensing, both organizations' permissions and the required target MailUser attributes.Do not pre-create a conflicting mailbox or assume a tenant-to-tenant mailbox move transfers every service.
File sharesMap owners and destinations, scan the source and inspect assessment logs before moving content.A successful scan does not prove permissions, application paths or user acceptance after migration.

Microsoft’s IMAP guidance makes the data and target-mailbox limits explicit. Its Google Workspace procedure is a different path with its own prerequisites and limitations; the two should not be treated as interchangeable. [6] [7]

For cross-tenant mailboxes, verify the current target-object and licensing instructions before provisioning. Microsoft warns that prematurely provisioning a target mailbox can conflict with the required object state. Holds and other stated restrictions also need a responsible disposition; this guide is not an instruction to clear them. [8]

For a file share, download the assessment reports and investigate blockers. Map the intended destination and actual business use before relying on a scan summary. [9]

Turn inventory exceptions into a representative pilot

This fictional 24-person company uses an IMAP email service, local calendar/contact data and a departmental file share. Six pilot users are chosen to cover its difficult workflows; six is an illustrative choice, not a recommended percentage. The pilot exposes missing scope rather than proving the move is ready.

Illustrative pilot scope and readiness record
WorkloadWhat the pilot revealsPreparation decision
Email foldersThe selected pilot mailboxes can use the planned IMAP connection and target mapping.Review migration errors and scoped mail samples. Do not extend that result to other data types.
Calendars and contactsThose required records are outside the IMAP migration scope.Hold workload acceptance until an approved separate method and representative validation are documented.
Departmental filesA business application still expects the old mapped path even though sample documents open in the new location.Assign the application owner a supported path/change decision and repeat the actual task.
Application mailThe invoice sender has no verified current sending method or accountable maintainer.Keep a named blocker. Verify the supported Microsoft 365 sender design and test the actual application identity.
Pilot decisionMail-copy progress is visible, but calendar/contact and application acceptance remain incomplete.No cutover date is approved from this pilot. Owners must resolve or explicitly accept the bounded exceptions.

Have ordinary users perform the complete task, and include difficult delegation, shared-resource, remote-device and accessibility cases where they exist. Record source identifiers, target location, expected and observed results, tool warnings and the person who accepts each result. Do not replace failed evidence with a technician’s verbal assurance.

Record readiness and hand a prepared scope to cutover

A batch status is useful telemetry, not a release decision. Microsoft notes that Synced can include errors; keep the affected user and item detail, correction or exclusion decision and business acceptance separately. [4]

Estimate transfer and validation effort from the representative pilot and current source/tool constraints. Volume, source performance, network conditions, throttling, errors and ongoing changes can affect duration. Explain the assumptions and a range; do not publish an invented universal transfer rate or a zero-interruption promise. [5]

  • Versioned inventory: every required workload has a source, target, owner and disposition.
  • Method eligibility: applicable current procedure, permissions, license and target-object preparation are recorded.
  • Pilot acceptance: representative tasks and exceptions have evidence and responsible approval.
  • Recovery limits: state what the method preserves, moves or removes and what a fallback would require.
  • Handoff: provide the cutover lead with exact scope, critical tests, staffing, communications and unresolved decisions.

Before switching email routing, use Validate Exchange Online Mailboxes, Domains, and Routing Before Cutover for recipient, accepted-domain and real sender-path checks. Once preparation is accepted, continue to Microsoft 365 cutover, validation and ownership for the live decision gates and retirement plan.

Microsoft 365 migration preparation with ALLMSP

ALLMSP can assess the source, design the target, check Microsoft 365 licensing and identity, select migration methods, prepare users and devices, and run representative pilots for Georgia businesses. The useful output is an owned, tested scope with explicit exclusions and recovery limits, not simply a date in a calendar.

Use ALLMSP Microsoft 365 services to coordinate implementation and continuing support, or cloud computing and migrations when the project includes other systems. Keep preparation, cutover approval and operating acceptance as distinct responsibilities even when one team performs the technical work.

Microsoft references for migration scope and eligibility

Use Microsoft documentation to confirm current tenant, domain, and migration behavior, then adapt the plan to the source platform, business workflows, data, security, and acceptable downtime.

Microsoft 365 migration planning FAQs

What should be inventoried before choosing a Microsoft 365 migration method?

Record the actual source platform, version and support state, identities, domains, mailboxes, aliases, delegates, calendars, contacts, archives, files, permissions, devices and application senders. Give each workload an owner, required history, target location, proposed method and acceptance test. Identify legal or retention restrictions and anything outside the tool’s scope. A mailbox count alone cannot choose the migration method or establish that the entire working environment will move.

How should the Microsoft 365 migration method be chosen?

Match each workload to the current Microsoft procedure for its source, required data, coexistence, identity design, licensing and target preparation. Exchange, IMAP, Google Workspace and cross-tenant moves have different prerequisites and limitations; files can require a separate assessment and migration path. Document why the method is eligible and which data it excludes. A method named in a general overview is not proof that an old server version remains supported.

Does IMAP migration move calendars, contacts and files?

Microsoft’s IMAP migration moves items in email folders, not calendar items, contacts or tasks. It also does not create the destination mailboxes. Inventory archives, local data and files separately rather than assuming they follow the mailbox. Assign an approved method and validation plan for each required excluded workload before the pilot can be accepted.

Should every migration start by creating a new target mailbox?

No. Target recipient preparation depends on the method. IMAP requires an existing destination mailbox, while Microsoft’s cross-tenant mailbox procedure requires a correctly prepared MailUser and specific matching attributes before licensing and moving the user. Creating a conflicting mailbox too early can cause a problem. Follow the chosen method’s current order; domain verification and having valid recipients before MX cutover are separate readiness decisions.

What should a Microsoft 365 file-migration assessment cover?

Map each source location to its intended SharePoint, OneDrive or other approved destination and owner. Review scan and assessment reports, permissions, identity mapping, blocked items, paths, versions, sharing links and applications that depend on the old location. Record what the selected tool preserves and what needs a separate action. An assessment report identifies migration issues; an ordinary-user pilot must still prove the required access and workflow.

Who should be included in the Microsoft 365 pilot?

Choose users and resources that expose the difficult cases: delegation, shared mail, mobile or remote work, large or unusual data, external collaboration, accessibility needs and business applications. Include the actual application-sender identity and file owners as well as people. Define the expected result for each case before testing, and retain the failures that change the plan. Do not select only small mailboxes or the most technically confident employees.

Does a Synced migration batch mean the pilot is ready for cutover?

No. Microsoft documents that a Synced batch can contain errors. Inspect the relevant batch and item reports, compare approved source and target scope, and test ordinary-user work such as calendar access, shared resources and required files. Keep technical synchronization, corrected defects, accepted exclusions and business acceptance as distinct statuses. The pilot is ready only when the responsible owners accept the defined results and remaining exceptions.

How can migration duration be estimated without guessing?

Measure the representative pilot by workload and include source constraints, throttling, network capacity, retries, errors, incremental changes and validation effort. Use Microsoft’s performance guidance to understand the factors, then document assumptions and a range rather than promising one mailbox-per-hour rate. The estimate should distinguish data transfer from employee preparation, testing, cutover and stabilization. A small easy mailbox is not a reliable proxy for every user.

What if required data is excluded or a migration is blocked?

Keep the item in a decision register with its owner, business or retention requirement, the documented limitation and an approved disposition. Choose a supported additional method, change the scope with responsible approval or hold the affected workload. Do not remove a legal hold or silently discard required history to make a batch succeed. Test the approved alternative and preserve the evidence before declaring the pilot complete.

When is the migration plan ready for a cutover runbook?

Each in-scope workload needs a known source and target, an eligible method, correct recipient and identity preparation, a representative pilot result and a named owner. Required exclusions, recovery limits, timing assumptions, support coverage and acceptance criteria must be understood. Hand that versioned scope to the business decision owner and cutover lead; schedule the actual change only after they accept its readiness and consequences.

Sources
  1. Plan Microsoft 365 setup for business. Introduces tenant setup, domains, users, subscriptions, applications, and migration preparation. ↩
  2. Add a custom domain to Microsoft 365. Explains domain verification, required DNS records, and why mailboxes should exist before MX cutover. ↩
  3. Microsoft 365 mailbox migration options. Compares supported migration paths for Exchange, IMAP, Google Workspace, and other source environments. ↩
  4. Manage Exchange Online migration batches. Covers creation, synchronization, status, errors, completion, and management of mailbox migration batches. ↩
  5. Microsoft 365 migration performance. Provides planning guidance for migration throughput, workload behavior, throttling, duration, and scheduling. ↩
  6. IMAP migration scope and preparation. Explains mail-folder scope, excluded calendars/contacts/tasks and existing target-mailbox preparation. ↩
  7. Google Workspace migration to Microsoft 365. Documents source preparation and the supported mail, calendar and contact path with workload-specific limitations. ↩
  8. Cross-tenant mailbox migration prerequisites. Documents MailUser preparation, required attributes, licensing, holds and source-mailbox behavior for this method. ↩
  9. Scan and assess file shares with Migration Manager. Explains file-share assessment reports and logs used to investigate potential migration blockers. ↩
Facebook
LinkedIn
WhatsApp
X
Email
Print
Threads
Reddit

Latest Articles