Skip to content

Moving to ShipmailMigrate from Gmail or Workspace

Migrate from Gmail or Google Workspace

Move your email from Gmail or Google Workspace to Shipmail. This guide keeps the mail cutover apart from Google identity, Drive, billing, and account removal, which Shipmail does not control. It covers three migration paths, DNS, mailboxes, importing old mail, rollback, and common mistakes. If you are still comparing providers, start with the Gmail alternatives for business email guide. For a short overview before the technical steps, read the Gmail-to-Shipmail migration overview. If you send a third-party address through Gmail with Send as, read what the January 2027 Send as deadline covers before you pick a date for this cutover.

Last updated

Separate mail from Google identity

Changing MX records changes where new mail for your domain arrives. It does not cancel Google Workspace, rename or delete Google users, transfer Drive files, or touch an app you log in to with Sign in with Google. Those are separate decisions on the Google side. Shipmail can host and import email, but it cannot promise that Google identity, Drive access, or Google data retention will continue after you change licenses, rename users, cancel Workspace, or delete the organization.

Choose one of three migration paths

Email-only cutover

Move new mail and old mail to Shipmail. Leave the Google organization, users, subscriptions, identity, and Drive as they are.

Use it when: Choose this when you still need Google identity, Drive, Docs, Meet, or Sign in with Google for other apps, and you are not ready to change that.

  1. List every mailbox, alias, and shared role address you need, then export the Google data you want to keep.
  2. Add the domain to Shipmail. Replace Google's MX records and update SPF, DKIM, and DMARC, then wait for every Shipmail verification check to pass.
  3. Create the matching mailboxes, aliases, and shared access in Shipmail, then import old mail if you want it.
  4. Do not rename or delete Google users. The MX change routes incoming email. It does not cancel Google Workspace or move Google identity and files.
  5. Google keeps billing you for Workspace until an administrator changes or cancels the subscription.

Temporary coexistence

Send incoming mail to Shipmail, and keep the Google organization and mailboxes active for a fixed window in case you need to roll back.

Use it when: Choose this when you want to test delivery, imports, mail apps, aliases, and third-party logins before you remove anything at Google.

  1. Write down the old Google MX, SPF, DKIM, and DMARC values before you change DNS. Lower the TTL ahead of the cutover if your DNS provider allows it.
  2. Publish MX records for one provider only. Do not mix Google and Shipmail MX records as a migration strategy. Cached DNS can still send some mail to Google while the change spreads.
  3. After Shipmail verifies the domain, create the matching mailboxes and addresses, then import old mail if you want it.
  4. Check both providers during the move. Send and receive a test from every important address. If new mail reached Google, run the import again before you finish.
  5. If a test fails, restore the Google MX records you wrote down. Keep the Google accounts active until the rollback window ends.

Full Workspace exit

Move email to Shipmail. Later, as a separate step, retire the paid Workspace subscription or the Google organization, once you have decided where identity, apps, and data go.

Use it when: Choose this only once mail works and a Google Workspace administrator has approved where identities, files, calendars, contacts, groups, and recovery paths will live.

  1. List every app you log in to with Sign in with Google. Add a password, passkey, or another identity provider to each one, and test it, before you change or delete the Google account.
  2. Transfer or export Drive data, both users' My Drive files and the organization's shared drives. Check the copy before you remove anyone.
  3. Export the calendars and contacts that need to move. List the groups and aliases you need before you change mail routing, then recreate them after Shipmail verifies the domain.
  4. Ask the Google administrator whether Cloud Identity fits as an identity-only plan. Its licenses, storage, shared drives, and admin tools differ from Google Workspace, so do not count on it to keep Drive working as before.
  5. Read Google's current cancellation instructions and contract terms. Shipmail cannot cancel Workspace, preserve Google data, transfer Drive ownership, or keep third-party Google logins working.

The built-in import does this for you

Shipmail imports your Gmail history in the background. It keeps folders, labels, read state, and dates, and skips duplicates. Open your mailbox on the Mailboxes page and choose Import mail, or read the mailbox import docs. The rest of this guide covers the DNS cutover, and imapsync if you would rather run the copy yourself. At the DNS cutover, use the domain troubleshooting guide to compare the expected and published MX, SPF, DKIM, and DMARC values.

Protection while you create mailboxes

Shipmail begins holding mail when MX verification succeeds and it activates the 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 setup hold has a 1 GiB limit per domain. Keep Google active, compare both inboxes, and test each important address before you retire it.

Pre-migration checklist

Work through this list before you change anything.

  • Sign in with Google: list third-party accounts that use the Workspace identity, then add and test an alternate login and recovery method for each one before changing that identity.
  • Drive and file ownership: inventory My Drive owners, shared drives, externally shared files, storage requirements, and links that must survive; plan transfers or exports with a Google Workspace administrator.
  • Calendars and contacts: decide what stays in Google and what needs an .ics, CSV, or vCard export; confirm shared calendars and directories separately.
  • Groups and aliases: list users, role addresses, groups, aliases, forwarding rules, and filters; plan how each address should work in Shipmail after verification.
  • Recovery paths: verify super-admin access, 2-Step Verification, recovery email and phone details, domain-registrar access, and non-Google recovery methods for critical third-party accounts.
  • Sending services: identify newsletters, support tools, and transactional senders so their SPF, DKIM, and DMARC configuration remains valid after the change.
  • Mail history: decide what to import or export, and keep the source available long enough to copy late-arriving mail after Shipmail verifies the domain.
  • MX and DNS cutover: record the current DNS values, lower TTL in advance where possible, prepare Shipmail's records, and schedule external send-and-receive tests.
  • Rollback: name the person who can restore the old MX records, define the rollback threshold, and keep the previous Google setup active through the verification window.
  • Google billing and deprovisioning: check the billing plan, retention/export requirements, Cloud Identity fit, and Google's current cancellation steps with an administrator before canceling anything.

Migration steps

1. Prepare Google and your DNS

  1. Inventory the Google mailboxes, aliases, groups, forwarding rules, and shared addresses that must keep receiving mail.
  2. Export any Google data you need, record the current DNS values, and lower the DNS TTL in advance where possible.
  3. Keep every Google mailbox active through the cutover and verification window.

2. Add and verify your domain

  1. Go to the Domains page in your Shipmail dashboard and click Add domain.
  2. Publish the MX, SPF, DKIM, and DMARC records that Shipmail shows. MX is part of domain verification.
  3. If other services still send mail for the domain, merge every required SPF include into one SPF record.
  4. Use Shipmail's custom DMARC mode and a temporary policy until every remaining sender passes SPF or DKIM alignment.
  5. Wait for every DNS and sending-identity check to pass. Shipmail enables mailbox creation only after the domain is fully verified.

3. Create your mailboxes and addresses

  1. Create a Shipmail mailbox for each Google mailbox that you want to migrate.
  2. Use the same local parts you had in Google. For example, create hello@example.com to replace that Google address.
  3. Recreate the required aliases and shared access, then set the mailbox passwords for your email clients.

4. Migrate historical email (optional)

  1. Open each destination mailbox and use Import mail, or use an IMAP migration tool described below.
  2. Keep Google active while the import runs. Some mail can still reach Google until DNS caches update.
  3. Run another import after your delivery tests to copy messages that reached Google during the transition.

5. Test the cutover

  1. Send external test messages to every important mailbox and alias, then send replies from Shipmail.
  2. Check both Shipmail and Google while DNS caches update.
  3. Do not retire Google until delivery, imports, aliases, shared access, and email clients all work.

6. Update email clients

  1. Update your email client settings to point to Shipmail instead of Gmail.
  2. IMAP: mx1.shipmail.to, port 993, SSL/TLS.
  3. SMTP: mx1.shipmail.to, port 465, SSL/TLS by default.
  4. If your client explicitly asks for STARTTLS, use SMTP port 587 instead.
  5. Username: your full email address. Password: the mailbox password you set in step 3.

7. Tighten DMARC policy

  1. If you used a temporary custom DMARC policy during the move, tighten it once every sender passes SPF or DKIM alignment.
  2. Move from p=none to p=quarantine first if you still want a gradual rollout.
  3. Finish on p=reject.

IMAP migration for historical email

To copy old email from Gmail yourself, use an IMAP migration tool. It signs in to both accounts and copies the messages across.

imapsync

Open-source command-line tool for Linux, macOS, and Windows. A good choice for large mailboxes.

imapsync \
  --host1 imap.gmail.com --port1 993 --ssl1 \
  --user1 you@example.com --password1 "GMAIL_APP_PASSWORD" \
  --host2 mx1.shipmail.to --port2 993 --ssl2 \
  --user2 you@example.com --password2 "SHIPMAIL_PASSWORD"

Preparing Gmail for IMAP migration

  1. For a personal Gmail account, IMAP access is already on. For Google Workspace, ask an administrator to confirm that IMAP access is enabled for your account and that the migration client is allowed by current admin policy.
  2. Prefer a migration tool that supports Sign in with Google or OAuth. Google Workspace no longer accepts username-and-password access from less secure apps.
  3. If your account uses 2-Step Verification and Google offers App passwords for it, create a dedicated app password for the migration and revoke it afterward. If App passwords are unavailable, use an OAuth-capable tool or ask your Workspace administrator for the supported path.

Common pitfalls

Forgetting to lower TTL before cutover

If your MX record has a 24-hour TTL, some servers keep delivering to Gmail for up to 24 hours after you change it. Lower the TTL to 300 seconds at least a day before the move.

Not merging SPF records

If you keep Google's SPF include alongside Shipmail's, merge them into one record. Two separate SPF records cause both to fail.

Gmail forwarding creating loops

Once your MX records point to Shipmail, Gmail forwarding to your Shipmail address does nothing useful and can create loops. Remove it after the DNS cutover.

Treating email routing as an identity or Drive migration

Changing MX records routes incoming email. It does not rename, cancel, or delete Google accounts. Drive, Docs, Calendar, OAuth logins, licensing, and retention stay Google-side decisions. They may keep working while the account and its license stay active. Cancelling or removing the account later can cut access or delete data.

Using an obsolete Google sign-in method

Do not give a migration tool your regular Google password or look for the removed less-secure-app setting. Prefer Sign in with Google or OAuth. Use a dedicated app password only when Google offers it for your account and the migration tool requires one.

Frequently asked questions

Will I lose any email during the migration?

No migration can promise zero loss. Keep Google active while Shipmail verifies the domain, then create and test every Shipmail mailbox. Check both inboxes until DNS caches update. If mail reaches Google, run another import before you close the old mailbox.

Can I keep Gmail as a backup and forward email to Shipmail?

We do not recommend it. Once your MX records point to Shipmail, email goes straight to Shipmail. Gmail forwarding left on after the cutover adds nothing and can create loops.

How long does the IMAP migration take?

It depends on mailbox size, how hard Google throttles, and the tool. Try one typical mailbox first and leave time for retries. Then compare message counts and check recent folders.

Do I need to migrate all email, or can I start fresh?

You can start fresh. Skip step 4 (historical email migration) and set up only DNS and mailboxes. Historical email stays in your Gmail account as long as you keep it active.

What about email sent to my old @gmail.com address?

If you used a custom domain with Google Workspace, the migration covers that domain. If you also used a @gmail.com address, that address stays with Google. You can set up forwarding from the @gmail.com address to your new Shipmail address.

Does changing MX records delete my Google Drive files or Google identity?

No. MX records decide where incoming email is delivered. They do not cancel Google Workspace, delete Google users, or transfer Drive files. Those are separate Google administration actions, and canceling or deleting accounts later can affect access and retention.

Can I keep using Sign in with Google after moving email?

Usually only while the underlying Google account remains available and the third-party service still recognizes it. Changing MX records alone does not change the Google login, but renaming, canceling, or deleting the account can. Inventory every dependency and add a tested alternate login before changing Google identity.

Can Shipmail preserve or transfer Google Drive data?

No. Shipmail moves and hosts email. It does not manage Google identities, Drive ownership, shared drives, or Google's retention rules. Work with a Workspace administrator and follow Google's export and ownership-transfer documentation.

Can I keep a Google identity without a paid Workspace subscription?

Google offers Cloud Identity for identity only, but its services, storage, shared drives, and admin tools differ from Workspace. Have a Google Workspace administrator confirm the right licenses and data plan before you cancel. Moving email to Shipmail does not make that switch for you.

How do I roll back the mail cutover?

Keep the old Google setup active and save its DNS values. If a test fails, restore the previous Google MX records. DNS caches take time to update again, so watch both providers and match up messages before you try again.

Ready to plan the mail cutover?

Prepare your address list and exports before you change DNS. Once Shipmail verifies the domain, create and test the new mailboxes. Leave Google identity and data decisions to your Workspace administrator.

Set up Shipmail mailboxes