Business Email Migration Checklist for SMEs

An email move can look simple until a director cannot find a contract thread, a shared mailbox stops receiving enquiries, or a member of staff is locked out on Monday morning. A proper business email migration checklist turns a potentially disruptive change into a controlled project, protecting the messages, contacts, calendars and access your team relies on.

For Norfolk and Suffolk businesses, email migration is often part of a wider change: moving to Microsoft 365, replacing an ageing server, improving cyber security, or bringing several sites under one IT system. The right approach depends on the size of the organisation, the current email platform and how heavily the business uses shared mailboxes, mobile devices and third-party applications.

Start with a clear migration plan

Before moving a single mailbox, agree what is being moved, why it is being moved and who is responsible for each decision. This avoids the common problem of treating email as a standalone service when it is connected to day-to-day operations, finance systems, websites, customer relationship management platforms and staff devices.

Set a realistic migration date and choose a quieter period where possible. A small office may be able to complete the final switch outside normal hours. A busy multi-site business may need a phased move, with pilot users first and groups of staff moved in stages. Speed matters, but continuity matters more.

Your plan should identify the current provider, the target platform, the number of users, total mailbox storage, internet connection details and any retained email archives. It should also name a business contact who can make quick decisions if an issue appears during the change.

Audit every mailbox and address

An accurate audit is the foundation of a successful migration. Do not only count named employee mailboxes. Include former staff accounts that must be retained for records, generic addresses such as sales@ or accounts@, forwarding rules, distribution lists and aliases used for different departments or trading names.

Check which shared mailboxes are actively used and who needs access to them. A shared inbox used by customer service staff may have folders, rules and permissions built up over years. Those details need to be documented, not assumed.

At the same time, identify unused accounts. Removing old mailboxes and addresses can reduce licensing costs and make the new system easier to manage. However, do not delete anything simply because it appears inactive. An old address may still receive supplier invoices, website enquiries or password reset messages.

Business email migration checklist: protect data first

The migration itself should not be the first time you discover how much business information is stored in email. Confirm the scope of data to be transferred, including mail, calendar appointments, contacts, tasks and shared mailbox content. If staff use Outlook data files stored locally on their PCs, these may need separate attention.

A sensible checklist includes the following controls:

• Confirm that current mailboxes and any local archives are backed up before work begins.
• Check the date range of mail to be migrated, particularly where very large historical archives are involved.
• Record mailbox permissions, delegation, shared calendars and folder access.
• Export or document contacts held outside the central address book.
• Identify automated systems that send or receive email, such as website forms, scanners, alarms and accounting software.
• Retain a rollback plan, including access to the former service for an agreed period if practical.

Data retention needs a business decision, not just a technical one. Moving every message from the past 15 years may increase cost and extend the project. Moving too little can create compliance, customer service and operational problems. For many SMEs, a full migration of active mailboxes combined with a secure, accessible archive for older records is the sensible middle ground.

Prepare the new email environment

Create and test the destination before changing public email delivery. User accounts, licences, shared mailboxes and security settings should be ready in advance, with clear naming conventions that staff will recognise.

Security should be built in from the start. Enable multi-factor authentication for all users, particularly administrators, and make sure recovery methods are accurate. Use separate administrator accounts rather than giving day-to-day user accounts unrestricted privileges. This reduces the damage a compromised password can cause.

Set up sensible anti-spam and anti-phishing protection, then review the policy with the business. An overly strict filter can delay genuine customer emails; a loose one leaves staff exposed to fraudulent invoices and account takeover attempts. The best settings reflect how the organisation works and are reviewed after go-live.

Also check device requirements. Staff may use Windows PCs, Macs, mobile phones, tablets and webmail. Confirm which versions of Outlook or mobile operating systems are supported, and replace or update anything that cannot connect securely. Older printers and scanners that send email are often missed until they stop sending scanned documents.

Review domain and DNS access

Email delivery relies on DNS records for the business domain. Make sure you can access the domain registrar or DNS hosting account before the migration window. This is essential for changing MX records and adding the authentication records that help other providers verify your email.

The exact records will vary by provider, but typically include SPF, DKIM and DMARC. Configured properly, they reduce the risk of criminals impersonating your domain and improve the likelihood that genuine messages reach recipients. Changes should be checked carefully: a misplaced character in a DNS record can interrupt mail flow.

If the website, email and domain are managed by different suppliers, agree who will make each change and when. This is one reason a single local IT partner can make projects easier to coordinate, but clear ownership is necessary whichever suppliers are involved.

Test with real users before the final switch

A pilot migration is worthwhile for most businesses. Select a small group that represents how the organisation works: someone who uses shared mailboxes, someone with a large archive, a mobile user and a senior member of staff who needs delegated calendar access.

Ask pilot users to send and receive internal and external emails, search older messages, open shared calendars, use mobile devices and test any key systems that send automated mail. Their feedback will expose practical issues that a purely technical test may miss.

Do not forget external contacts. After testing the new service, send messages to common destinations such as major customer domains and personal accounts, then confirm replies arrive correctly. This can highlight filtering or authentication issues before the business-wide change.

Manage the cutover carefully

When the final migration starts, communicate clearly with staff. Tell them what will happen, when to expect brief disruption, what they need to do and who to contact for help. Avoid vague messages such as “email is being upgraded”. Explain whether they need a new password, multi-factor authentication setup or a revised Outlook profile.

Most migrations involve an initial data transfer followed by a final synchronisation close to the DNS switch. This reduces downtime because the bulk of historical mail has already been copied. There may still be a short period where messages arrive in different locations or take longer than usual to appear. That is normal, provided it is monitored and resolved promptly.

During cutover, monitor mail flow, failed logins and support requests. Keep an eye on shared mailboxes, website forms and automated senders first, as these can affect customers without being immediately visible to staff. Maintain a simple issue log so recurring faults are identified rather than handled as isolated calls.

Complete the checks after migration

A migration is not finished when new messages begin arriving. Over the next few days, confirm that users can access the mail they need and that security settings are working as intended. Review any missing folders, permissions, calendars or contacts while the previous system is still available.

Check that mobile devices have been enrolled securely and that former staff accounts no longer have access. Update internal documentation with account ownership, licence details, administrator arrangements and domain credentials. These records will save time when staff join, leave or change roles.

Finally, provide short, practical guidance for users. They should know how to use multi-factor authentication, report suspicious messages, access shared mailboxes and recover from a lost device. Good technology is only part of the protection. Staff need to understand the new way of working.

For a business where email supports every sale, booking and customer conversation, careful preparation is far cheaper than recovering from avoidable downtime. Anglian Internet can help East Anglia businesses plan, deliver and support an email move that suits their systems, people and budget.