Business email setup: a practical migration checklist

A business email address needs more than a domain and a working inbox. Someone must own the accounts, the DNS settings, recovery and the move from any existing provider. Plan those responsibilities before changing where mail is delivered.

There is no reliable one-hour promise for setup or migration. Mailbox size, access, calendars, shared addresses, applications and DNS caching all affect the work. The checklist below helps you agree the scope and the evidence needed before calling it complete.

1. Record what the business already uses

List people, mailboxes, aliases, shared addresses and distribution groups. Include website forms, scanners, accounting software and marketing platforms that send as your domain. Record the domain registrar, authoritative DNS provider and authorised administrator. Store credentials in an approved password manager, not the planning sheet.

Check whether contacts, calendars, shared folders and archives need moving as well as email. A migration method that copies messages may not copy these other items. Identify any retention requirements and agree who can approve the change.

2. Choose the service around the work

Compare administration, collaboration, recovery, device support and the actual subscription features. A mailbox bundled with hosting and a Microsoft 365 or Google Workspace subscription serve different needs. An included mailbox is part of a hosting package; it is not evidence of a free standalone email service.

Check the current plan and supported migration method with the provider. Google Workspace planning is covered in our migration guide. Do not assume all providers import the same file formats or that an IMAP copy includes calendars and contacts.

3. Prepare accounts before changing delivery

Verify domain ownership using the exact value supplied by the chosen service. Create the required users and mailboxes, assign appropriate licences, protect administrator access and arrange account recovery. Confirm staff can sign in with the approved authentication method.

Microsoft explicitly instructs administrators to create users and mailboxes before changing the MX record. Follow the equivalent current instructions for your provider. Changing an MX record redirects incoming delivery; it does not migrate the contents of an old mailbox.

4. Plan and test the migration

Preserve a recoverable copy of the information in scope. Test a representative mailbox and check folders, dates, attachments and any separately migrated calendars or contacts. Record items the chosen tool cannot move.

Agree the cutover window, staff instructions, final synchronisation, old-service overlap and recovery plan. Lowering a DNS record’s TTL does not instantly expire copies that were cached under its previous value. Allow for the existing TTL and test actual delivery. Keep the old service until reconciliation and acceptance are complete, with the retention period agreed in advance.

5. Configure authentication for every legitimate sender

SPF, DKIM and DMARC work together, but they do not guarantee inbox placement or prevent every impersonation attempt.

• SPF authorises sending systems for the domain used in the envelope sender. Maintain one valid SPF record for each domain that needs it, accounting for all approved sending services.
• DKIM adds a signature that receiving systems can validate. Publish the provider’s exact selector records and enable signing where required.
• DMARC checks whether successful SPF or DKIM authentication aligns with the visible From domain. A pass through either aligned method can satisfy DMARC. Its policy requests how receivers handle failures; receivers make the final delivery decision.

Inventory and test legitimate senders before tightening a DMARC policy. Do not jump to quarantine or rejection as a workaround for missing DKIM. Review reports through an authorised service and protect any information they contain.

6. Verify delivery and hand over ownership

Test inbound and outbound mail with independent external addresses, replies, aliases and shared mailboxes. Check the website form, scanner and business applications too. Inspect message authentication results and migration reports, then have the business owner confirm the agreed acceptance checks.

If mail fails, preserve the full error, time, affected address and delivery trace for authorised support. Do not simply wait 48 hours or weaken authentication. Check the actual DNS answer, service status, mailbox configuration and provider guidance. Use supported modern sign-in; an app password is not a universal fix.

Finish with named owners for renewals, administrator recovery, new starters, leavers and backup or retention decisions. The free account-ownership checklist helps record responsibilities without storing passwords.

Get help with business email

hostme.ie provides business email setup and migration support. We agree the systems, information to move, acceptance checks and price before work starts. A migration or major configuration change is a separately scoped project; ongoing support follows its written service agreement.

Talk through your business email setup on WhatsApp.

Technical references reviewed on 25 September 2026. Check your provider’s current instructions and actual subscription before making changes.