page-banner-shape-1
page-banner-shape-2

How to Migrate Your Business Email to Google Workspace in Easy Steps

  • Ajay Singh Raghav
  • November 19, 2026
Google Workspace email migration

How to Migrate Your Business Email to Google Workspace in Easy Steps

Google Workspace email migration

Moving company email to a new platform sounds simple until the first mailbox goes missing, the first message bounces or the first customer says that nobody replied. A planned Google Workspace email migration avoids those problems by copying old mail into new Gmail accounts, switching the domain mail routing at the right moment and proving that every sender is authenticated. This guide shows the whole process in plain steps, from preparation to cleanup. 

The advice here is based on current Google documentation and corrects several points that older articles still repeat. The most important correction is that an IMAP based Google Workspace email migration copies email and label data only, so contacts and calendars need separate handling. Other changes include the new name of the data import tool, the single MX record that Google now recommends and the stricter sender authentication rules that Gmail enforces. 

Whether you run a five person office on cPanel hosting or a company with hundreds of mailboxes, a careful Google Workspace email migration follows the same logic: verify the domain, create users, copy mail, move contacts and calendars, switch DNS and authenticate the domain. The sections below explain each step, the tools Google provides for each size of project, the mistakes that cause lost mail and the compliance points that matter in India. 

What Google Workspace Email Migration Involves in 2026 

A Google Workspace email migration moves mail from an existing source, such as a hosting control panel mailbox, an IMAP server, Microsoft Exchange, Microsoft 365 or another Gmail account, into Gmail inside Google Workspace. It has four separate parts that are often confused: copying old messages, moving contacts and calendars, redirecting new mail through DNS and securing the domain with authentication records. Each part uses different tools and can succeed or fail on its own. 

Google publishes a migration product matrix that maps every data source and project size to a recommended tool. For IMAP servers, the self service data import tool in the Admin console is intended for projects of up to 100 users, and Google Workspace Migration for Microsoft Exchange, usually shortened to GWMME, handles larger IMAP projects. Larger Google Workspace to Google Workspace moves use Google Workspace Migrate for projects above 1,000 users. The table below summarises the main options. 

Situation Recommended Tool What It Moves 
IMAP mail server, up to 100 users, trusted TLS certificate, reachable from the internet Data import tool in the Admin console Email and label data only 
IMAP server on a private network, without a trusted certificate or using plain usernames GWMME, a Windows based tool Email and label data only 
IMAP server with 101 to 1,000 users GWMME Email and label data only 
Users with local PST files Google Workspace Migration for Microsoft Outlook Mail, calendar and contacts from PST files 
Contacts exported as CSV or VCF files Import in Google Contacts Contacts 
Calendar exported as an ICS file Import in Google Calendar Calendar events 

Sources such as Microsoft Exchange and Microsoft 365 have their own migration paths in the same matrix, and a project of that kind should start by checking the matrix for the exact source and size. CloudMinister explains its deployment and migration support on its Google Workspace page, and the background of the product is summarised in the Google Workspace entry on Wikipedia. 

Why Businesses Choose Google Workspace Email Migration 

Companies decide on a Google Workspace email migration for practical reasons that show up in daily work. Gmail on your own domain gives a professional address and shows no advertising. Spam and phishing filtering, malware scanning and 2 Step Verification are part of the platform, and storage is pooled across users. Google commits to a 99.9 percent monthly uptime target for core Workspace services, which allows about 43 minutes of downtime in a 30 day month, and the CloudMinister article on 99.9 versus 99.99 percent SLA downtime explains what such numbers mean in practice. 

Email is also the doorway to the rest of the suite. After a Google Workspace email migration, the same account opens Drive, Docs, Sheets, Meet, Chat and Calendar, and Gemini features are included in paid business plans. The CloudMinister guides to cloud based productivity with Google Workspace and business gains from Google Workspace describe these benefits in more detail, and the article on Google Workspace for business compares the plans. 

Older versions of this article quoted worldwide user counts and a starting price in rupees. Those figures change often and have been removed. Current prices are explained in the CloudMinister guide to Google Workspace pricing India. 

Planning and Budgeting for Google Workspace Email Migration 

Good planning decides how smooth a Google Workspace email migration will be. Start with a simple inventory: the number of mailboxes, the size of each, the aliases and forwarding rules, mailing lists and shared mailboxes, the source server type and the place where the domain DNS is managed. This inventory drives the choice of plan and tool. 

Plan choice is mainly a storage and feature question. Business Starter pools 30 GB per user, Business Standard 2 TB and Business Plus 5 TB, so the combined size of all mailboxes and files should fit inside the pool of the chosen plan. Standard adds meeting recording, and Plus adds Google Vault for retention and eDiscovery, which matters when old mail must be preserved for legal reasons. Official annual prices are 7, 14 and 22 US dollars per user per month, flexible billing costs about 20 percent more, and Indian invoices carry 18 percent GST. The official Google Workspace pricing page lists current details. 

Schedule matters as well. Choose a low activity period, such as a weekend, for the DNS switch, tell staff and key clients in advance, and keep a rollback plan that allows the old mail system to stay available for a period after the change. 

Pre Migration Checklist for Google Workspace Email Migration 

Before a Google Workspace email migration copies its first message, confirm the items below. Most failed migrations trace back to a missing item on this list. 

  • Super administrator access: the data import tool and GWMME both require a super administrator in Google Workspace. 
  • Domain control: login to the domain registrar or DNS host, because verification and mail routing need DNS changes. CloudMinister customers can manage names through domain registration and domain transfer services. 
  • Source server access: IMAP must be enabled, the IMAP hostname and port are known and each user password is available. For the data import tool the source server needs a trusted TLS certificate and must be reachable from Google services. 
  • Multi factor authentication on the source: accounts that use 2 step verification may need app passwords or a temporary relaxation so that the migration can sign in. 
  • Licences and accounts: every destination user must exist in Google Workspace with a licence assigned before data can be copied. 
  • Mailbox sizes: record the size of every mailbox and identify very large ones and very large attachments. 
  • Backups: take a complete backup of the old mailboxes. The CloudMinister article on immutable backups for ransomware protection explains how to keep copies that cannot be altered. 
  • Communication plan: prepare a short notice for staff and, where needed, clients. 

Hosting that uses cPanel needs one more check. When a domain already has mail on a cPanel server, the Email Routing setting for the domain must be changed to Remote Mail Exchanger after the switch so that mail from the website and server is delivered to Google instead of staying on the local server. Businesses that use shared hosting with cPanel and Workspace together should make this change as part of the migration. The cPanel server support page describes related services. 

Step 1 in Google Workspace Email Migration: Add and Verify the Domain 

The first step of a Google Workspace email migration proves to Google that you control the domain. Sign in to the Google Admin console as a super administrator, open the Account section, go to Domains and Manage domains, choose Add a domain and enter the name. Google then offers verification methods, and the TXT record method is the most common. 

Google shows a text value that begins with google-site-verification. In the DNS zone of the domain, add a TXT record at the root of the domain, shown as a blank host or the at sign depending on the DNS provider, and paste the value exactly. A default TTL of 3600 seconds is fine. Return to the Admin console and click Verify. Verification is often quick, but DNS changes can take up to 48 hours to appear everywhere, so do not recreate the record while waiting. 

Once the domain is verified, Google prompts you to activate Gmail for it. Activating Gmail shows the mail routing records that will be needed later, but mail delivery should not be switched until the data has been copied. Verifying early lets the team create users with the final addresses and prepare everything else without touching live mail. 

Step 2 in Google Workspace Email Migration: Create Users and Licences 

Next, the Google Workspace email migration needs its destination accounts. Add each user with the final business address, assign the chosen licence and set a temporary password that the user changes at first sign in. Use one naming convention, such as first name dot last name, so that addresses look consistent and administration stays simple. 

Recreate aliases and shared addresses. Alternate addresses for a person can be added as aliases on the same account, and shared addresses such as sales or support can often be handled with a Google Group that works as a collaborative inbox, which avoids paying for a full user seat. Organise users into organisational units if different teams need different settings, and enforce 2 Step Verification from the start. Users who will receive migrated mail must be active and licensed, because suspended or unlicensed accounts cannot take part in the copy. 

Step 3 in Google Workspace Email Migration: Prepare the Source Mail Server 

A Google Workspace email migration works only if the source system allows Google to read its mailboxes. Confirm that IMAP is enabled, note the IMAP server name and the secure port, usually 993 with SSL or TLS, and check that no firewall blocks connections from Google. The data import tool needs a trusted TLS certificate on the source server, which is a certificate issued by a recognised authority and not a self signed one. A valid SSL certificate on the mail host usually meets this requirement. 

Google requires each user IMAP password together with the IMAP and Workspace email addresses. For a small project these can be entered one by one, and for several mailboxes they are placed in a CSV file with the source address, the destination address and the password. Because this file holds passwords, it should be created only when needed, shared with nobody and deleted after the migration finishes. 

If the source server sits on a private network, has no trusted certificate or signs in with plain usernames that are not email addresses, the data import tool will not work and GWMME is the correct choice. GWMME runs on Windows and connects from inside the network. 

Step 4 in Google Workspace Email Migration: Run the Data Import 

With preparation complete, the copy phase of the Google Workspace email migration is short. In the Admin console open Data, then Data import and export, then Data import. Older guides call this screen Data migration, but the current name is Data import. Sign in as a super administrator, choose IMAP and start the import. Enter the IMAP server and port, then add the users by typing them in or uploading the CSV file. The Google guide to IMAP migration describes the screens and the requirements. 

The import settings allow a start date, so only messages from that date onward are copied, and options to include deleted and junk mail. A shorter date range copies faster and can be followed by a second pass for older mail if the team needs it. Start with a small pilot of one or two users, check the result and then continue with the rest in batches. 

Folders on the source become labels in Gmail, and the tool copies email and label data only. Large mailboxes can take hours or days, and speed is limited by the source server, the network and Google throttling, so large batches should start before a weekend or another quiet period. The Admin console shows the progress and any errors for each user, and failed users can usually be corrected and retried. 

Step 5 in Google Workspace Email Migration: Move Contacts, Calendars and PST Files 

An IMAP based Google Workspace email migration does not move calendar events, calendar resources, contacts, Google Drive files or Google Sites. Treating the mail copy as the whole migration is the most common mistake in older guides, and users notice quickly when their address book is empty. 

  • Contacts: export contacts from the old system as CSV or vCard files and import them in Google Contacts. 
  • Calendars: export calendar events as ICS files and import them in Google Calendar. 
  • PST files: users who keep mail, calendars and contacts in local Outlook files can use Google Workspace Migration for Microsoft Outlook. 
  • Exchange and Microsoft 365 sources: these have dedicated tools that can include mail, calendars and contacts, and the migration matrix lists the right one for each size. 

Teams that are moving from Microsoft software should also review the CloudMinister page on Microsoft 365 if some users will stay on that platform during a transition. A mixed period is possible, but it requires careful mail routing so that messages reach the correct mailbox. 

Step 6 in Google Workspace Email Migration: Switch MX Records and Activate Gmail 

The MX switch is the moment in a Google Workspace email migration when new mail starts arriving in Google Workspace. Prepare for it a day or two earlier by lowering the TTL of the current MX records, for example to 300 seconds, so that the change spreads quickly. After the data copy is verified, edit the DNS zone at the planned time. 

Google now recommends a single MX record. Create an MX record at the root of the domain with priority 1 and the value smtp.google.com, and delete every other MX record from the previous provider. Domains set up before 2023 may still use the older set of five aspmx records, which continue to work, but a mixture of old and new sets should be avoided. An MX record must point to a host name and never to an alias. In the Admin console, complete the Activate Gmail step for the domain. 

DNS changes can take up to 48 hours to appear everywhere, although they are usually much faster. Verify the result with the Google MX checker or by running a DNS lookup for the MX records of the domain, which should show only smtp.google.com. During propagation some senders still deliver to the old server, so keep the old mail system running for at least a week, check its mailboxes for late messages and copy anything that arrived there after the main import. Raise the TTL again once everything is stable. 

Step 7 in Google Workspace Email Migration: Configure SPF, DKIM and DMARC 

Mail that arrives correctly must also be trusted by recipients. Since February 2024, Gmail requires bulk senders to authenticate their mail, and all senders should publish SPF or DKIM records. A complete Google Workspace email migration therefore ends with three authentication records. 

  • SPF: publish one TXT record at the root of the domain with the value v=spf1 include:_spf.google.com ~all. A domain may have only one SPF record, so if one already exists, merge the Google include into it and keep any other legitimate senders, such as your website mail or marketing platform, in the same record. 
  • DKIM: generate the key in the Admin console under the Gmail authentication settings, publish the TXT record that Google provides at the google domainkey host name and then start authentication. 
  • DMARC: publish a TXT record at the _dmarc host name. Start with a monitoring policy such as v=DMARC1; p=none, review the reports and move to quarantine and then reject when legitimate mail all passes. 

These records reduce spoofing and improve inbox placement, and they are the foundation of email trust. Any other service that sends mail for the domain, such as a billing system or newsletter tool, must be added to SPF and, ideally, set up with its own DKIM key. 

Verifying and Cleaning Up After Google Workspace Email Migration 

Verification turns a finished Google Workspace email migration into a trusted result. Sign in as several users, compare folder structures and message counts with the source, open a sample of old messages and attachments and search for a few known senders. Send and receive test messages between internal addresses and to external providers, and check that replies arrive in the correct inbox. 

Then update the devices. Users should add the Google account to the Gmail app on phones and, if they use a desktop client, reconfigure it for Google. Check signatures, forwarding rules, out of office replies and filters, because rules are not copied by an IMAP import. Confirm that website forms, printers, scanners and applications that send mail now use Google or an approved relay with correct authentication. 

Keep the old mail system and its backups for an agreed retention period, then retire it. Document the final DNS records, admin accounts and passwords in a secure place. Review the sign in and audit reports in the Admin console during the first weeks to catch unexpected activity. 

Common Problems in Google Workspace Email Migration and How to Fix Them 

Most Google Workspace email migration problems repeat from project to project, and the table below lists the usual symptoms and their causes. 

Problem Likely Cause Fix 
Login failed for a user Wrong password, IMAP disabled or multi factor authentication on the source Check the password, enable IMAP and use an app password if needed 
Server cannot be reached Firewall, wrong port or private network Open the port to Google or use GWMME inside the network 
Certificate error Self signed or untrusted TLS certificate Install a trusted certificate or use GWMME 
Contacts and calendar missing IMAP copies mail and labels only Import CSV, VCF and ICS files or use the correct tool 
Mail still goes to the old server MX not updated, high TTL or cached DNS Check records, wait for propagation and use the MX checker 
Messages land in spam Missing or duplicate SPF, no DKIM or DMARC Merge SPF into one record and publish DKIM and DMARC 
Migration very slow Large mailboxes and source or Google throttling Migrate in smaller batches and during quiet hours 

When a problem persists, collect the exact error from the Admin console, test the IMAP login from a separate mail client and check DNS from an independent location. Solving the cause on one user usually solves it for the whole batch. 

Security and Compliance in Google Workspace Email Migration 

A migration handles passwords and complete mail archives, so security needs attention. Share credentials only with the people doing the work, use temporary passwords for new accounts and require 2 Step Verification before users start working. Delete the CSV file with source passwords as soon as the copy ends, and change any source passwords that were shared. 

For Indian organisations, the key law is the Digital Personal Data Protection Act 2023, being brought into force through the Digital Personal Data Protection Rules 2025, notified in November 2025. Most substantive duties take effect about 18 months later, around May 2027. Published summaries, such as this overview of the DPDP Rules 2025, describe reasonable security safeguards including encryption, access control, logging and backups, a minimum one year retention of security logs and penalties of up to 250 crore rupees for failing to maintain safeguards. The CloudMinister DPDP compliance checklist for servers and cloud gives a practical list. 

Several practices apply during a Google Workspace email migration. Keep a record of who accessed the migrated data, store the old backups securely, decide how long old mail must be retained and use Google Vault where the plan allows it. Audit logs in the Admin console are kept for a limited period, so organisations that need a full year of security logs should check retention and export options. Businesses that want an independent review can use cyber security services, and they should confirm legal duties with qualified counsel because this article is not legal advice. 

Doing It Yourself or Using a Partner for Google Workspace Email Migration 

Small projects with mail only and a technical administrator can run a Google Workspace email migration in house with the data import tool. The free tool and the clear documentation make it realistic when there are fewer than about twenty mailboxes, the source server meets the requirements and nobody needs calendars or complex mail routing. 

A partner is worth considering when the project is larger, when the source is Exchange or Microsoft 365, when downtime is expensive or when staff lack time. A partner brings tested checklists, handles DNS and authentication, schedules the cutover and supports users afterward. CloudMinister works as a Google Workspace partner and describes its services on the Google Workspace page, and the article on the Google Workspace tools explains what users will receive after the move. Whichever route is chosen, ask for a written plan that lists the tool, the batches, the cutover time, the rollback option and the responsibilities of each party. 

Sample Timeline for a Google Workspace Email Migration 

A typical small company with twenty mailboxes can follow this Google Workspace email migration schedule. Larger projects stretch each phase. 

  • Week 1: inventory, plan choice, backups and verification of the domain. 
  • Week 2: creation of users and groups, pilot migration with two users and review of results. 
  • Week 3: batch migration of the remaining mailboxes, import of contacts and calendars and lowering of the DNS TTL. 
  • Cutover day: switch the MX record, activate Gmail, publish SPF, DKIM and DMARC and test mail flow. 
  • Following week: monitor delivery, check old server for late mail, configure devices and train users. 
  • Week 6: retire the old system after the agreed retention period and document the final setup. 

The timeline is illustrative, and the real schedule depends on mailbox size, source speed and the availability of the people involved. A short pilot early in the project almost always saves more time than it costs. 

Conclusion

A Google Workspace email migration is not a difficult project, but it is an exacting one. Success depends on doing the right steps in the right order: verify the domain, create and license users, prepare the source server, copy the mail, move contacts and calendars, switch the MX record, publish authentication records and verify the result. Each step has a clear tool and a clear check, and skipping a step is what causes lost mail, empty address books and messages sent to spam. 

The most valuable lessons are the ones that older guides miss. An IMAP import copies mail and labels only, so contacts, calendars and rules need their own plan. The tool is now called Data import and is intended for up to 100 users, with GWMME and other tools for larger or private sources. Google now recommends a single MX record, and Gmail expects SPF, DKIM and DMARC. Keeping the old server and backups for a while gives a safety net that costs very little. 

For Indian businesses, the project also supports compliance. Encryption, access control, audit logs and retention are part of Workspace, and the Digital Personal Data Protection Rules make these duties concrete from around May 2027. A well documented migration, with records of who did what and when, is good evidence that the organisation takes data protection seriously, and the handling of source passwords and old archives deserves the same care as the new system. 

Teams that plan well finish a Google Workspace email migration with little disruption, and their users spend the following weeks enjoying a faster inbox, shared calendars, Drive and Meet instead of fixing missing mail. A short pilot, a calm cutover window and a checklist for the first week are the habits that separate smooth projects from stressful ones. Businesses that want local support can speak with a hosting company in India that works as a Google Workspace partner. 

Frequently Asked Questions

1. What is Google Workspace email migration? 

Google Workspace email migration is the process of copying mail from an existing system, such as an IMAP server, Exchange or Microsoft 365, into Gmail accounts in Google Workspace, then switching the domain mail routing and publishing authentication records. 

2. Does the IMAP data import move contacts and calendars? 

No. An IMAP based Google Workspace email migration copies email and label data only. Contacts are imported from CSV or vCard files, calendars from ICS files, and PST files can use Google Workspace Migration for Microsoft Outlook. 

3. Which tool should I use for Google Workspace email migration? 

For IMAP servers with a trusted certificate and up to 100 users, use the data import tool in the Admin console. For private networks, untrusted certificates or larger IMAP projects, use GWMME. Check the Google migration product matrix for other sources. 

4. How long does a Google Workspace email migration take? 

Small projects with a few mailboxes can finish in a few days including preparation, while large mailboxes can take hours or days to copy. DNS changes can take up to 48 hours to spread, so plan the MX switch with margin. 

5. Will I lose email during Google Workspace email migration? 

Not if the process is planned. Keep the old server active for at least a week after the MX switch, check it for late messages and keep backups. Mail sent during DNS propagation may still reach the old server. 

6. What MX record does Google Workspace use? 

Google recommends one MX record at the root of the domain with priority 1 and the value smtp.google.com. Older domains may still use five aspmx records, which continue to work, but old and new sets should not be mixed. 

7. Why do migrated emails go to spam after Google Workspace email migration? 

The usual reason is missing or duplicated SPF, no DKIM signing or no DMARC policy. Publish a single SPF record that includes Google, enable DKIM in the Admin console and add a DMARC record, then review reports. 

8. Can I do a Google Workspace email migration myself or should I hire a partner? 

A small, mail only project with a technical administrator can be done in house with the free data import tool. A partner is better for larger projects, Exchange or Microsoft 365 sources, strict deadlines or when downtime would be costly. 

Ajay Singh Raghav

Ajay Singh Raghav is a Senior Linux System Administrator at CloudMinister Technologies, where he has spent over 4 years installing, configuring, maintaining, and troubleshooting Linux servers for hosting and cloud environments. He specializes in AWS cloud computing alongside core Linux server administration, with hands-on expertise across server management, backup and restore systems, and cPanel-based hosting environments. His day-to-day experience keeping production servers stable and secure gives him a practical, ground-level understanding of the infrastructure he writes about.

Leave a Reply

Your email address will not be published. Required fields are marked *

Call Now Button