
A Microsoft 365 migration checklist is not simply a technical to-do list. It is the plan that prevents a Monday morning where staff cannot find shared files, customers receive bounced emails, or an old employee account still has access to company information. For a growing business, the migration needs to protect day-to-day work while putting better control around the systems people rely on.
The right approach depends on what you are moving, how much data you hold, and whether you are replacing wider IT systems at the same time. A small business moving email from an older hosted service has different needs from a multi-site organisation bringing files, devices and identities into Microsoft cloud services. The principle is the same: understand the current position, make clear decisions before moving data, test properly, and keep ownership visible throughout.
Microsoft 365 migration checklist: start with the business
Before licences are assigned or mailboxes are copied, agree what the migration is meant to achieve. It may be improved remote working, safer file sharing, replacement of ageing servers, support for a new office, or better device control. Setting this out prevents a migration becoming a like-for-like move that carries old problems into a new platform.
Identify a business owner for the project and a technical lead with authority to make decisions. They should agree the scope, timetable, success measures and what is outside the project. For example, are you moving email and calendars only, or also Teams, SharePoint files, personal OneDrive data, mobile devices and security policies?
At this stage, map the people and systems affected. Include office-based, remote and frontline staff; shared mailboxes; meeting rooms; generic accounts; directors; temporary staff; and third parties with access to company data. Also record applications that send email, such as finance systems, website forms, scanners, CRM platforms and alarm systems. These are often missed until after the switch.
Audit what you have before choosing what to move
A good audit reduces cost and avoids unnecessary disruption. Review your current email domains, mailboxes, distribution groups, shared mailboxes, contacts, calendars and archive requirements. Establish how much data exists, where it sits and whether there are legal, contractual or retention obligations that affect it.
File data needs particular attention. Shared drives commonly contain years of duplicated, out-of-date or poorly organised documents. Moving everything may be appropriate where retention requires it, but it can also recreate a confusing filing system in SharePoint or Teams. Decide which active files should be migrated, what should be archived, and what can be securely removed under an agreed retention approach.
Use the audit to identify permissions that no longer make sense. If everyone can access a finance folder because that was the easiest workaround five years ago, moving it without change preserves the risk. Microsoft 365 gives you a chance to apply sensible access based on roles, teams and business need.
Choose licences and design the target environment
Licence selection should reflect how people work, not just the lowest price per user. Some staff may need desktop Office applications, larger mailboxes or advanced security capabilities; others may only need web and mobile access. Consider shared-device users, kiosk-style roles and staff who rarely use email. The right mix controls ongoing cost without limiting the tools employees need.
Design the Microsoft 365 environment before creating users at scale. Agree naming conventions for Teams and SharePoint sites, who can create new groups, how external sharing will work, and who owns each workspace. Without this structure, Teams can quickly become difficult to navigate and sensitive information can be shared too widely.
Security settings belong in the initial design, not a later improvement phase. At a minimum, plan multi-factor authentication, conditional access rules where appropriate, secure administrator accounts, anti-phishing protection, mobile device requirements and logging. The exact controls depend on your risk profile, workforce and compliance obligations. A financial services business, for example, will usually need more formal controls and evidence than a small professional services firm.
Prepare identities, domains and access
Every user needs a clear identity and a predictable sign-in process. Clean up duplicate accounts, confirm correct names and email addresses, and decide whether user accounts will be created directly in Microsoft 365 or synchronised from on-premises Active Directory. Synchronisation can be useful where an existing directory remains in place, but it adds dependencies that should be understood and maintained.
Verify the company’s email domains in advance and document who has access to the domain registrar and DNS records. A migration can be delayed unnecessarily if nobody can make the required changes to mail records. Record existing DNS settings before amending them, including those used by website, email marketing and third-party services.
Set up a small group of administrator accounts with strong protection and documented responsibilities. Avoid relying on one individual’s personal account as the only route into the tenant. Businesses need continuity if a member of staff is unavailable or leaves.
Move a pilot group first
A pilot is where the migration plan meets real working practices. Choose a representative group rather than only technically confident staff. Include people who use shared calendars, mobile devices, large mailboxes, Teams meetings and shared files. Their experience will show where guidance or configuration needs improving.
Test the full journey: signing in, resetting a password, using multi-factor authentication, sending and receiving external email, accessing shared mailboxes, joining Teams calls, opening key documents and working from home. If you are migrating files, check permissions as well as content. A document that arrives intact but cannot be opened by the right team is not a successful migration.
Use the pilot to validate timings. Mailbox migration speed, internet capacity and the volume of file changes during the move can all affect the cutover plan. For some businesses, a staged migration is the lower-risk route. Others may need a planned out-of-hours cutover to reduce the period in which systems are split between old and new platforms.
Communicate clearly before cutover
Staff do not need a technical explanation of DNS records. They need to know what is changing, when it will happen, what they must do, and where to get help. Send communications early enough for people to prepare, then repeat the practical instructions closer to the migration date.
Explain whether users will need a new password, multi-factor authentication app, device update or Outlook profile. Give separate guidance for Windows PCs, Macs and mobile phones if relevant. Short, role-specific instructions are more useful than a long generic document.
Managers should know how business continuity will be handled. Confirm the support route, expected response arrangements, planned downtime if any, and what staff should do if they cannot access email or files. Clear ownership keeps small issues from becoming wider operational disruption.
Cut over with checks, support and a back-out plan
On migration day, work through an agreed runbook rather than relying on memory. This should cover the sequence of technical tasks, responsible person, decision points, contact details and checks needed before declaring the move complete. It should also define the back-out plan. Not every issue requires reversing the migration, but the team needs to know what threshold would trigger that decision.
Once email routing changes, monitor message flow closely. Test internal and external email, shared mailboxes, forwarding rules and sending from business applications. Check priority users first, including directors, finance, customer service and teams that work with time-sensitive information.
Keep users informed during the change, even when progress is on plan. A simple update gives people confidence that the work is controlled and tells them when to start using the new service. Provide visible support for the first working day, when questions about Outlook, mobile access and file locations are most likely.
Complete the Microsoft 365 migration checklist after go-live
Go-live is not the end of the work. Review the migration against the agreed success measures and resolve exceptions while they are still visible. Confirm all expected mailboxes and data have moved, permissions are correct, licences are assigned appropriately, and old services are not still being used by accident.
Then turn the new environment into an operating service. Document administration processes, onboarding and offboarding steps, backup arrangements, security alert ownership and how changes to Teams or SharePoint will be governed. Microsoft 365 includes retention and recovery options, but they are not a substitute for deciding how the business will protect and restore critical information.
Finally, ask staff what has improved and where friction remains. If users are still emailing documents back and forth or saving files locally because they do not understand Teams, the technology has been installed but not fully adopted. Focused follow-up guidance can make a greater difference than adding more tools.
A well-run migration gives your business more than a new email platform. It creates a clearer, safer way for people to work. Plan the change carefully, give employees practical support, and keep responsibility defined from the first decision through to everyday use. Your IT should feel taken care of, not handed over to chance.



