Business email on your domain: plan a careful migration
Separate domains, mailboxes and forwarding, then plan addresses, old messages and delivery tests before moving email.
An address such as info@example.com requires a domain and services for receiving and sending mail. The website and email may use different providers. Identify each component first.
This is a planning guide. Obtain actual settings from your chosen mail provider; incorrect values can interrupt delivery.
Decide which addresses need mailboxes
List personal addresses, shared addresses and automated senders. A mailbox stores messages and provides access. An alias is another address, not necessarily another mailbox; confirm the provider’s terminology.
Agree who reads and answers shared addresses. Forwarding to someone’s personal inbox differs from a shared inbox where colleagues can see completed work.
Inventory the migration without passwords
| Item | What to document |
|---|---|
| Address | Which existing addresses must keep working? |
| Owner | Who uses it and approves the migration? |
| Content | Must messages, folders, contacts or calendars move? |
| Devices | Which phones, computers and mail apps need changes? |
| Systems | Do forms, invoicing or newsletters send from the domain? |
Messages, contacts and calendars may need different methods. Agree transfer and verification before closing the old account.
Understand the DNS records
MX records identify receiving mail servers, separately from website routing. See Cloudflare’s MX explanation.
SPF, DKIM and DMARC help receiving systems check the sender domain and handle failures. Their roles differ, and all authorised sending services must be considered. See SPF, DKIM and DMARC explained.
Do not copy another provider’s example values. Inventory current senders so forms and invoicing continue to work.
Plan the switch
Create and check new accounts before redirecting incoming mail. Decide when content is copied, who changes DNS and how messages arriving during transition are handled.
Keep the previous service accessible until transfer and delivery are verified. Agree its retention period, incident responsibility and a route back if a critical issue appears.
Test more than login
Send to and receive from external addresses. Check replies, attachments, mobile settings, shared addresses and automated systems. Use the provider’s method to verify domain authentication.
Record the address, result and owner of each test. Opening webmail verifies login, not the whole mail flow. Authentication settings cannot guarantee inbox placement at every recipient.
If you choose Glomiva
Our hosting service describes mailboxes and webmail. Discuss your addresses, migration content and automated senders. If the website is moving too, keep email as a separate part of the agency handover plan.
Keep reading
Choose a platform · 2 min read
WordPress or custom development? Choose for your workflow
Compare publishing, functionality, ownership and ongoing responsibility before choosing your website technology.
Choose a platform · 3 min read
Choosing business hosting and support: questions to ask
Compare responsibility, backups, restoration and incident handling to understand what your hosting and support agreement covers.
Choose a platform · 3 min read
Shopify or WooCommerce? Compare costs, responsibility and workflow
Test the same product and order workflow, then compare ongoing costs, maintenance, integrations and exit options.
