1-844-366-6700

Should You Migrate Your Business Email Yourself or Hire a Pro?

Email Migration Guide · 2026

Should You Migrate Your Business Email Yourself or Hire a Pro?

Short answer: DIY works if you have a handful of mailboxes, a simple source system, and a few days where a hiccup will not hurt. Hire a professional if you have more than a few dozen users, shared mailboxes or public folders, compliance requirements, a tight cutover window, or no one who has done this before.

The tools are available to everyone. The difference is knowing what they leave out, and what to do when something goes wrong.

Last updated: October 2026

500,000item cap per mailbox on Microsoft IMAP migration
25 MBlargest message Google's data migration service moves
150mailboxes where Microsoft says cutover performance suffers

The Quick Decision Guide

Your situationDIY is realisticHire a professional
Number of mailboxes1 to 1025 or more
Source systemStandard IMAP, or a single Gmail or Microsoft 365 account setLegacy Exchange, hosted Exchange, multiple domains, or mixed systems
Data beyond emailEmail onlyCalendars, contacts, shared mailboxes, public folders, archives
Compliance needsNoneHealthcare, legal, financial, government contracts
Tolerance for mistakesA few lost messages would be annoyingA lost message could cost a client or trigger a compliance issue
In-house IT skillsSomeone comfortable with DNS and admin consolesNo one, or someone already stretched thin
Rule of thumb: if most of your answers land in the middle column, DIY can work. If even two or three land in the right column, the cost of a mistake usually outweighs what you would save.

What a DIY Email Migration Actually Involves

Most DIY guides make migration sound like one button. In practice, you are running a small IT project with several moving parts:

  1. Inventory everything. Every mailbox, alias, shared inbox, distribution list, forwarding rule, and every app that sends mail as your domain (invoicing, CRM, website forms, marketing tools).
  2. Set up the new platform. Create the tenant or workspace, add and verify your domain, and create every user and mailbox before any data moves.
  3. Choose a migration method. Each method supports different data and different source systems. The next section covers what each one leaves behind.
  4. Run the initial copy. Large mailboxes can take a long time, and throttling by either platform can slow things further.
  5. Prepare DNS. Lower your MX record TTL ahead of time, and prepare SPF, DKIM, and DMARC changes for the new platform.
  6. Cut over. Switch your MX records so new mail lands in the new system, then run a final sync for anything that arrived in between.
  7. Reconnect every device. Outlook profiles, phones, tablets, and shared calendars all need attention.
  8. Verify and clean up. Spot-check mailboxes, confirm mail flow in both directions, and keep the old system available until you are sure nothing was missed.

None of these steps is mysterious. The risk is that they depend on each other, and a mistake in step 2 or 5 often does not show up until step 6 or later.

Where DIY Migrations Go Wrong

1. The free tools only move what they were designed to move

IMAP is the most common DIY method because almost every email system supports it. But Microsoft's IMAP migration documentation states that it does not migrate contacts, calendar items, or tasks, that it moves a maximum of 500,000 items per mailbox (newest to oldest), and that the largest message it can carry is 35 MB. The mailboxes also have to exist in Microsoft 365 before the migration starts.

Going the other direction, Google's data migration service FAQ says the tool works best with groups of 100 users or fewer, does not migrate messages larger than 25 MB, and does not support shared or public IMAP folders.

If you do not know which of your data falls outside those limits, you will find out after cutover, when someone asks where their calendar went.

2. Method choice depends on your source system and size

For organizations moving from on-premises Exchange, Microsoft's guidance on choosing a migration path explains that a cutover migration can technically handle up to 2,000 mailboxes, but that it is more reasonable to migrate 150 users or fewer because performance suffers at larger sizes. For more than 150 mailboxes, Microsoft recommends an Exchange hybrid approach, which requires directory synchronization and a lot more setup.

Picking the wrong method can mean starting over. It is one of the most common reasons a "quick weekend project" turns into a month.

3. The DNS cutover is where mail gets lost

Email does not move all at once. When you change your MX records, other mail servers around the world keep delivering to your old system until their cached copy of the record expires. If your TTL is still at a default value of an hour or more, mail can keep landing in the old system long after you stop watching it. Migration providers commonly advise lowering the MX record TTL to about five minutes at least 24 to 48 hours before the switch, then running a final sync after cutover to capture anything that slipped through.

The same cutover is where authentication records matter. A domain should have only one SPF record, so adding the new platform means editing the existing record, not adding a second one. Get SPF, DKIM, or DMARC wrong and your outbound mail can land in spam or be rejected, which feels like an outage even though nothing is technically down. If you are not sure your domain is protected, our guide to preventing phishing and spoofing with DMARC records covers what each record does.

4. Delta syncs, duplicates, and known issues

Any migration that runs longer than a day or two needs a second pass to pick up mail that arrived after the first copy. Tools differ in how they handle that. Google's own documentation for its Workspace Migrate product lists known issues, including duplicated messages after a delta migration when a folder was renamed in Outlook. These are not exotic edge cases. They are what happens when real mailboxes, built up over years, meet a tool with assumptions.

5. Microsoft is changing the ground under migration tools

If you are migrating into or out of Microsoft 365, timing matters more than usual this year. Microsoft planned to begin blocking Exchange Web Services (EWS) in Exchange Online by default on October 1, 2026, with administrators able to keep access temporarily through an application allow list, and a complete shutdown scheduled for April 2027. Microsoft's Exchange team described a phased, admin-controlled model built on an organization-level setting and an allow list of approved app IDs.

Why does that matter for a migration? EWS has long been how many migration and backup tools read and write mailbox data. Vendors have to move to the Microsoft Graph API instead, and some migration providers have said their tools were being updated ahead of the deadline. If you are using a lower-cost or older tool you found online, confirm it supports the newer approach before you start. A professional team already works from a current toolset, and will know whether your tenant needs an allow list entry for anything still depending on EWS.

6. The people side of cutover

Even a technically perfect migration can feel broken to employees. Outlook profiles need to be rebuilt, phones need new settings, and shared calendars sometimes need to be re-shared. If you are planning the human side, our article on what to expect during an email migration lays out the typical timeline from a user's perspective.

DIY vs. Professional at a Glance

DIY is a fit when

  • You have ten or fewer mailboxes, and few or no shared mailboxes
  • Your source is a standard IMAP provider or a simple Gmail setup
  • Email is the only data you need to move, or you are comfortable recreating contacts and calendars by hand
  • Someone on your team can manage DNS and is willing to learn the admin console
  • You can pick a quiet window and tolerate some delay if something goes sideways

Hire a professional when

  • You have 25 or more mailboxes, or any shared mailboxes, public folders, or archives
  • You are moving from legacy or on-premises Exchange, or between two Microsoft 365 tenants
  • You operate under compliance requirements and need a defensible process
  • You have a hard deadline, such as a contract end date or an acquisition closing
  • Your team has never done a migration, or your IT person is already at capacity
  • A DIY attempt has already stalled or produced errors

What a Professional Migration Adds

Hiring a migration provider is not about the copy itself. The software does that. What you are paying for is everything around it:

  • Pre-migration assessment. Finding the shared mailboxes, large mailboxes, aliases, forwarding rules, and legacy integrations that would otherwise surface on cutover day.
  • The right method and tooling. Choosing between IMAP, cutover, staged, hybrid, or a third-party tool based on your data and your timeline, not on whichever is easiest to set up.
  • A tested cutover plan. TTL changes, authentication records, delta syncs, and a rollback plan that has been thought through before it is needed.
  • Pilot first. Moving a small group of mailboxes before everyone else, so surprises affect two people, not the whole company.
  • Post-migration support. Fixing the device and Outlook issues that always appear in the first week.
  • Accountability. If something goes wrong, someone owns it and has done this before.

To see what this looks like in practice, our email migration service page outlines how we approach it, and our step-by-step guides for migrating from Google Workspace to Microsoft 365 and from Microsoft 365 to Google Workspace show the full process on each platform.

The Real Cost Comparison

DIY looks free because the tools are included with your subscription. The cost shows up in time and risk.

Quick estimate: employees affected × average loaded hourly cost × hours of disruption. For example, 20 employees losing two hours each at $40 an hour is $1,600 in lost productivity, before IT time spent fixing problems or business lost to delayed email. Change the numbers to match your team.

The cost of a bad cutover scales with headcount, while the cost of a careful one mostly does not. For a breakdown of what professional email migration typically costs, see our email migration cost guide.

One more option to know about: Microsoft's FastTrack program gives eligible Microsoft 365 customers access to online planning and migration resources, and customers with 150 or more seats can get remote guidance from FastTrack engineers or approved partners. It is worth checking whether your organization qualifies before you decide.

Questions to Ask Any Migration Provider

Whether you hire us or someone else, these questions separate experienced providers from the rest:

  1. Which migration method will you use for my situation, and why?
  2. What will not migrate, and how will we handle it?
  3. How do you handle the DNS cutover and the final sync?
  4. Will you run a pilot group first?
  5. Which tools do you use, and are they current with Microsoft's EWS changes?
  6. What is the rollback plan if cutover fails?
  7. What support do my employees get after cutover, and for how long?

A provider who answers these clearly and without hedging has probably done this many times.

Frequently Asked Questions

Can I migrate business email myself?

Yes, for small and simple setups. Both Microsoft 365 and Google Workspace include self-service migration tools. The tools work best with a few mailboxes, a standard source system, and email-only data. Larger or more complex migrations usually need planning and experience the tools do not provide.

What is the biggest risk of migrating email yourself?

Lost or delayed mail during the DNS cutover, and data that the chosen tool does not move. IMAP migration, for example, skips contacts, calendars, and tasks. Both risks are avoidable with planning, but they are easy to miss the first time.

Does an IMAP migration move calendars and contacts?

No. Microsoft's IMAP migration moves email messages and folder structure only. Calendars, contacts, and tasks need a different method or manual recreation. IMAP migration to Microsoft 365 also caps at 500,000 items per mailbox and 35 MB per message.

Will I lose email during a migration?

You should not, if the cutover is planned well. The usual safeguards are lowering the MX record TTL a day or two before the switch, running a final sync after cutover, and keeping the old system available until you confirm nothing is still arriving there.

Does Microsoft or Google migrate my email for free?

Both platforms include self-service migration tools in their admin consoles. Microsoft also runs FastTrack, which offers remote guidance from engineers or approved partners to customers with 150 or more seats. Smaller organizations usually run the tools themselves or hire a migration partner.

How does Microsoft's EWS retirement affect email migration?

Many migration and backup tools have relied on Exchange Web Services to read and write mailboxes. Microsoft planned to block EWS in Exchange Online by default starting October 1, 2026, with full removal scheduled for April 2027. Confirm that any migration tool you use supports the newer Microsoft Graph approach.

When should I hire a professional for email migration?

Consider a professional if you have 25 or more mailboxes, shared mailboxes or public folders, compliance requirements, a firm deadline, or no one in-house who has completed a migration before. The more complex the environment, the more a mistake costs.

What should I ask an email migration provider?

Ask which method they will use and why, what will not migrate, how they handle the DNS cutover, whether they run a pilot first, which tools they use, what the rollback plan is, and what post-migration support employees receive.

Not sure which side of the line you are on?

Tell us how many mailboxes you have, what you are moving from, and when you need to be done, and we will tell you honestly whether it is a project you can handle yourself.

Talk to an Email Migration Specialist

Sources