Microsoft 365 Migration Checklist for Small Business

A Microsoft 365 migration moves your business email, calendars, contacts and files from an old system into Microsoft's cloud. Done well, your staff log in on Monday and everything is where they expect it. Done badly, mail goes missing for days, shared folders lose their permissions and someone discovers the old server held the only copy of last year's accounting files.

The difference is almost always the planning. TechBoss handles Microsoft 365 migration for businesses across Toronto and the GTA, and this checklist is the same order of work we follow. Use it to plan your own move, or to check that the provider you hire is covering every step.

It is written for owners, office managers and operations leads at small and mid-sized businesses, moving from an old email host, Google Workspace, an on-premise Exchange server or a file server in the back room.

Before You Start: Is Microsoft 365 the Right Fit?

Most businesses that already use Word, Excel and Outlook end up on Microsoft 365, because the desktop apps, email and file storage all work under one login. If your team lives in a browser and you are weighing your options, read our Microsoft 365 vs. Google Workspace comparison before you commit. The rest of this checklist assumes you have chosen Microsoft 365.

Phase 1: Inventory What You Have

You cannot move what you have not listed. Start with a full picture of your current setup.

• Users and mailboxes: every person, shared mailbox (info@, accounts@), distribution list and alias. Note the size of each mailbox.
• Former staff: mailboxes for people who have left. Decide whether to migrate them, convert them to shared mailboxes or archive them.
• Files: every place files live, such as a file server, local computers, Dropbox, Google Drive or USB drives. Note the total size and who uses each folder.
• Permissions: who can see and change each shared folder. This is the part most often lost in a rushed move.
• Domains and DNS: every domain you send email from, who hosts the DNS and who has the login.
• Devices: computers, phones and tablets that connect to company email, and whether they are company-owned or personal.
• Line-of-business apps: accounting, CRM or industry software that sends email, scans to a folder or connects to the old server.
• Printers and scanners: any that scan to email or to a network folder will need new settings.

Phase 2: Plan Your Microsoft 365 Migration

• Choose licences per person. Not everyone needs the same plan. Some staff need the desktop apps, some only need email and web apps. Matching the plan to the job keeps the monthly cost down.
• Decide what moves and what stays. Twenty years of email does not always need to come across. Agree on a cut-off, and archive the rest somewhere you can still search.
• Clean up first. Delete duplicate files, empty old folders and remove accounts nobody uses. Migrating clutter costs time and storage.
• Map files to the right home. Personal work files go to each user's OneDrive. Team and department files go to SharePoint sites or Teams. Draw this map before anything moves.
• Pick a migration method. Small offices often move everyone in one weekend (a cutover). Larger or more complex moves go in batches by team (a staged migration).
• Set the date. Choose a quiet period, avoid month-end or year-end, and tell staff well in advance.
• Write a rollback plan. Know what you will do if something fails during cutover, and keep the old system running until the new one is confirmed.

If the move is part of a bigger shift away from on-premise servers, our cloud migration checklist covers the wider project.

Phase 3: Prepare the Microsoft 365 Tenant

Your Microsoft 365 "tenant" is your company's own space in the Microsoft cloud. Set it up properly before any data arrives.

• Add and verify your domain so mail can be delivered to your real addresses.
• Create user accounts and assign licences, using the naming you agreed on.
• Turn on multi-factor authentication (MFA) for every account, starting with administrators. Our post on why MFA is non-negotiable explains why this step matters most.
• Limit admin accounts. Use separate admin logins for administration only, not for daily email.
• Set email authentication. Configure SPF, DKIM and DMARC records so your mail is trusted and harder to spoof.
• Create SharePoint sites and Teams to match your file map, with permissions set by group rather than by individual.
• Plan backup. Microsoft keeps your service running, but recovering deleted or overwritten data beyond its retention settings is your responsibility. Add a separate Microsoft 365 backup.

Phase 4: Migrate Email, Calendars and Files

• Lower the DNS time-to-live a day or two ahead so the mail record change takes effect quickly.
• Pre-stage the bulk of the data. Copy older mail and files ahead of time, then run a final sync at cutover so only recent changes move on the night.
• Switch the MX record to point incoming mail at Microsoft 365.
• Run the final sync to catch anything that arrived on the old system during the switch.
• Move files to OneDrive and SharePoint, keeping folder structure and permissions as mapped.
• Update connected devices and apps: scanners, printers, accounting software and anything else that sends mail.

Phase 5: After Cutover

• Set up Outlook, OneDrive and Teams on every computer and phone, and check each person can open their mail and files.
• Spot-check mailboxes and folders against the old system for missing items.
• Test sending and receiving from outside addresses, including shared mailboxes.
• Give staff a short guide: where their files went, how to share a file and how to join a Teams meeting.
• Keep the old system read-only for a set period, then shut it down and cancel the old service.
• Review licences after the first month and remove any you do not need.

Privacy and Data Location

If you hold personal information about customers or patients, you remain accountable for it under PIPEDA after it moves to the cloud. Know where your data is stored, who can reach it and how long you keep it. Some regulated industries or client contracts also require data to stay in Canada, which you can usually set when the tenant is created. Our PIPEDA compliance checklist has more detail. This is general information, not legal advice.

Common Microsoft 365 Migration Mistakes

• Moving files without mapping permissions, so everyone can suddenly see payroll.
• Forgetting shared mailboxes and aliases, so mail to info@ bounces.
• Leaving MFA off "until things settle down."
• Switching DNS on a Friday afternoon with no one available Monday morning.
• Shutting off the old server before anyone has checked the new one.
• Paying for top-tier licences for every user when most only need email.

What a Microsoft 365 Migration Costs

The cost depends on the number of users, how much data you have, where it is coming from and how many apps and devices need to be reconnected. A straightforward email move for a small office is a much smaller job than moving a file server, an on-premise Exchange server and several applications at once.

At TechBoss, larger cloud migration projects are priced at $2,500 to $15,000, and every project gets a fixed written quote after a free consultation. Microsoft licences are billed separately. Once you are on Microsoft 365, day-to-day admin (new users, licences, security settings) is included in our Professional managed IT plan at $89 per user per month, along with cloud backup and email security. See all prices on our pricing page.

How It Works with TechBoss

1. Free consultation: we look at your current email, files and systems and talk through what you need.
2. Migration plan and fixed quote: you get the inventory, file map, cutover date and a written price.
3. Tenant setup: we configure Microsoft 365 with MFA, email authentication, permissions and backup before any data moves.
4. Migration: we pre-stage your data, run the cutover and do the final sync.
5. Handover: we set up devices, check mailboxes and files with your staff and leave you with documentation. Ongoing admin is available through our managed IT plans.

We work with businesses in Toronto, Mississauga, Vaughan, Markham and across the GTA, and handle remote migrations for clients across Canada.

Frequently Asked Questions

How much does a Microsoft 365 migration cost in Toronto?

It depends on users, data volume and where you are moving from. TechBoss prices larger cloud migration projects at $2,500 to $15,000 and gives you a fixed written quote after a free consultation. Microsoft licences are separate.

Will we lose email during the migration?

Not if it is planned properly. Mail is pre-staged, the MX record is switched at a quiet time and a final sync picks up anything that arrived during the change. The old system stays available until the new one is checked.

Can we migrate from Google Workspace to Microsoft 365?

Yes. Mail, calendars, contacts and Drive files can all be moved to Microsoft 365. Shared drives are mapped to SharePoint sites so teams keep access to the same files.

Do we still need backup once we are on Microsoft 365?

Yes. Microsoft keeps the service running, but recovering data that was deleted, overwritten or encrypted by ransomware beyond its retention settings is your responsibility. Cloud backup is included in our Professional plan.

Can we keep working during a Microsoft 365 migration?

Yes. Most of the data is copied in the background while staff work as normal. The switch itself is scheduled for evenings or a weekend.

Plan Your Microsoft 365 Migration with TechBoss

TechBoss plans and runs Microsoft 365 and cloud migrations for businesses across Toronto and the GTA, with security and backup set up from the first day. Tell us what you are moving from and we will map it out and give you a fixed price. Request your free Microsoft 365 migration plan.