How to Migrate Your Business Email to Microsoft 365

Migrating your business email to Microsoft 365 is one of the most impactful technology decisions a UK business can make. It moves your email from ageing on-premises servers or basic hosting providers to a modern, cloud-based platform with enterprise-grade security, reliability, and collaboration features.

But email migration is not without risk. A poorly planned migration can result in lost emails, extended downtime, confused employees, and frustrated clients who can't reach you. This guide walks you through the entire process — from choosing the right Microsoft 365 plan to completing post-migration validation — so your transition is smooth and your business doesn't miss a beat.

Assessing Your Current Email Environment

Before you begin planning the migration, you need a thorough understanding of what you're migrating from. The source environment determines which migration method to use, how long the migration will take, and what challenges you're likely to encounter.

Start by documenting the basics. How many mailboxes do you have, including shared mailboxes and distribution lists? What's the total data volume across all mailboxes? What's your current email platform — on-premises Exchange, Google Workspace, IMAP hosting, or something else? Are there any mailboxes under legal hold or subject to regulatory retention requirements?

Next, identify your email-dependent systems. CRM platforms, helpdesk tools, accounting software, and other business applications often send email on behalf of your domain or integrate directly with your email server. These integrations must be reconfigured after migration. Document every application that uses SMTP relay, authenticates against your mail server, or references your email domain.

Finally, review your DNS records. Your MX records (directing email delivery), SPF record (listing authorised senders), DKIM records (email signing), and DMARC record (authentication policy) will all need updating during the migration. Record their current values so you can update them confidently.

Choosing the Right Microsoft 365 Plan

Microsoft offers numerous plans, and choosing the right one affects your costs, features, and future flexibility. For UK businesses, the most common choices are between the Business and Enterprise tiers.

Plan	Monthly Cost (per user)	Email Storage	Desktop Apps	Best For
Exchange Online Plan 1	£3.30	50 GB	No	Email-only users
Microsoft 365 Business Basic	£4.50	50 GB	No (web only)	Small teams needing email + Teams
Microsoft 365 Business Standard	£9.40	50 GB	Yes	Most SMEs (up to 300 users)
Microsoft 365 Business Premium	£16.60	50 GB	Yes	SMEs needing advanced security
Microsoft 365 E3	£27.40	100 GB	Yes	Mid-size businesses (no user limit)
Microsoft 365 E5	£47.60	100 GB	Yes	Enterprises needing full compliance/security

For most UK SMEs with up to 300 employees, Microsoft 365 Business Standard offers the best balance of features and cost. It includes Exchange Online, Teams, SharePoint, OneDrive, and desktop Office applications. If you need advanced security features — device management, advanced threat protection, and information protection — Business Premium is worth the additional investment.

For businesses with more than 300 users, or those requiring advanced compliance features (eDiscovery, audit logging, legal holds), the Enterprise E3 or E5 plans are necessary. E3 covers most requirements, whilst E5 adds advanced security (Defender for Office 365 Plan 2), compliance (advanced eDiscovery, communication compliance), and analytics (Power BI Pro).

Pre-Migration Preparation

Thorough preparation is the single biggest factor in a successful migration. Rushing this phase to save time invariably costs more time in troubleshooting afterwards.

Clean up your current mailboxes. Before migrating, encourage users to delete unnecessary emails, empty their deleted items folders, and archive old emails they don't need in their primary mailbox. Reducing the data volume speeds up the migration and reduces the risk of hitting storage limits in Microsoft 365.

Verify your domain in Microsoft 365. Add your email domain to your Microsoft 365 tenant and verify ownership by adding a TXT record to your DNS. This step doesn't affect your current email delivery — it simply proves to Microsoft that you own the domain. Complete this well before the migration date to avoid delays.

Create user accounts. Set up user accounts in Microsoft 365 for every person who needs a mailbox. Assign appropriate licences to each user. If you're migrating from an environment with Active Directory, consider using Azure AD Connect to synchronise your on-premises directory with Azure AD — this ensures usernames and passwords remain consistent.

Configure security settings. Before any users start accessing Microsoft 365, configure your security baseline. Enable multi-factor authentication (MFA) for all accounts, configure anti-phishing policies, set up data loss prevention rules if needed, and review your sharing policies for SharePoint and OneDrive. It's far easier to get security right before users start using the platform than to retrofit it afterwards.

Migration Methods: Choosing the Right Approach

The best migration method depends on your source environment, the number of mailboxes, and how much downtime your business can tolerate.

Cutover migration moves all mailboxes simultaneously. It's the simplest approach and works well for businesses with fewer than 150 mailboxes. You create a migration batch, Microsoft syncs all mailbox data, and then you switch your MX records to point to Microsoft 365. The initial sync can run for days while your old system remains active, and only the final delta sync (catching up on new emails received during the sync) requires a brief cutover window.

Staged migration is appropriate for larger organisations or those migrating from on-premises Exchange. Mailboxes are moved in batches, allowing you to migrate departments or offices one at a time. This requires a hybrid configuration where both your on-premises Exchange and Exchange Online coexist, with mail routing configured to deliver to the correct location for each user.

IMAP migration is used when migrating from non-Exchange platforms (Google Workspace, Zimbra, generic IMAP hosting). This method copies email messages from the source IMAP server to Exchange Online. It's straightforward but has limitations — calendar items, contacts, and folder rules typically don't migrate via IMAP and must be handled separately.

Third-party migration tools (BitTitan MigrationWiz, Quest, SkyKick) offer the most flexibility and are recommended for complex migrations. They support a wider range of source platforms, provide better progress reporting, and can migrate additional data types that native tools cannot handle.

Executing the Migration

With preparation complete and your migration method chosen, it's time to execute. Here's a step-by-step walkthrough of a typical cutover migration, which is the most common approach for UK SMEs.

Step 1: Start the initial synchronisation. Create the migration batch in the Exchange admin centre or using PowerShell. The initial sync copies all existing mailbox data to Microsoft 365. Depending on the number and size of mailboxes, this can take anywhere from a few hours to several days. Crucially, your existing email system continues to operate normally during this phase — users won't notice anything.

Step 2: Verify the initial sync. Once the initial sync completes, review the migration report for errors. Common issues include oversized mailboxes, corrupted items, and permission problems. Address any errors before proceeding to the cutover.

Step 3: Communicate with your users. Send a clear communication explaining what's happening, when the cutover will occur, what users need to do (reconfigure Outlook, update mobile devices), and who to contact for help. Provide step-by-step instructions for reconnecting Outlook and configuring email on mobile devices.

Step 4: Perform the cutover. Schedule the cutover for a low-traffic period — Friday evening or Saturday morning works well for most UK businesses. Update your DNS MX records to point to Microsoft 365 (yourdomain-co-uk.mail.protection.outlook.com). Update your SPF record to include Microsoft 365 (include:spf.protection.outlook.com). Trigger the final delta sync to catch up on any emails received since the initial sync.

Step 5: Update DNS authentication records. Configure DKIM by creating the required CNAME records in your DNS. Enable DKIM signing in the Exchange admin centre. Update or create your DMARC record. These steps are essential for maintaining email deliverability after the migration.

Post-Migration Configuration

The migration itself is only half the job. Post-migration configuration ensures everything works correctly and your new environment is properly optimised.

Reconfigure email clients. Users will need to reconfigure Outlook with their Microsoft 365 accounts. For Outlook 2016 and later, autodiscover typically handles this automatically — users may just need to enter their email address and password. For older versions of Outlook, manual configuration may be needed. Mobile devices will also need to be reconfigured, either through autodiscover or manual setup.

Recreate mail flow rules. If your old system had mail flow rules (transport rules, forwarding rules, auto-replies), these need to be recreated in Exchange Online. Document all rules from your old system before decommissioning it.

Configure shared mailboxes and distribution lists. Recreate any shared mailboxes and assign appropriate permissions (Send As, Send on Behalf, Full Access). Recreate distribution lists and security groups with the correct memberships. If you used Azure AD Connect, some of these may have synchronised automatically.

Update application configurations. Reconfigure all applications that send email via your old server. Update SMTP relay settings to use Microsoft 365's SMTP endpoints. Applications that use direct SMTP with authentication should use smtp.office365.com on port 587 with TLS. For high-volume sending or applications that don't support modern authentication, configure a connector for SMTP relay in Exchange Online.

Testing and Validation

Thorough testing after migration prevents problems from going unnoticed until they affect clients or business operations.

Send and receive testing: Test email sending and receiving for each mailbox type — individual mailboxes, shared mailboxes, and distribution lists. Send test emails from external addresses (Gmail, Yahoo, other business contacts) to verify inbound delivery. Send emails to external addresses to verify outbound delivery and check that SPF and DKIM authentication are passing.

Calendar and contacts: Verify that calendar items migrated correctly, including recurring meetings and meeting invitations. Check that contacts are accessible in the new environment. If calendar or contact migration was incomplete, use Outlook's import/export function or a migration tool to transfer the missing data.

Mobile device testing: Test email access on the range of mobile devices used in your organisation — iPhone, Android, and any other platforms. Verify that push notifications work, calendars sync, and contacts are accessible.

Application testing: Test every application that sends email to ensure it's correctly configured with the new SMTP settings. Send test emails from your CRM, helpdesk, accounting software, and any other email-sending applications. Verify that automated notifications, reports, and alerts are working correctly.

Common Migration Pitfalls

Based on our experience migrating UK businesses to Microsoft 365, here are the most common issues and how to avoid them.

Forgotten SMTP relays. Multi-function printers, monitoring systems, and legacy applications that send email via SMTP are frequently forgotten during migration planning. When the old mail server is decommissioned, these stop working. Audit every device and application that sends email before starting the migration.

Large mailboxes causing timeouts. Mailboxes over 10 GB can cause migration timeouts, especially over slower internet connections. For very large mailboxes, consider pre-migrating historical data in stages before the final cutover.

Public folders. If your current Exchange environment uses public folders, these require special handling during migration. Microsoft provides public folder migration tools, but the process is more complex than standard mailbox migration and should be planned separately.

Email signatures losing formatting. HTML email signatures often lose their formatting during migration, particularly if they contain images hosted on your old server. Rebuild signatures using images hosted externally (in SharePoint or a CDN) and test them across email clients before rolling out to all users.

Users not updating their passwords. If you're not using Azure AD Connect for password synchronisation, users may need new passwords for Microsoft 365. Communicate this clearly and provide a simple process for setting up their new credentials, including MFA enrolment.

Decommissioning Your Old Email System

Once you're confident that the migration is complete and all systems are working correctly, you can plan the decommissioning of your old email environment. Don't rush this — we recommend maintaining the old system in a receive-only state for at least 30 days after the MX record cutover.

During this period, any emails that arrive at the old server (from cached DNS entries or misconfigured external systems) should be forwarded to Microsoft 365. Monitor the old system's logs to identify any sources still sending to it directly, and update those configurations.

Before final decommissioning, export any data that wasn't part of the migration — server-side rules, custom configurations, and compliance archives. Once you're satisfied that nothing will be lost, you can shut down the old system, cancel the hosting, or repurpose the hardware.

Migrating to Microsoft 365 is a significant project, but with proper planning and execution, it can be completed with minimal disruption to your business. The result is a more reliable, more secure, and more capable email platform that scales with your business and integrates with the broader Microsoft 365 ecosystem.