Google Workspace to Zoho Mail Migration Guide

• Create and verify the destination domain, users and groups in Zoho Mail before migrating mailbox data.
• Authorize access carefully using the Google Workspace administrator and service-account details required by Zoho.
• Run a pilot migration first so labels, folders, contacts and calendars can be checked before the full move.
• Plan mail routing and MX cutover separately from copying historical data.

01Dependencies before you plan the migration

Treat these as migration dependencies, not tasks to discover during cutover. Confirm ownership, access and destination readiness before configuring a production batch.

• 01
  Zoho organisation and edition: confirm the destination organisation, applicable licences, mailbox storage and administrator access.
• 02
  Verified destination domain: add and verify every email domain that will receive migrated users.
• 03
  Destination identities: create the required Zoho Mail users and groups before migrating their data. Zoho One organisations may need to manage users from the Zoho One Admin Panel.
• 04
  Matching calendar domain: for calendar migration, the Zoho Mail domain must match the Google Workspace domain, and the relevant Workspace users must already exist in Zoho Mail.
• 05
  Google administrator access: identify the Google Workspace super administrator who can approve the required access.
• 06
  Service-account authorization: prepare the service-account email address, domain-wide delegation and the supported JSON or P12 key file using Zoho’s current authorization guide.
• 07
  Data scope: decide whether the project includes mail, contacts and calendars. Google Drive to Zoho WorkDrive is a separate migration workstream.
• 08
  User mapping: prepare source and destination addresses, aliases, groups, shared addresses and exceptions.
• 09
  Storage assessment: compare source mailbox sizes with destination capacity and allow for possible duplication caused by Gmail labels.
• 10
  Cutover plan: define pilot users, migration batches, mail routing, MX changes, user communication, validation and rollback responsibilities.

Understand Gmail labels before copying mail

Gmail labels and conventional mail folders do not behave in exactly the same way. A message with multiple labels may appear in multiple destination folders, depending on the selected migration settings. This can increase apparent message counts and storage use.

Review heavily used labels such as Important, Starred and nested team labels during the pilot. Use Zoho’s include, exclude and tag options only after checking the result for representative users.

02Adding the Google Workspace migration

• 01
  Sign in to the Zoho Mail Admin Console and open Data Migration.
• 02
  Choose Start Migration for the first setup or Create for another migration.
• 03
  Enter a clear server-configuration name.
• 04
  Choose Google Workspace as the source application.
• 05
  Enter the Google Workspace super-admin email address and service-account email address.
• 06
  Upload the supported service-account key file and authenticate the connection.

Google’s authorization requirements can change. Complete this step against Zoho’s current authorization guide rather than relying on screenshots or saved instructions from an earlier migration.

03Configuring Google Workspace migration

• 01
  Name the settings so the selected scope can be recognised later.
• 02
  Select the data to migrate: Mail, Contacts and/or Calendar.
• 03
  Choose whether to migrate all folders or only specified folders.
• 04
  Review folder include and exclude rules, including nested-folder syntax, against Zoho’s current documentation.
• 05
  Choose whether all email should move or only messages after a specified date.
• 06
  Review the available Gmail-label handling settings before saving the configuration.
• 07
  Confirm any POP-access option only if it is required for the post-migration client setup.

Use a small pilot group to validate folder placement, timestamps, message counts, contacts and calendars. Do not assume the same settings will suit every organisation.

04Creating the migration batch

• 01
  Enter a migration name that identifies the source, scope and batch.
• 02
  Set a reasonable maximum connection limit for concurrent users.
• 03
  Select the available storage-threshold behaviour for the migration.
• 04
  Create the migration and proceed to user mapping.

A higher connection limit is not automatically better. Batch size and concurrency should reflect source limits, destination capacity, mailbox size and the results of the pilot.

05Adding and mapping users

Zoho currently documents three ways to add migration users: manual addition, CSV import and fetching users from the source server.

Manual addition

• 01
  Select the migration and choose Add.
• 02
  Enter the Google Workspace source address and corresponding Zoho destination address.
• 03
  Choose the priority where required and confirm the mapping.

CSV import

• 01
  Select the migration and choose Import.
• 02
  Download and follow the current sample-file format shown by Zoho.
• 03
  Include both the source account and its destination account.
• 04
  Upload the CSV and review the preview, mappings and import status before proceeding.

Fetch from the source

• 01
  Select the migration, choose to add users and use Fetch where available.
• 02
  Select the required source users and confirm the corresponding destination accounts.
• 03
  Review the preview and resolve missing or incorrect mappings before starting.

06Critical points during the migration process

• 01
  Pilot before production: migrate a small but representative group, including large mailboxes and users with complex labels or calendars.
• 02
  Watch Gmail label duplication: a message carrying several labels can be written into several Zoho Mail folders. Validate storage and folder results before expanding the batch.
• 03
  Check folder syntax exactly: include and exclude rules use quoted folder names, and nested-folder patterns require the convention currently documented by Zoho.
• 04
  Map both sides of every account: CSV imports require a valid source address and corresponding destination address.
• 05
  Control concurrency: set the connection limit from pilot results and source behaviour; increasing parallel connections without testing can create avoidable failures.
• 06
  Monitor destination storage: choose and observe the available storage threshold so a batch does not silently consume the remaining mailbox capacity.
• 07
  Preserve required credentials: if the selected migration method authenticates with individual source credentials, do not change them until that migration completes. The service-account workflow uses administrator-authorized access.
• 08
  Review every data type separately: mail, contacts and calendars have separate progress and failure details.
• 09
  Retry deliberately: use retry for failed users after resolving the cause. Zoho’s newer sync option may be released in phases and should be confirmed for the organisation.
• 10
  Separate data copy from mail cutover: historical migration does not by itself redirect new incoming mail. Coordinate routing and MX changes in the approved cutover window.

07Starting and monitoring the migration

• 01
  Start with a representative pilot batch rather than every mailbox.
• 02
  Monitor overall progress and open individual user details for message-level statistics.
• 03
  Review mail failures and the separate contact and calendar results where those data types are included.
• 04
  Resolve errors, rerun only the required scope and verify the result with pilot users.
• 05
  After validation, schedule production batches and the mail-routing or MX-record cutover for a controlled window.

08Prepare DNS and email authentication for cutover

Historical data migration and live mail delivery are separate. Plan DNS changes with the person who controls the authoritative DNS zone.

• 01
  Reduce relevant DNS TTL values in advance where the provider allows it, so planned MX changes can propagate sooner.
• 02
  Use the Zoho Mail Admin Console values for the organisation’s data centre rather than copying generic MX records from another account.
• 03
  Publish and verify the required SPF record for authorised senders. Avoid creating multiple competing SPF records for one domain.
• 04
  Generate, publish and verify the DKIM record from the Zoho Mail configuration.
• 05
  Plan DMARC after SPF and DKIM alignment has been checked. Begin with a monitoring policy appropriate to the organisation before moving to enforcement.
• 06
  Test inbound and outbound delivery after propagation and keep the old routing available only as long as the approved transition requires.

09Post-migration validation

• 01
  Confirm inbound and outbound mail flow.
• 02
  Check aliases, groups, forwarding, signatures and mobile or desktop clients.
• 03
  Compare recent and historical mail, key folders, contacts and calendars for selected users.
• 04
  Communicate login details, cutover timing and support instructions to users.
• 05
  Keep the source environment available for an agreed validation period before decommissioning it.

Product and configuration note

Admin Console labels, authorization requirements and migration options can change. Available capabilities may also depend on the Zoho edition, organisation type and region. Confirm the final procedure against Zoho Mail’s current official documentation before a production migration.