Zero-Downtime Email Migration from Google Workspace, cPanel or M365

Migrating company email from legacy providers (such as Google Workspace, Microsoft 365, cPanel, or Zoho) often raises fears of lost customer emails, broken inboxes, and business disruption.

Nyota Mail features an automated, server-to-server imapsync migration engine that transfers your historical emails, subfolders, and archives in the background while your team continues sending and receiving messages with zero email downtime.

1. How Zero-Downtime Migration Works Under the Hood

To prevent lost emails, migrations follow a structured three-phase lifecycle:

PHASE 1: INITIAL BULK SYNC (Old Host Still Live)
 Legacy MX records remain active -> imapsync engine background-copies
 historical inbox, sent, and custom archive folders to Nyota Mail.
                         │
                         ▼
 PHASE 2: DNS MX CUTOVER
 Update domain MX records to server.mxroute.com (Priority 10).
 New incoming messages route directly to Nyota Mail instantly.
                         │
                         ▼
 PHASE 3: DELTA CATCH-UP SYNC
 imapsync executes a final pass, copying only residual emails received
 on the old host during the DNS propagation window.

2. Source Provider Requirements (Before You Begin)

Depending on where your legacy email is currently hosted, complete these preparation steps:

A. Migrating from Google Workspace (Gmail)

1. Go to your Google Account Security Settings.
2. Ensure 2-Step Verification is turned on.
3. Search for App Passwords (myaccount.google.com/apppasswords).
4. Generate a 16-character App Password named Nyota Migration.
5. Use this 16-character string (without spaces) as your source password during migration.

B. Migrating from Microsoft 365 / Exchange Online

1. In the Microsoft 365 Admin Center, ensure IMAP Access is enabled for the migrating user under Mail 
   →→
    Email Apps.
2. If modern basic auth is disabled, generate an App Password in your Microsoft Account security settings.

C. Migrating from cPanel / Webmail / Other IMAP

1. Find your legacy incoming IMAP server hostname (e.g., mail.yourdomain.com or cpanelXX.yourhost.com).
2. Have your current mailbox email and password ready.

3. Step-by-Step Migration Process

Step 1: Provision Mailboxes in Nyota Mail

Before initiating a sync, create the destination mailboxes on your domain:

1. Log in to mailadmin.nyotaimara.com/mailboxes.
2. Click "Add Mailbox" and create the user account (e.g., jane@yourcompany.com).
3. Set an initial mailbox password.

Step 2: Trigger the Initial Background Sync

1. In the Nyota Mail Console, navigate to Email Migration.
2. Click "New Migration Task".
3. Configure the Source Server:
4. • Source Host: imap.gmail.com (for Google), outlook.office365.com (for M365), or your cPanel host.
   • Source Port: 993 (SSL/TLS).
   • Source User: jane@yourcompany.com.
   • Source Password: Your legacy password or Google App Password.
4. Select the target Destination Mailbox in Nyota Mail.
5. Click "Start Migration Sync".

The migration engine will stream historical folders in the background. You can monitor live progress and message counts in your dashboard.

Step 3: Switch Domain MX Records (DNS Cutover)

Once the initial bulk sync reaches 100%:

1. Open your domain DNS provider (e.g., Cloudflare, Namecheap, GoDaddy).
2. Update your MX records as outlined in our Custom Domain DNS Setup Guide:
3. • server.mxroute.com (Priority 10)
   • server-backup.mxroute.com (Priority 20)
3. Save changes. New incoming emails will now land in your Nyota Mail inbox.

Step 4: Run the Final Delta Catch-Up Sync

A few hours after updating your MX records, some senders with cached DNS records might have delivered emails to your old provider.

1. Return to Email Migration in mailadmin.nyotaimara.com.
2. Click "Run Delta Sync" next to the completed task.
3. The engine will compare folder hashes and copy only newly arrived messages.
4. Once completed, your migration is 100% finished, and you can safely decommission the old email provider.

4. Common Pitfalls & How to Troubleshoot

Pitfall A: "Authentication Failed with Google Workspace ([AUTHENTICATIONFAILED] Invalid credentials)"

• The Cause: Entering your standard Google login password when 2-Step Verification is active.
• The Resolution: You must generate and enter a Google App Password from myaccount.google.com/apppasswords.

Pitfall B: "Some subfolders did not copy over."

• The Cause: Certain legacy cPanel hosts use non-standard folder prefixes (e.g., INBOX.Sent instead of Sent).
• The Resolution:
• • Log in to Webmail at mail.nyotaimara.com 
    →→
     Settings 
    →→
     Folders.
  • Ensure all imported subfolders are checked to display in your active client tree.

Related Support Guides & Links

• Custom Domain DNS Setup Guide (MX, SPF, DKIM, DMARC)
• Configuring Outlook, Apple Mail & Thunderbird (IMAP/SMTP)
• Direct Migration Console