We are currently revamping our website to improve user experience. During this time, some pages or links may not function as expected. We regret any inconvenience and appreciate your patience and continued support.

Email Migration Problems: Why Moves to Microsoft 365 Go Wrong

Email migration problems for the IT head or IT manager in India or the GCC who is planning, or partway through, a move to Microsoft 365. The article covers eight problems, from data nobody listed to mail landing on the old server and Outlook that will not reconnect. Each has a cause, the sign to watch for, the business impact and a one line fix. No tools are named and no prices are given.

Email migration problems appear when data is left unlisted, mail routing changes too soon or too late, mailbox rights do not carry across, or devices do not find the new mailbox. Each of these has a sign that shows early. A team that knows the signs can act before users notice.


Last reviewed 2026-11-16 by Manish Sharma.

This guide covers the email migration from an Exchange server or another mail platform into Exchange Online. Files go to OneDrive and SharePoint, but that work stays outside this guide. The wider job of moving mail and files into Microsoft’s cloud has its own page.

For each problem you get the cause, the sign to watch, the impact on the business and a fix in one line. A separate guide sets out the ten steps that run the move in a set order.

Eight email migration problems in three stages: before the first mailbox moves, at switch-over and inside the mailbox, with Outlook and phones last
Eight problems, four places to look.

Email Migration Problems Start Before the First Mailbox Moves

Two email migration problems begin in the plan, because the list of what exists is incomplete.

Data Nobody Listed

Mail does not live only in mailboxes. For example, archives, PST files on laptops and public folders sit outside the list a plan starts from.

Microsoft Learn also names an Import Service for organizations with many large PST files, by network upload or by mailed drive. That route is a project of its own, so it needs a place in the plan.

  • Cause: the plan came from the mailbox list alone.
  • Sign: the mailbox count and total size differ from what the plan lists.
  • Impact: old mail is missing for the people who need it.
  • Fix: walk the old system and a sample of laptops before the plan is final.
Walk the old system first

List archives, PST files and public folders before the plan is final.

Methods That Carry Mail Only

However, an IMAP move carries mail folders only. Microsoft Learn says IMAP can’t migrate contacts, calendar items and tasks. However, a user can move them by hand. Read the page Ways to migrate multiple email accounts to Microsoft 365 or Office 365, dated 13 July 2026, for the full list of methods. We read the three Microsoft Learn pages cited in this guide on 16 November 2026, and each link carries the page’s own date.

Method names matter in one way here, because some move everything and some move mail alone. The choice between them is a separate topic.

  • Cause: the team picked the method for speed, not for what it carries.
  • Sign: calendars are empty after the first pilot.
  • Impact: meetings and contact lists vanish on the first morning.
  • Fix: pilot with a user who has a busy calendar and a full contact list.
Why the signs matter

Each problem shows a sign early, and the sign is the cheapest moment to act.

Email Migration Problems at Switch-Over: Why Mail Goes Missing

Two email migration problems appear at switch-over, and both lose mail that customers have already sent.

MX Timing and Mail on the Old Server

Until the MX record changes, mail for moved users still routes to their old mailboxes. Sender systems also keep the old location until the record’s time to live (TTL) runs out. Microsoft says to set 3,600 seconds or less on each MX record. The page Migrate email to Exchange Online using the Exchange cutover method, dated 28 March 2024, also gives the reason.

  • Cause: the TTL stayed high, or the MX record changed before mailboxes were ready.
  • Sign: some senders’ mail arrives and some does not.
  • Impact: replies from customers go missing on switch-over day.
  • Fix: lower the TTL in advance and change the MX record only when the new mailboxes are ready.

Ending the Move Too Soon

Microsoft says to wait at least 72 hours after the routing change before deleting a cutover batch. Ending sooner removes the safety net, because late mail may still arrive.

After an IMAP move ends, Microsoft says the move does not carry new mail sent to the source system. On a cutover move, a mailbox with no license stops working when the 30 day grace period ends.

  • Cause: the project plan treated the move as done once the data had copied.
  • Sign: the old system still receives mail after the batch closes.
  • Impact: mail lands where nobody looks.
  • Fix: keep the batch open until you confirm routing and the wait ends.
Do not close the batch early

Keep the cutover batch open for at least 72 hours after the routing change.

Email Migration Problems Inside the Mailbox: Items, Rights and Rules

Three more email migration problems sit inside the mailbox. They stay hidden until someone looks for a specific message, meeting or rule. A team sorting out Office 365 migration issues should look here before the support desk phones ring.

Item Counts That Do Not Match

Microsoft Learn says the migration report flags items that retention or archive policies removed as “missing”. Those gaps are expected, so they need no fix. Also, the IMAP route has limits of 500,000 items per mailbox and 35 MB per message. The page What you need to know about migrating your IMAP mailboxes, dated 12 March 2024, gives the detail.

  • Cause: policies and limits remove or skip items.
  • Sign: missing counts in the move report.
  • Impact: real loss hides behind expected gaps.
  • Fix: sort the report into expected gaps and unexplained gaps, and look at the second group first.

Shared Mailboxes, Delegates and Groups

Also, a cutover move does not create migrated groups as security groups in Microsoft 365. Before migration, remove any manager or delegate who is not moving from the object. Both points come from Microsoft’s cutover page. For groups, see the directory that stores users and groups.

  • Cause: rights and groups tied to the old directory.
  • Sign: an assistant loses access to a manager’s calendar.
  • Impact: executives lose their working arrangements overnight.
  • Fix: list every delegate and group before the move and test each in the pilot.

Forwarding and Inbox Rules That Stop

The Microsoft Learn pages read for this guide do not say that forwarding and rules carry across. Instead, treat each one as unmoved until tested.

  • Cause: rules lived on the server or in a mail client, and nobody wrote them down.
  • Sign: a team mailbox that used to forward goes quiet.
  • Impact: requests sent to a shared address go unanswered.
  • Fix: ask each team to list its forwarding and rules before the move.

Email Migration Problems on Outlook and Phones

Outlook finds the new mailbox through an Autodiscover record that you set after the move. If the old Exchange server stays in service, Microsoft says the Autodiscover record must point to Microsoft 365 in both internal and external DNS. The cutover page names the record, and that is the one to read first.

If admins lack access to the old mailboxes, they reset passwords. Microsoft’s IMAP page says this, and users need the new ones on day one.

These mailbox migration problems show up on the help desk first: profiles that will not connect and phones that stop syncing mail. Security settings matter after the move too, and the threats that follow mail to its new home are covered in a separate post.

  • Cause: Autodiscover points at the old server, or users lack the new password.
  • Sign: calls about profiles and phone mail on day one.
  • Impact: a morning of lost working time across the firm.
  • Fix: publish the day-one steps for users before switch-over.

Key Takeaway Outlook and phones fail on day one, so publish the day-one steps before switch-over.

Email Migration Problems: Signs and Business Impact

The table lines up all eight problems with the sign to watch and who notices first.

Problem Sign to watch Who notices first Business impact
Data nobody listed Counts differ from the plan The migration lead Old mail missing
Methods that carry mail only Empty calendars in the pilot Pilot users Lost meetings
MX timing Some senders get through, some do not Customers Lost replies
Ending the move too soon Old system still gets mail The help desk Mail lands unseen
Item counts Missing counts in the report The migration lead Hidden loss
Shared mailboxes and groups Assistants lose calendar access Executives Broken workflows
Forwarding and rules A team mailbox goes quiet The team Unanswered requests
Outlook and phones Profile and sync calls Every user Lost time
Planning order for a mail move: switch-over timing, ending the move, rights, then devices
Plan first for the problems that lose mail.

Signisys’s working view is to plan first for the two problems that lose mail: switch-over timing and ending the move too soon. Rights come next, and then devices. Our reasoning is simple. Lost mail is the hardest loss to undo, but rights and profiles can be fixed once the cause is known.

Key Takeaway Lost mail is the hardest loss to undo, so plan switch-over timing and the end of the move first.

Why Large Batches and Unready Users Make Email Migration Problems Worse

Big batches, however, add risk. A cutover move takes up to 2,000 mailboxes. Microsoft recommends only 150, because creating and moving 2,000 users takes a long time. Then ask Microsoft’s support team about throttling and service health before sizing batches.

Users who did not hear what changes on day one raise the support load. These email migration issues compound: a large batch means more people calling about the same profile problem at once.

A short notice to staff takes little effort. It removes a share of the calls if you send it before switch-over.

What Comes After the Problems

Later questions in a mail move fall outside the problems covered above.

Pricing is not covered here.

Signisys provides these services: see our digital workplace solution, end-user computing services and the Microsoft 365 use case. A working session reviews your mailbox list, routing plan and rights, with no promised result and no price. No charge, with a fixed scope.

Book a consultation
Talk through your mail move before switch-over

Email Migration Problems FAQ

Why is email forwarding not working after the move?

The Microsoft pages read for this guide do not say that rules and forwarding move with the mailbox. Instead, ask each team to list them before the move.

Can a move to Microsoft 365 lose email?

Yes, mainly at switch-over and when the move ends too soon. Signisys’s working view is that these two cause the loss. The other problems hide mail or break access.

What do users notice first after the switch?

Outlook profiles and phone mail. Also, if you reset passwords, users need the new ones.

Is old mail at risk if we switch off the old server early?

Yes, if mail still routes to it or nobody has copied it yet. Keep the old server until you confirm routing, and wait the 72 hours Microsoft names.

Newsletter

Security Insights, Delivered.

Practical, vendor-neutral analysis of threats, tools, and architecture decisions.

Book a Consultation

A practice principal will contact you within 1 business day.

Thank you! A Signisys principal will be in touch within 1 business day.