A Microsoft 365 migration for a UK small business is a planned move of email, files and related apps into your organisation's own Microsoft 365 tenant. It normally runs in five phases: discovery, tenant and DNS preparation, a pilot, cutover, then clean-up and security. The right migration method depends on the system you are leaving and how many mailboxes you have.
Microsoft 365 is the current name for the service many people still call Office 365. The older name is still widely used, including in our own site navigation; this guide uses Microsoft 365.
This checklist is for UK SME owners and whoever looks after IT and operations. It covers email, files, devices and the business apps that are easy to forget, not just mailboxes. We link to Microsoft Learn for Microsoft's limits and rules. Whether you are comparing Microsoft 365 migration services or planning to do the work in-house, the same steps apply.
It involves more than moving inboxes. A typical move covers email, calendars and contacts; shared files moving into SharePoint or OneDrive; the laptops and phones staff use; and any printers, scanners or business systems that send email.
The mailboxes are rarely what goes wrong. Problems come from the edges: the scanner that emails PDFs, the accounts package that sends invoices, a shared mailbox nobody listed, or a registrar login held by someone who left years ago. Treat it as a whole-business move, not an email job.
| Task | Business owner | IT provider (in-house or external) | Microsoft |
|---|---|---|---|
| Agree scope, timing and acceptable disruption | Decides | Advises | — |
| Domain registrar and DNS access | Owns the accounts and approves changes | Makes the DNS changes | — |
| Tenant, users and licences | Approves licence choices and costs | Sets up and configures | Provides the service and admin tools |
| Moving mail and files | Confirms what must move and what can be archived | Plans and runs the migration | Publishes the migration methods and tools |
| Security settings and admin roles | Approves who has admin rights | Configures and documents | Provides the security features |
| Telling staff what changes | Sends or backs the message | Prepares instructions and support | — |
| Backup and retention choices | Decides what the business needs | Implements the chosen approach | Runs the underlying service |
If you would rather hand some of this over, our managed cloud services page covers "Cloud Infrastructure, Data Migration, Maintenance and Security", along with services such as cloud email for business and Office 365 backup. Replacing PCs or servers, or moving to a newer version of Windows, is a separate workstream; if that is also on your list, see IT system and workstation upgrades.
The system you are leaving and the number of mailboxes decide it. There is no single best method for every small business, so start with what you run today.
Microsoft describes its options in its guide to the ways to migrate multiple email accounts to Microsoft 365:
| Method | What moves | Microsoft Learn criteria | Main limitations |
|---|---|---|---|
| Cutover | All mailboxes in a single migration | Exchange 2003, 2007, 2010 or 2013 with fewer than 2,000 mailboxes (overview page); the cutover guide says Exchange Server 2003 or later | Microsoft says 150 users or fewer is "more reasonable" because of the time involved |
| Staged | Mailboxes in batches | Exchange 2003 or 2007 with more than 2,000 mailboxes | Both source versions are long out of support; rarely relevant to a small firm |
| Hybrid | Mailboxes moved gradually while on-premises and online mailboxes coexist | Exchange 2010 with 150–2,000 mailboxes, or moving in small batches over time; or Exchange 2013 or later | In our judgement, the most complex option to set up and maintain |
| IMAP | Email in the inbox and other mail folders | Gmail, Outlook.com and other IMAP-capable systems | Contacts, calendars and tasks are not moved; mailboxes must be created first; new mail sent to the old system after migration is not moved |
| Google Workspace | Mail via Microsoft's dedicated Gmail migration path | Firms moving from Google Workspace | See the Google Workspace (Gmail) entry in Microsoft's migration guide, linked above |
On cutover, Microsoft's own wording is worth quoting in full: "With cutover migration, you can move up to 2,000 mailboxes, but due to length of time it takes to create and migrate 2,000 users, it's more reasonable to migrate 150 users or less." For a business with fewer than 50 users on Exchange 2010 or 2013, cutover is often the simplest route. If you run Exchange 2016 or 2019, note that Microsoft's overview lists cutover for Exchange 2003–2013 and hybrid for Exchange 2013 or later, while its cutover guide says cutover suits Exchange Server 2003 or later. Check both pages before choosing. Microsoft's cutover migration guide and its notes on staged migration explain the prerequisites.
Many small firms are not on Exchange at all. If your email is with a hosting company, IMAP is often the practical choice, but contacts and calendars then need moving separately, for example via a PST file (an Outlook data-file export of a mailbox). Otherwise staff find empty calendars on their first morning.
A practical sequence is discovery, tenant and DNS preparation, a pilot, cutover, then clean-up and security. Work through them in order and tick off each item as you go.
In its guide to connecting your domain by adding DNS records, Microsoft advises: "Before you begin, add users and set up mailboxes in Microsoft 365 for all email users on your domain." Updating the MX record before mailboxes exist is a common way to lose mail.
If the trigger for your move is an ageing server, note that Exchange Server 2016 and 2019 and Office 2016 and 2019 reached the end of Microsoft support on 14 October 2025, according to Microsoft's 2025 end-of-support list.
Move a small group first, ideally people who report problems clearly, and agree what "working" means:
Fix what the pilot uncovers before you schedule the main cutover.
The aim is that staff keep working throughout. A short adjustment period, while people sign in again and phones pick up new settings, is normal. Nobody can honestly promise zero disruption.
It depends on the number of mailboxes, the amount of data, the system you are leaving and how many apps and devices must be reconfigured. With good planning, the aim is that staff keep working and no mail is lost, though a short settling-in period is normal.
Be wary of any "typical timeline" that ignores those variables: a five-person office on hosted email and a 40-person firm with a server, shared drives and an accounts package are very different projects. The main fixed planning item is DNS, because lowering the TTL needs lead time before cutover. Mail loss usually comes from sequencing errors, such as changing MX records before mailboxes exist, or from forgotten shared mailboxes and aliases. Discovery and a pilot reduce both risks.
Turn on multi-factor authentication (MFA) for everyone, block legacy authentication, limit admin roles, keep a separate emergency admin account, and set up SPF, DKIM and DMARC for your domain.
Backup after the move. Moving to Microsoft 365 does not remove the need to decide how your own data is protected and retained. Microsoft offers a separate Microsoft 365 Backup product, and describes ransomware and accidental or malicious deletion as the scenarios it is designed for. Many businesses add a backup service of their own. For the wider case, read our article on data backup.
UK GDPR and data location. Personal data moves during a migration, so the UK GDPR still applies. The ICO's guide to data security explains the requirement for "appropriate technical and organisational measures", and its guidance on international transfers covers data sent outside the UK. Microsoft's data location documentation explains where Microsoft 365 services store data, and the Data Location Card in the admin center shows details for your tenant. This is general information, not legal advice.
It depends on your circumstances rather than your size alone. Some firms manage a simple move in-house; others bring in a Microsoft 365 migration company or their existing IT provider.
Consider paying for Microsoft 365 migration services if several of these apply:
Microsoft's own guidance notes that if none of its standard methods suits your organisation, you can consider working with a partner to migrate email. If you do the work yourself, the checklist above still applies, and it helps to line up ongoing Microsoft 365 support for business afterwards, whether from staff or through IT support services.
If you are planning a move and want a second opinion on scope, method or timing, talk to Swift about your Microsoft 365 migration.
There is no reliable single figure, because mailbox count, data volume, the source system and the number of apps and devices to reconfigure all change it. The one lead time to plan early is lowering the DNS TTL before cutover.
Mail loss is usually avoidable with a pilot and the right sequencing, but expect a short settling-in period. Keep the old system readable for an agreed time and check it for stragglers, especially after an IMAP migration.
Start from what you run today: Exchange points to cutover, staged or hybrid, while hosted email or Gmail usually means IMAP or Microsoft's Google Workspace path. If you use IMAP, export contacts and calendars separately.
MFA for everyone, legacy authentication blocked, few admins plus an emergency account, and SPF, DKIM and DMARC on your domain. Build these into the migration project rather than scheduling them for later.
Yes, you still need to decide how your data is protected and retained. Microsoft offers Microsoft 365 Backup as a separate product, and many businesses use another backup service.
Check how many of the get-help criteria above apply to you. If only one or two do, an in-house move with a careful checklist may work; if several apply, outside help is worth considering.
Blog article date:
19 th
Nov 2026
Posted by Tas
Tags Microsoft 365, Office 365, Email Migration, Cloud Services, IT Support
Please use the following links to go directly to our services pages that relate to this blog article.