Switch providers without changing your address
Use an address on a domain you own. If your address ends in a provider's domain, switching providers means changing your address. If it ends in your own domain, you can swap the provider behind it and keep the address.
Last updated
Rented address vs owned domain
An address like yourname@gmail.com lives on Google's domain. You can forward it, but you cannot move it to another provider. An address like you@yourdomain.com belongs to whoever owns the domain. You can change the email host and people keep writing to the same address.
That is why business email belongs on a custom domain. The domain stays put, and Google Workspace, Microsoft 365, Fastmail, Shipmail, or another provider handles the mail behind it.
Why this avoids provider lock-in
The painful part of leaving a provider is telling every customer, vendor, bank, and login service that your address changed. With a custom domain, the address does not change, so switching providers is a DNS and settings job that nobody outside your team notices.
- Your website, invoices, business cards, and account logins can keep the same address.
- You can change the provider that hosts the mailbox when your needs or pricing change.
- You can create role addresses like hello@, support@, billing@, and founders@ on the same domain.
How switching providers works at a high level
1. Use an address on your own domain
The address should be something like you@yourdomain.com, hello@yourdomain.com, or support@yourdomain.com. If your address ends in gmail.com, outlook.com, or another provider-owned domain, you cannot take that exact address to another host.
2. Inventory the addresses you need
List the mailboxes, aliases, forwarding rules, catch-all settings, and shared addresses at your old provider. Record what each address should become at the new host.
3. Plan what happens to existing mail
A provider switch changes where new mail arrives. It does not copy your old inbox. Export the messages you need, keep the old account open during the move, or use the migration tools your old and new providers support.
4. Add and verify the domain
MX records live in your domain's DNS settings and tell the internet where to deliver mail. Shipmail verifies MX, SPF, DKIM, and DMARC before it lets you create mailboxes.
5. Recreate, import, and test
Once Shipmail verifies the domain, create the matching mailboxes and address rules. Import old mail, send a test to each important address, and keep the old provider active until every test arrives.
Your domain, unchanged
yourdomain.com
you@yourdomain.com
MX record points to
Old provider
Was receiving mail
Shipmail
Now receiving mail
Mail delivery follows the MX record. The address never changes.
Protection while you recreate addresses
Shipmail begins holding mail when MX verification succeeds and it activates your domain, before the remaining verification checks finish. The 48-hour setup window starts when Shipmail records the domain as fully verified. During that window, creating a matching mailbox or alias releases non-spam mail addressed to it in the To or Cc field.
The hold has a 1 GiB limit per domain. Keep the old provider active, compare both inboxes, and test each important address before closing it.
Mailboxes, aliases, and forwarding
Mailboxes, aliases, forwarding, and shared inboxes behave differently, so write down what each address does before you move. For the differences, read the mailbox vs alias vs forwarding guide.
These settings do not follow the address to the new provider. Recreate each one, then test every important address after you change DNS.
Check address portability before cutover
Owning the domain makes the address portable. Provider settings are a different story. You usually rebuild alias destinations, catch-all rules, forwarding rules, and wildcard subdomain routing at the new provider.
If you want an address to survive a future provider move, put it on a domain you control. Shipmail aliases already follow that rule, because they can only use a verified domain in your organization. Shipmail does not issue provider-owned masked aliases. The warnings below are about addresses and routing at your old provider.
| Address pattern | Portability | Shipmail behavior |
|---|---|---|
Regular aliasbilling@yourdomain.com | Portable address, manual setup | Keep the same address when you control the domain. Recreate the alias and its destination in Shipmail after verifying the domain. |
Catch-all or wildcardanything@yourdomain.com | Portable domain, provider-specific rule | Shipmail supports one catch-all destination per verified domain. Enable it manually because the old provider's routing rule does not move with DNS. |
Plus addressingyou+shop@yourdomain.com | Portable when the base address moves | Plus addressing is on by default for every mailbox. Recreate the base address, then test any tagged address used as an account login. There is no separate tag list to import. |
Masked or provider-owned aliasrandom@provider.example | Not portable | You cannot recreate the same address in Shipmail because you do not control its domain. Keep forwarding active during the transition and update each account that uses it. |
Custom subdomainanything@project.yourdomain.com | Portable if you control its DNS | Add and verify the subdomain as a separate Shipmail domain. Provider-specific wildcard routing across many subdomains is not imported, so set up each subdomain you use. |
Multiple domainshello@brand-one.com and hello@brand-two.com | Portable when you own every domain | Add and verify each domain. A Shipmail alias can use any verified domain in the organization and deliver into one existing mailbox. |
What Shipmail imports and exports today
Mailbox import copies messages from connected IMAP accounts or supported files. It keeps folders, read state, and original dates, and it can import contacts from supported sources. It does not create domains, mailboxes, aliases, catch-all settings, forwarding rules, DNS records, or provider-specific filters.
Shipmail account export creates one ZIP per active, provisioned mailbox with email, calendars, and contacts. Archived, suspended, and unprovisioned mailboxes are skipped. A separate metadata ZIP lists domains and eligible mailboxes with profile, API key, webhook, and audit information. It does not currently provide a migration-ready export of alias assignments, catch-all settings, forwarding rules, or DNS records. Keep your own address inventory for those settings.
What stops at your old provider
Settings saved at your old provider stay there. They stop working the moment your MX records point to Shipmail, and nothing warns you, so note them before you switch and set them up again on each new mailbox:
- Forwarding, for example a copy of every message to a personal address. Set it up again under mailbox forwarding.
- Auto-replies, such as an out-of-office message. Set them in the mailbox's Incoming mail settings.
- Inbox rules that sorted or flagged mail. Recreate them as inbox rules. From Outlook, Bring rules from Outlook has the AI assistant propose each one.
- Signatures. Add one in the mailbox's settings.
A new mailbox shows the same list on its settings page for its first 30 days, with a button to each setting.
Provider-to-Shipmail mapping example
| Old provider | Build in Shipmail after verification |
|---|---|
| hello@acme.com is a mailbox | Create hello@acme.com as a mailbox, then import its mail. |
| billing@acme.com is an alias for hello@acme.com | Create billing@acme.com as an alias on the hello@acme.com mailbox. |
| *@acme.com delivers to hello@acme.com | Enable catch-all for acme.com and select hello@acme.com as the destination. |
| founder+github@acme.com is used for a login | Create founder@acme.com. No tagged alias is needed, but test the exact login address. |
| *@updates.acme.com uses provider wildcard routing | Add updates.acme.com as a separate domain, verify it, then enable its catch-all. |
| random@provider.example is a masked alias | Keep the old alias forwarding for now and change the address at the account that uses it. |
Pre-migration inventory and export checklist
- Export your old provider's address or alias list if it offers one. Otherwise copy or screenshot the settings before you cancel.
- List every mailbox, regular alias, catch-all or wildcard, plus address used as an account login, masked address, forwarding rule, custom subdomain, and shared inbox.
- Mark whether you control the domain for each address. An address on a provider-owned domain cannot move with you.
- Write down where each address delivers today and what it should become in Shipmail.
- Decide whether you need old mail copied, exported, or kept in the old account for reference.
- Lower DNS TTL ahead of time if your DNS host lets you and you want faster cutover control.
- Add the domain to Shipmail, publish its MX, SPF, DKIM, and DMARC records, and wait for every verification check to pass.
- Create the matching mailboxes, aliases, forwarding rules, shared access, and catch-all settings in Shipmail.
- Test every important address, catch-all, and reply path after Shipmail creates the matching destinations.
- Keep the old provider active long enough to catch missed settings or delayed DNS propagation.
Where Shipmail fits
Shipmail hosts custom-domain business email without running your own mail server or buying a full office suite. Add your domain, copy the DNS records shown in the dashboard, verify the domain, then create the mailboxes your team needs.
If you are setting up domain email for the first time, start with the hello@yourdomain.com guide. If you already know you want to move a domain to Shipmail, follow the custom domain email setup guide.
Frequently asked questions
Can I keep my email address if I leave my provider?
Yes, if the address is on a domain you own, such as you@yourdomain.com. The address belongs to your domain, not to the provider, so you point the domain's MX records at the new host and recreate the same mailboxes there. An address on the provider's own domain, such as @gmail.com or @outlook.com, cannot move with you.
Will I lose my email if I transfer my domain?
No, as long as the domain's DNS records come with it. Moving a domain to another registrar does not change where mail is delivered. Mail stops only if the MX, SPF, DKIM, and DMARC records are lost, which can happen when the new registrar also starts hosting your DNS. Copy those records before you switch nameservers.
Can I keep my Gmail address if I leave Gmail?
You can keep using a Gmail account only inside Google's consumer mail service. The portable setup is to use your own domain, such as you@yourdomain.com, with Gmail, Google Workspace, Shipmail, Fastmail, Microsoft 365, or another host behind it.
What are MX records?
MX records are DNS records that say which mail servers receive email for your domain. They are the main switch you change when moving inbound mail from one provider to another.
Do aliases move automatically?
No. Aliases, forwarding rules, and shared mailboxes are provider settings. For a Shipmail move, inventory them first, verify the domain, then recreate them before retiring the old provider.
Will my old messages move automatically?
No. Changing DNS affects new mail routing. Existing mail stays with the old provider unless you export it, import it, or use a migration tool supported by the providers involved.