Skip to content

New: How We Design Technology - our seven-layer architecture model, explained in full. See the architecture

general

Why Microsoft 365 Migrations Fail: Mistakes Small Firms Make

11/04/2026

It's 7:40 on Monday morning. The migration ran over the weekend, and the tool reported every mailbox as complete. Then the calls start. The scanner by the front desk can't send to email. Two partners can't see the shared calendar. A project folder looks empty to half the team, and the office manager's Outlook keeps asking for a password. All of it lands on your desk at once, with the whole company waiting.

Most Microsoft 365 migration failures come from a short, predictable list of reasons, and very few involve the migration tool. They come from things nobody inventoried, permissions nobody mapped, and a cutover with no way back. Because they're predictable, you can catch most of them weeks ahead.

At a glance

  • Most failed cutovers trace back to gaps in discovery: shared mailboxes, devices that send email, deep folder paths, and permissions nobody wrote down.
  • Run a pilot with clear pass criteria, and decide in advance what would make you stop and roll back.
  • Treat DNS, licensing, sign-in changes, and user communication as part of the migration plan from the first week.

Microsoft 365 migration failures usually start in discovery

Migration tools move what you point them at. They won't tell you about the warehouse label printer that emails shipping confirmations, or the accounting system that sends invoices through the old mail server. Discovery is where you find those things, and it's the step most often cut short. Before you pick a date, write down:

  1. Every user mailbox, shared mailbox, room or equipment calendar, and distribution list, with sizes.
  2. Every file share, its size, its owner, and which departments depend on it.
  3. Every device or application that sends email, including scanners, copiers, alarm panels, and line-of-business software.
  4. Who controls DNS and the domain registrar, and whether anyone still has the login.
  5. Which licenses each person needs, based on the apps they use every day.

The inventory becomes your migration plan. Anything missing from it tends to surface as a help desk ticket on Monday.

File migrations break on permissions and paths

Permissions that only worked on the old server

File server permissions grow for years. Someone gets direct access to a folder for one project, groups get nested inside groups, and an old "Everyone" entry quietly opens a folder that should have been restricted. Nobody notices because nobody looks closely.

SharePoint and Teams organize access around sites, team membership, and sharing links. Copying folders one for one either recreates the old mess or breaks access in the middle of someone's deadline. Map access by role and department instead. Decide which groups need which sites, have the owners of sensitive folders such as HR and payroll approve the result, and test with one real user from each group before cutover. Write those decisions down, and the migration becomes a chance to clean up access for good.

Names, paths, and sync limits

Microsoft documents a list of restrictions for OneDrive and SharePoint. Some characters, including the colon, question mark, quotation marks, and pipe symbol, aren't allowed in file or folder names, and neither are leading or trailing spaces. Certain names are blocked outright, such as CON, PRN, AUX, desktop.ini, and anything that starts with a tilde followed by a dollar sign. Path length limits also apply and vary by app, and client folders nested eight or ten levels deep can run past them.

Sync has practical limits too. For the best performance, Microsoft recommends keeping the total under 300,000 items across your cloud storage and notes that problems can appear above that number. Telling everyone to sync a whole department library is a reliable way to get slow laptops and sync errors in the first week. Run a pre-migration scan, fix names and flatten deep paths before you move anything, and give people shortcuts to the folders they use.

Shared mailboxes, calendars, and devices that send email

Shared mailboxes such as info@ and billing@, room calendars, and delegate access are easy to overlook because nobody thinks of them as users. They still need to be rebuilt with the right permissions and tested by the people who rely on them. An executive assistant who manages two calendars will find a missing delegate permission within minutes.

Devices and applications that send email deserve their own line in the plan. Microsoft describes several ways to connect them:

  • SMTP AUTH client submission sends through a licensed mailbox using its credentials and can reach internal and external recipients.
  • Direct send delivers only to recipients in your own Microsoft 365 domains and rejects external addresses.
  • SMTP relay through a connector authenticates with a certificate or a static public IP address and doesn't need a licensed mailbox.

Two details catch small firms off guard. SMTP AUTH is turned off by default for organizations created after January 2020, so a new tenant can leave the scanner silent until someone enables it for the right mailbox. Microsoft has also announced that it's retiring Basic authentication for SMTP AUTH client submission, and the timeline has shifted more than once, so a copier that signs in with a plain username and password may work after cutover and stop later.

Check what each device supports, move to modern authentication or a connector where you can, and test every one before the MX record changes.

Cutover timing: DNS, licenses, and sign-in

Mail keeps flowing to the old system until the MX record changes. Lower the record's time to live a few days ahead, schedule the switch for a quiet window, and plan a final sync to catch messages that arrived while DNS caught up. Microsoft's cutover guidance also lists creating the Autodiscover DNS record as a post-migration task. When that record is missing or still points at the old server, Outlook can keep looking in the wrong place, which users experience as endless password prompts.

Size the method to the job. Microsoft notes that an Exchange cutover migration can move up to 2,000 mailboxes but recommends 150 or fewer, because creating and migrating users takes time. Large mailboxes take longer than people expect, so start the bulk copy early.

Microsoft's documentation also reminds admins that licenses still have to be assigned to migrated users. Decide plans by role before the weekend, so nobody finds out on Monday that their account lacks the desktop apps they use all day.

Then there's sign-in. Turning on multifactor authentication the same morning everyone meets a new mailbox doubles the confusion. Enroll people in MFA during the pilot, or schedule it as its own step a week or two later. Either approach works. Rolling both out at once rarely does.

No pilot, and no way back

A pilot group catches what discovery missed. Pick five to ten people across departments: someone with a huge mailbox, someone who lives in shared calendars, someone who scans to email, an executive assistant, and at least one skeptic. Run them on Microsoft 365 for a week with clear pass criteria. Mail flows both ways. Shared mailboxes open. Files sync. Phones connect. The line-of-business app sends its messages.

The bigger mistake is a cutover with no rollback gate. Once the MX record moves and the old server is wiped, every problem has to be fixed forward under pressure. Before the cutover weekend, write down:

  1. The conditions that would make you stop, such as mail flow failing or a critical app unable to send.
  2. Who makes the go or no-go call, and the deadline for making it.
  3. The exact steps to point mail back, and what happens to messages received in the meantime.
  4. How long the old system stays intact after cutover, and who signs off before it's decommissioned.

At CTP, we build that gate into every migration plan. Leadership approves a project more readily when they know it can stop safely, and the person running it sleeps better too.

Training that arrives too late

People forgive a lot when they know what's coming. A week before cutover, send a short note on what changes, what stays the same, when it happens, and who to call. On the first morning, hand out a one-page quick reference covering sign-in, where files moved, shared mailboxes, and phone setup, and walk the floor that day.

Teams deserves its own plan. Without channels, naming conventions, or guidance on what goes where, the same files end up living in three places. If Teams is part of your move, our notes on configuring Teams so people adopt it cover the setup choices that matter most.

Mistakes, symptoms, and prevention side by side

  • Skipped discovery
    • What you see on Monday: Devices, apps, or shared mailboxes stop working
    • How to prevent it: Inventory every mailbox, share, device, and DNS owner
  • Copied permissions one for one
    • What you see on Monday: Access denied, or far too much access
    • How to prevent it: Map access by role and have data owners approve it
  • Ignored name and path limits
    • What you see on Monday: Files fail to migrate or won't sync
    • How to prevent it: Scan, rename, and flatten before moving
  • Forgot devices that send email
    • What you see on Monday: Scanners and alerts go silent
    • How to prevent it: Choose and test a sending method for each device
  • Rushed DNS changes
    • What you see on Monday: Missing mail and Outlook password prompts
    • How to prevent it: Lower TTL early and confirm MX and Autodiscover
  • No pilot or rollback gate
    • What you see on Monday: Problems fixed live with everyone watching
    • How to prevent it: Pilot for a week and write down the stop conditions
  • Training after cutover
    • What you see on Monday: Help desk flooded with basic questions
    • How to prevent it: Communicate early and support people in person on day one

Plan the way back before you start

A Microsoft 365 migration that goes well looks uneventful. That calm comes from early work: a thorough inventory, clean permissions, tested devices, a pilot, and a written decision point that lets you stop safely. Each step protects the project and the person whose name is on it.

For a second set of eyes on your plan, we handle Microsoft 365 migration for small and mid-size businesses with one named senior advisor and documented decisions from discovery through cutover. Schedule a conversation and bring your inventory, or the gaps in it.

Sources and further reading

Ask about something important for you.

Curious about our take on an industry or technology topic? Let us know.

Contact Us