Is a domain change the same as tenant migration?

Not always. A domain change may involve new user addresses inside the same or a different managed environment, while tenant migration specifically moves users between managed Google Workspace environments.

Can old and new email addresses differ?

Yes. Prepare explicit source-to-target mappings when addresses change.

When should DNS or mail-flow changes be made?

Make final mail-flow changes only after the target has been prepared and the migrated data has been validated.

Can migration be staged?

Yes. Pilot users, production waves and incremental follow-up runs can reduce cutover risk.

What data is preserved during a domain migration?

The supported Google Workspace API workflow can migrate emails, attachments, calendars, contacts, tasks and label organization. Validate representative records during the pilot.

How do I handle aliases and shared identities?

Document each alias and shared identity in the mapping table and confirm ownership before migration so none are missed.

Will users keep their old address during the change?

That depends on your addressing plan. Record old and new addresses in the mapping table and communicate the change to users before cutover.

What should I test after the DNS change?

Confirm sign-in, validate target addresses, verify representative messages, calendars, contacts and tasks, and test inbound and outbound mail flow.

Is technical support available?

Yes. EdbMails provides 24/7 free technical support during domain migration projects.

Reseller
Products
EdbMails

All-in-one Recovery and Migration
- EDB Recovery and Migration
- OST, PST, MBOX, NSF, EML, MSG
- Office 365, Exchange Migration
- SharePoint, OneDrive & Teams
- Google Workspace Migration
- IMAP Migration
- Duplicate Remover
- EdbMails Data Recovery
- Backup Solutions
All Products
EDB Recovery and Migration

EdbMails lets you recover corrupted, damaged, and offline Exchange EDB files, convert EDB mailboxes to PST format, and directly migrate mailbox data to Office 365 and live Exchange Server.

EDB to PST

Recover corrupted, damaged, offline EDB files and convert Exchange EDB mailboxes to PST file format

Public Folder to Exchange

Migrate public folders from an Exchange offline EDB file to live Exchange Server

EDB to Live Exchange Migration

Directly migrate offline Exchange database (EDB) files to live Exchange server

Archive Mailbox to Office 365

Migrate archive mailboxes from offline EDB files directly to Office 365

EDB to Office 365 Migration

Directly migrate offline Exchange database (EDB) files to Office 365

Public Folder to Office 365

Migrate public folders from an offline Exchange EDB file to Office 365

OST, PST, MBOX, NSF, EML, MSG Export and Migration

EdbMails lets you to recover OST and PST files, export OST, PST, MBOX, NSF, EML, and MSG files to PST files, and directly migrate OST, PST, MBOX, and NSF mailbox data to Office 365 and live Exchange Server.

OST Recovery and Migration

Recover offline OST files, convert OST to PST, and migrate OST to Office 365 and Exchange Server

PST Recovery and Migration

Recover Outlook PST files , Export PST to PST, migrate PST to Office 365 and Exchange Server

MBOX Export and Migration

Export MBOX to PST, migrate MBOX to Office 365 and Exchange Server

NSF Export and Migration

Export NSF to PST, migrate NSF to Office 365 and Exchange Server

EML to PST Export

Convert EML files to Outlook PST files

PST to MSG Export

Convert Outlook PST file to MSG file format

MSG to PST Export

Export MSG files to Outlook PST files

Office 365, Exchange Migration

EdbMails lets you securely migrate mailboxes across Microsoft 365, Exchange, Google Workspace (G Suite), and IMAP-supported servers such as Outlook, Gmail, Zimbra, Zoho Mail, and cPanel, ensuring zero downtime.

Office 365 Migration

Migrate between Office 365 tenants, Office 365 to Exchange, Office 365 to PST, PST files to Office 365.

Exchange Migration

Migrate between any Exchange Servers, Exchange to Office 365, Exchange to PST, PST files to Exchange.

Tenant to Tenant Migration

Migrate Mailboxes, Public Folders, Archive Mailboxes between Office 365 Tenants.

Exchange to Office 365

Migrate Mailboxes, Public Folders, Archive Mailboxes from live Exchange server to Office 365.

Office 365 to IMAP

Migrate Office 365 to IMAP, Office 365 to Gmail, Office 365 to Outlook, Office 365 to Zoho etc.

Exchange to IMAP

Migrate from live Exchange Server to IMAP servers such as Gmail, Outlook, and Zoho Mail.

Public Folder to Office 365

Migrate Public Folders between Office 365 tenants with complete folder hierarchy and mailbox data integrity.

Exchange to PST

Export live Exchange Server mailboxes, public folders, and archive mailboxes to Outlook PST files.

SharePoint, OneDrive & Microsoft Teams Migration

EdbMails lets you migrate SharePoint sites, OneDrive data, Microsoft Teams, teams, channels, chats, permissions, and documents between Microsoft 365 tenants while maintaining the existing folder structure and data integrity.

SharePoint Online Migration

Migrate documents, lists, files and folders from SharePoint sites.

OneDrive for Business Migration

Migrate documents, lists, files, folders, private chats from OneDrive.

Microsoft Teams Migration

Migrate Teams, chats, channels, documents, files and folders etc.

Google Workspace / G Suite Migration

EdbMails offers secure Google Workspace migration to Office 365, Exchange, or IMAP, and export to PST covering emails, contacts, calendars and tasks.

Google Workspace Migration

Migrate emails, calendars, contacts, tasks from Google Workspace to Google Workspace, office 365, Exchange and IMAP. Export to PST

Google Workspace to Office 365

Migrate emails, calendars, contacts, tasks from Google Workspace / G Suite to Office 365

Google Workspace to Exchange Server

Migrate emails, calendars, contacts, tasks from Google Workspace / G Suite to on-Premise Exchange Server

Google Workspace to IMAP

Migrate emails, calendars, contacts, tasks from Google Workspace / G Suite to IMAP, Outlook, Zimbra, Zoho etc.

Google Workspace to Google Workspace

Migrate emails, calendars, contacts, tasks between two Google Workspace / G Suite tenants

Google Workspace to PST

Export emails, calendars, contacts, tasks from Google Workspace / G Suite to Outlook PST files

IMAP Migration

EdbMails IMAP Migration tool lets you easily migrate emails from IMAP servers such as Outlook, Gmail, Zoho Mail, Zimbra, cPanel, and more. Supports IMAP to IMAP, Office 365, Exchange Server, PST, and bulk PST to IMAP migration.

IMAP Email Backup & Migration

Backup and migrate emails from IMAP servers to PST, Office 365, and On-Premises Exchange Server

IMAP to Office 365

Migrate emails, folders, and attachments from IMAP servers to Office 365

IMAP to Exchange

Migrate emails, folders, and attachments from IMAP servers to on-premises Exchange Server

IMAP to PST

Export emails, folders, and attachments from IMAP servers to Outlook PST files for backup

PST to IMAP

Migrate emails, folders, and attachments from bulk PST files to IMAP servers

Duplicate Remover

EdbMails Duplicate Remover lets you easily remove duplicate items from Office 365 and Exchange Server, and from IMAP, Outlook, Gmail, Zimbra, Zoho Mail, etc., ensuring a clean and organized mailbox.

Remove Duplicates

Easily clean up your Office 365, Exchange, Outlook and IMAP accounts by removing duplicate emails.

Remove Duplicates from Office 365

Remove duplicate emails, calendars, contacts, journal tasks, etc. from Office 365.

Remove Duplicates from Exchange Server

Remove duplicate emails, calendars, contacts, journal tasks, etc. from live Exchange Server.

Remove Duplicates from IMAP, Outlook

Remove duplicate emails, attachments from IMAP, Outlook, Gmail, Zimbra, Zoho Mail etc.

Exchange, SharePoint, OneDrive, Teams and Office 365 Backup

EdbMails enables secure, automated backup and recovery for Microsoft 365 services including Exchange Online, SharePoint, OneDrive, Teams, and Live Exchange Server with complete data protection and restore flexibility.

Office 365 Backup

Incremental, Granular, Encrypted and Compressed Office 365 Mailboxes Backup

Exchange Server Backup

Incremental, Granular, Encrypted and Compressed Exchange Mailboxes Backup

SharePoint, OneDrive & Teams Backup

Backup Online site collections, Team sites, Office 365 groups, all documents etc.

EdbMails Data Recovery

EdbMails Data Recovery Software lets you recover permanently deleted data, including photos, videos, documents, and archived files, from partitions on hard drives, SSDs, USB drives, SD cards, and external storage devices.

EdbMails Data Recovery

Recover and restore permanently deleted data from hard drives, SSDs, USB drives, SD cards, and etc.

Whitepaper

Request a Demo

Sign Up

Google Workspace Domain Migration

Move mailbox data during a Google Workspace domain transition

EdbMails helps migrate supported Google Workspace mailbox data when users are moving to accounts associated with a new domain or destination environment. Map existing source users to the required target accounts, migrate in controlled batches, apply filters where appropriate, and perform incremental migration passes as the organization prepares for the final domain transition.

Just $299 for 100 Mailboxes

Google Workspace to Microsoft 365 Migration Google Workspace to Google Workspace Migration Google Workspace to Exchange Migration Google Workspace to IMAP Migration Google Workspace to PST Export Google Workspace Admin Configuration

Google Workspace Migration Software Now on Azure Marketplace!

Product Menu

Separate mailbox migration from your Google Workspace domain cutover

A Google Workspace domain migration is required when an organization changes its email domain, rebrands, restructures business units, or moves users into another managed Google Workspace environment with different addresses. The data migration and the DNS/domain transition should be planned as related but separate workstreams.

EdbMails moves supported mailbox data between Google Workspace environments while administrators prepare the target users and the source-to-target identity mapping.

Data migration Address mapping DNS cutover

What a domain migration involves

A domain migration combines two distinct kinds of change. Keeping them separate is the single most important planning decision — changing mail flow before the data and target accounts are ready is what causes delivery gaps.

The data stream

The user data that must be preserved — handled by the supported Google Workspace migration workflow for mailboxes, calendars, contacts, tasks and labels.

The addressing stream

The addressing or DNS change that gives users their new identity — handled by preparing target users, mapping old addresses to new, and changing DNS only after verification.

Common domain migration scenarios

Corporate rebranding

Company name change

Subsidiary to parent domain

Consolidating multiple domains

New environment for a reorganized unit

Map old addresses to new addresses

Where source and target addresses differ, create an explicit mapping table. Review aliases, renamed users, shared identities and exceptions before the bulk migration begins — the mapping table is the reference every later step depends on, so it should be signed off before any production run.

Item	Why it matters	Action before migration
Renamed users	New address must receive the right data	Record old and new address in the mapping table.
Aliases	Secondary addresses affect delivery and identity	Document each alias and its target.
Shared identities	Shared mailboxes or groups can be missed	List them explicitly and confirm ownership.
Exceptions	Some users may not change or move	Mark them clearly so they are excluded.

Separate data migration from mail-flow cutover

Do not change production mail flow simply because the first migration pass has completed. Prepare and validate the target users, run pilot and production migration, perform incremental follow-up runs, verify the destination, and then make the agreed domain or mail-routing changes.

Preserve supported mailbox data

The supported Google Workspace API workflow migrates emails, attachments, calendars, contacts, tasks, labels or folder organization, and supported metadata. Validate representative records where address changes could affect display or ownership expectations.

Email & attachments

Calendars

Contacts

Tasks

Labels / folders

Step-by-step domain migration

1
Inventory the scope
Inventory users, aliases and supported data types in scope.
2
Prepare target users
Prepare the target users and assign required licenses on the new domain or environment.
3
Build the mapping table
Build and review the old-to-new address mapping table.
4
Run a pilot
Run a pilot with users whose addresses change.
5
Validate the pilot
Validate migrated data and target addressing on the pilot accounts.
6
Migrate in waves
Run the production migration in controlled waves.
7
Incremental follow-up
Run incremental follow-up passes to capture new or changed items.
8
Verify the destination
Verify the destination thoroughly before any cutover.
9
Make the DNS change
Make the agreed DNS or mail-routing changes and test inbound and outbound mail.

Staged migration & best practices

A staged approach is especially useful for domain changes: migrate a small pilot first, then move users in controlled waves, using incremental runs to reduce the change left for the final transition.

Make the DNS change last

Treat the DNS or MX change as the last step, gated on verification — not a trigger that follows the first successful data pass.

Communicate new addressing

Tell users the new addressing ahead of cutover so they know when and where to sign in.

Pilot address-change accounts

Pilot specifically with accounts whose addresses change — that is where display-name and ownership expectations surface.

Keep the source reachable

Keep the source reachable until the destination is confirmed, so no user is left without access.

Verification after domain migration

Confirm users can sign in to the target environment.
Validate mailbox mapping and target addresses.
Verify representative messages, calendars, contacts and tasks.
Review migration logs.
Test inbound and outbound mail after any final DNS or routing changes.

Common issues to watch for

Changing MX/DNS too early

Changing MX or DNS records before the target is verified can interrupt delivery — the most damaging mistake in a domain migration.

Missed aliases or shared identities

A common data gap. They belong explicitly in the mapping table so none are overlooked before migration.

Address-driven display changes

Address changes can affect how some items display, so validate representative records on the pilot accounts before scaling.

Frequently asked questions

Is a domain change the same as tenant migration?
Not always. A domain change may involve new user addresses inside the same or a different managed environment, while tenant migration specifically moves users between managed Google Workspace environments.
Can old and new email addresses differ?
Yes. Prepare explicit source-to-target mappings when addresses change.
When should DNS or mail-flow changes be made?
Make final mail-flow changes only after the target has been prepared and the migrated data has been validated.
Can migration be staged?
Yes. Pilot users, production waves and incremental follow-up runs can reduce cutover risk.
What data is preserved during a domain migration?
The supported Google Workspace API workflow can migrate emails, attachments, calendars, contacts, tasks and label organization. Validate representative records during the pilot.

How do I handle aliases and shared identities?
Document each alias and shared identity in the mapping table and confirm ownership before migration so none are missed.
Will users keep their old address during the change?
That depends on your addressing plan. Record old and new addresses in the mapping table and communicate the change to users before cutover.
What should I test after the DNS change?
Confirm sign-in, validate target addresses, verify representative messages, calendars, contacts and tasks, and test inbound and outbound mail flow.
Is technical support available?
Yes. EdbMails provides 24/7 free technical support during domain migration projects.

Google Workspace Domain Migration

Move mailbox data during a Google Workspace domain transition

Just $299 for 100 Mailboxes

Separate mailbox migration from your Google Workspace domain cutover

What a domain migration involves

The data stream

The addressing stream

Common domain migration scenarios

Map old addresses to new addresses

Separate data migration from mail-flow cutover

Preserve supported mailbox data

Step-by-step domain migration

Inventory the scope

Prepare target users

Build the mapping table

Run a pilot

Validate the pilot

Migrate in waves

Incremental follow-up

Verify the destination

Make the DNS change