Microsoft 365 Migration Guide

Build the schedule from discovery and a representative pilot, not a fixed number of weeks. Source access, transfer limits, errors, client changes, and business approval all affect elapsed time. Record the operating window and stop conditions before the final move.

Phase 1: Assessment and planning Inventory the source platform, data, identities, licensing, applications, and required access. Agree included workloads and exclusions.

Phase 2: Pilot and pre-staging Where supported, test representative content and access before transferring larger batches. Record errors and unsupported items.

Phase 3: Cutover Use an approved window, named decision-makers, readiness evidence, user communications, and documented fallback decision points.

Phase 4: Verification and support Check the acceptance criteria with the business owner. Record unresolved exceptions, support responsibilities, and source-system retention before approving decommissioning.

Cutover is more than an MX record change. Account readiness, mail routing, DNS, synchronisation, connected applications, and client access need separate checks. Agree the expected disruption window and fallback options; background copying alone does not prove that every message is present or that users can work.

Outlook and mobile mail apps may need account, profile, authentication, or device changes. Test representative clients and document supported versions, user instructions, and support contacts. Do not assume automatic reconnection or a fixed number of minutes per device.

Review migration logs, failed or skipped items, and representative destination access against the acceptance criteria. Counts are one check, not proof that content, permissions, and workflows are equivalent. Keep unresolved exceptions visible and agree source retention before decommissioning; a successful job status is not a no-data-loss guarantee.

Migration methods have different coverage. Microsoft's IMAP migration transfers mail-folder items, not contacts, calendar items, or tasks. Confirm separate methods for other required data using the Microsoft IMAP migration limitations as a starting point.

For Google Workspace, inventory Gmail, Calendar, contacts, Drive files, sharing, and any scripts or integrations separately. Test representative conversions and permissions using the selected method. Do not assume document formatting, automation, or every Google feature will transfer unchanged.

Teams configuration and any required Teams-content migration need their own scope. Decide the target structure, guest access, permissions, and required content, then verify a representative workflow. A completed mailbox migration does not establish that collaboration work is complete.

Can we migrate over a weekend to minimise disruption? A weekend or low-traffic window can be considered after readiness checks. Confirm the authorised contacts, expected disruption, final verification, and fallback decision points. Do not assume the remaining work is only a DNS change.

What if we have a lot of old email? Inventory archives and retention requirements before choosing a method. Historical volume, source limitations, and failed items can affect timing and availability. Agree priority data and verification evidence rather than promising every archive will be accessible at cutover.

Do we need to buy new hardware? Assess the devices, operating systems, client versions, and security requirements used by your team. A representative pilot should identify unsupported configurations or required changes. Hardware replacement is a discovery decision, not an automatic requirement or an automatic exemption.

What licences do we need? Match licensing to destination workloads, installed applications, security controls, and migration tools. Conditional Access requires appropriate licensing. Confirm the selected plan and any additional costs before approving the scope; a mailbox entitlement alone does not establish entitlement to every control.

Can North Star run our Microsoft 365 migration? North Star can assess and scope a migration for businesses across Northern BC, Alberta, and Yukon. Agree supported workloads, security configuration, acceptance criteria, support duration, and handoff responsibilities before scheduling changes.

Planning a Microsoft 365 migration? Call 672-983-1174 to discuss the source environment and required outcomes. Check Microsoft's Conditional Access licence requirements when planning access controls.