Microsoft 365 migration checklist: what should a small business prepare?
Before moving to Microsoft 365, list your accounts and data, identify who owns them, agree what will move and test a representative sample. Plan the change around your working week, then check that people can do their jobs before retiring the old setup.
That is the purpose of this Microsoft 365 migration checklist: to help an owner or office manager prepare a clear brief for the person doing the technical work.
Start with the things that would cause trouble if they were missing on Monday morning: incoming enquiries, appointments, current job files and the software people use to serve customers.
1. Agree what is moving
“Move us to Microsoft 365” can hide several different jobs. Work through these separately:
Email: individual accounts, shared addresses, aliases and older messages people still need.
Calendars and contacts: including shared diaries and appointments others manage.
Files: current work, archives, templates and restricted business records.
Connected services: website forms, scanners or applications that send mail, and software linked to existing accounts or folders.
Your business domain: who controls the domain name and its DNS settings, which help direct services such as email.
For each item, record whether it is moving, staying where it is or awaiting a decision. Include data stored on individual computers if people depend on it.
The source system and migration method affect what transfers. For example, Microsoft's email migration guidance says an IMAP email migration does not transfer contacts, calendar items or tasks. Your provider should explain how anything outside the chosen method will be handled.
Ask about permissions, shared access, file links and any history you need to preserve. Put an unanswered question on the list rather than treating it as included.
2. Microsoft 365 migration checklist: your planning record
Use one entry for each important system or collection of data. Copy these fields into your planning document:
System or data set: ______
Business owner and cover person: ______
Current service and location: ______
Proposed destination: ______
Must-keep information and date range: ______
Who needs access, and what level: ______
Connected apps or dependencies: ______
What is excluded or still undecided: ______
Acceptance check, checker and planned date: ______
Result, unresolved issue and action owner: ______
Keep passwords and recovery codes out of this record. Note who can arrange authorised access, then let the provider agree a secure way to obtain what they need.
Here is a hypothetical entry for a small maintenance business: “Active jobs; office manager; current shared drive; proposed Operations SharePoint library; retain the agreed job folders; office team can edit; engineer access to be confirmed. Acceptance: the office manager opens a recent job sheet, updates a test copy and checks the engineer's approved access.”
That gives someone a specific test to perform. Add separate entries for email and calendars so they receive their own checks.
3. Decide how the new setup should work
Name a business decision-maker and an authorised technical lead. The business decides what work must continue, who should see information and which dates are unsuitable. The technical lead checks the migration method, access requirements, dependencies and likely limitations.
Agree the target file structure before copying everything. Our OneDrive vs SharePoint guide helps distinguish individual working files from shared team documents. Keep that decision simple enough for staff to follow.
Review licences against actual tasks, devices and security requirements. Our Business Basic, Standard and Premium comparison is a starting point; confirm the current options with whoever manages your subscription.
Also agree sign-in protection, administrative responsibilities and how staff will receive their new sign-in instructions securely. Check the recovery arrangements for important data. Record any retention requirements for the business and provider to address before changing or cancelling existing services.
Microsoft's setup planning guidance covers people, domain access, email, files and connected software. Having those answers ready makes the scope much clearer.
4. Test a small move and plan the changeover
Ask the provider to propose a pilot: a controlled test using a suitable account or set of files. Choose work that reveals real requirements, with sensible safeguards for anything customer-facing.
Have the people involved try their usual tasks and record problems. Microsoft's SharePoint and OneDrive rollout guidance recommends a pilot, defined success criteria and a way to collect feedback before a wider rollout.
Use what you learn to agree the changeover window. Avoid assuming that Friday evening is convenient: some businesses are busiest over the weekend.
The plan should answer:
When should staff stop making changes in the old location?
Where should they work during the move?
How will new messages or changed files be handled?
Who can approve proceeding, delaying or stopping?
Who handles problems during the move and the next working day?
Ask the provider to explain the contingency or rollback options, their limits and the point at which returning to the old setup becomes more complicated. Tell staff what changes, when it changes and how to get help if their usual email is unavailable.
5. Check the business can work
After the move, use the acceptance checks in your record. Ask named people to confirm:
They can sign in using the agreed security method.
Work email sends and arrives, including relevant shared addresses.
Calendars, appointments and contacts are available as agreed.
Representative files open, save and can be found in the right place.
Approved colleagues have the access they need, with restricted areas still restricted.
Key business applications and connected workflows work as expected.
Log anything missing, who owns the fix and its impact on work. Keep the old service available for the agreed period while checks and outstanding decisions are completed. Retention, cancellation and deletion need explicit business approval and an authorised administrator's checks.
Ready to scope your migration?
You have a useful starting brief when you can name the systems, data owners, must-keep work, unresolved questions and dates to avoid. The provider can then establish the technical scope and plan the move with you.
Cache4's Microsoft 365 service includes setup, migration of existing email and relevant files, training and ongoing management, with the work agreed around your needs.
Book a free 30-minute Discovery Call with Paul. Bring your current services and one example of work the move must preserve. We'll talk through what you want to change and whether we can help.
Comments