Home / Documentation

POP3 to Gmail Migration Documentation

Complete guide to migrating and continuously syncing POP3 email to Gmail

Table of Contents

Overview

POP3 to Gmail Sync is a cloud-based service that continuously migrates and synchronizes emails from legacy POP3 mail servers to Gmail accounts. Unlike one-time migration tools, our service runs in the background, handling large mailboxes incrementally and recovering gracefully from interruptions.

The tool is designed for IT consultants, system administrators, and businesses moving from legacy email systems (cPanel, legacy hosting, on-premise servers) to Gmail or Google Workspace.

The Problem We Solve

Challenges with Traditional Email Migration

Migrating email from POP3 servers to Gmail presents several challenges:

  • Timeouts and failures: Large mailboxes often cause migration tools to timeout or fail partway through, requiring manual restarts.
  • Gmail's deprecated POP3 fetcher: Gmail has deprecated their built-in POP3 fetcher, and it lacks features like email notifications for failures.
  • Credential security: Storing POP3 passwords securely while allowing automated access is complex.
  • Oversized messages: Messages exceeding the 10MB limit cause failures that block entire migrations.
  • Monitoring gaps: Most tools provide no visibility into progress or remaining messages.
  • All-or-nothing approaches: Traditional tools require continuous connectivity and complete the entire migration in one session.

Our Solution

POP3 to Gmail Sync addresses these challenges with a continuous, resilient approach:

  • Incremental batching: Processes emails in small batches with pauses between sessions
  • Automatic resumption: Picks up exactly where it left off after any interruption
  • Client-side encryption: POP3 credentials are encrypted in the browser before transmission
  • Email notifications: Get notified when messages fail to import (unlike Gmail's deprecated fetcher)
  • Real-time monitoring: Track remaining messages and sync status live
  • OAuth security: Uses Google OAuth for secure, minimal-permission access to Gmail
  • Privacy-focused: No email metadata storage—messages deleted after sync

How It Works

Step-by-Step Migration Process

1. User Authentication (OAuth)

Users authenticate with Google using OAuth 2.0. The service requests only the minimum necessary permission: gmail.insert scope. This allows the service to add messages to your Gmail account without being able to read, modify, or delete existing emails.

2. POP3 Configuration

Users provide their POP3 server details:

  • POP3 server hostname (e.g., mail.example.com)
  • Port (typically 995 for SSL/TLS)
  • Username and password
  • SSL/TLS settings

Important: Your POP3 password is encrypted in your browser before being sent to our servers.

3. Continuous Sync Loop

Once configured, the service runs a scheduled background process:

  1. Connect: Establishes a connection to your POP3 server
  2. List: Retrieves a list of available messages (tracking already-synced UIDs)
  3. Fetch: Downloads a batch of messages (typically 10-50 at a time)
  4. Process: For each message:
    • Checks size against the 10MB limit
    • Uploads to Gmail using the API
    • Deletes from POP3 server on success (ensuring we don't store metadata about your emails)
    • Sends email notification for oversized or failed messages
  5. Disconnect: Closes the connection cleanly
  6. Wait: Pauses before the next sync cycle (typically 1-5 minutes)
  7. Repeat: Continues until no messages remain
Why batching? By processing emails in small batches with connection resets, we avoid timeout issues, reduce server load, and maintain a reliable sync even over unreliable networks.

4. Monitoring & Status

Throughout the sync, you can view real-time status:

  • Number of messages remaining on the POP3 server
  • Last sync time
  • Error messages (if any)
  • OAuth token status

Common Use Cases

1. Legacy Email Migration

Migrating from old email systems (cPanel, Plesk, legacy hosting providers) to Google Workspace or Gmail.

Scenario: A small business has 10 years of email on a shared hosting cPanel account and wants to move to Google Workspace.

2. Historical Email Archiving

Importing archived email from backup servers or old accounts into Gmail for searchability and accessibility.

Scenario: An organization has archived emails on an old server they want to decommission.

3. Multi-Account Consolidation

Consolidating multiple legacy email accounts into a single Gmail account.

Scenario: A consultant has 5 old email accounts from different clients and wants everything in one Gmail account.

4. Continuous Backup Sync

Continuously syncing an active POP3 account to Gmail as a backup or transition strategy.

Scenario: A company is gradually transitioning to Gmail but needs to keep their legacy system running temporarily.

5. Gmail Fetcher Alternative

Replacing Gmail's deprecated built-in POP3 fetcher with a more reliable solution that includes email notifications.

Scenario: Gmail has deprecated their fetcher, or you need visibility into import failures.

Getting Started

Prerequisites

  • A Gmail account or Google Workspace account
  • Access to your POP3 email server credentials
  • POP3 server hostname and port information
  • Modern web browser (Chrome, Firefox, Safari, Edge)

Quick Start Guide

Step 1: Sign In with Google

  1. Visit the application
  2. Click "Sign in with Google"
  3. Grant permission for Gmail insert access

Step 2: Add POP3 Configuration

  1. Click "Add POP3 Configuration"
  2. Enter your POP3 server details:
    • Server hostname (e.g., mail.example.com)
    • Port (usually 995 for SSL, 110 for non-SSL)
    • Username (often your full email address)
    • Password
  3. Enable SSL/TLS (recommended)
  4. Click "Save Configuration"
Tip: Your password is encrypted in the browser before being sent to our servers. The encryption happens automatically.

Step 3: Monitor Progress

  1. The sync starts automatically within minutes
  2. Refresh the page to see updated status
  3. Watch the "Remaining messages" counter decrease

Step 4: Manage Your Sync

  • Pause: Delete the configuration to stop syncing
  • Resume: Re-add the configuration to continue from where it left off
  • Multiple accounts: Add multiple POP3 configurations for different mailboxes

Technical Details

How the Sync Works

The service is a cloud-based application that:

  • Connects to your POP3 server on a schedule
  • Fetches messages in small batches
  • Uploads them to Gmail via the Gmail API
  • Deletes successfully synced messages from the POP3 server
  • Sends you email notifications for any failures

Key Features

  • OAuth security: Uses Google OAuth for Gmail access (insert-only permission)
  • Client-side encryption: Your POP3 password is encrypted in your browser before transmission
  • No metadata storage: Emails are deleted after sync, so we don't store information about your messages
  • Original dates preserved: Messages appear in Gmail with their original send dates
  • Size limit: 10MB per message
  • Email notifications: Get notified when messages fail to import

Security Model

OAuth Authentication

  • You authenticate directly with Google
  • The service never sees your Google password
  • Minimal permission scope (gmail.insert only - cannot read or modify existing mail)
  • Automatic token refresh

POP3 Credential Protection

  • Your POP3 password is encrypted in your browser before transmission
  • Credentials are stored encrypted
  • SSL/TLS support for encrypted connections to your POP3 server

Privacy Protection

  • No email metadata storage: Messages are deleted from the POP3 server after successful sync, so we don't store any information about your email content or history
  • Minimal data collection: We only store what's necessary for the sync to function
  • You control retention: Delete your configuration to remove all associated data
Important: When you delete a POP3 configuration, the service stops syncing. However, emails already synced to Gmail remain in your Gmail account. To remove them, you must delete them from Gmail separately.

Requirements & Limitations

System Requirements

  • Gmail account: Personal Gmail or Google Workspace account
  • POP3 server: Must support standard POP3 protocol
  • Browser: Modern browser with JavaScript enabled
  • Network: Internet connectivity for the service to reach both Gmail and your POP3 server

POP3 Server Requirements

  • Standard POP3 protocol support
  • UIDL support (for tracking synced messages)
  • Optional: SSL/TLS support (recommended)
  • Server must be publicly accessible or accessible via the service network

Limitations

Message Size

Messages larger than 10MB are:

  • Left on the POP3 server (not deleted)
  • You receive an email notification to handle them manually

Gmail API Quotas

Google imposes API quotas on Gmail operations. The service is designed to stay within these limits through:

  • Batch processing with pauses
  • Rate limiting
  • Exponential backoff on quota errors

Attachments

All attachments are preserved and synced exactly as they appear in the original message, up to the 10MB total message limit.

Message Metadata

  • Preserved: Subject, From, To, Cc, Bcc, Date, Message-ID, attachments
  • Not preserved: Read/unread status (all messages appear unread in Gmail initially)

Deletion

Messages are deleted from the POP3 server after successful sync to Gmail. This ensures we don't need to store any metadata about your emails, protecting your privacy. If you need to keep messages on the POP3 server, this service is not suitable.

Troubleshooting

Common Issues

Sync Not Starting

Symptoms: Configuration saved but no progress after 10+ minutes

Possible causes:

  • OAuth token expired - sign out and sign in again
  • POP3 server unreachable - verify hostname and port
  • Firewall blocking the service - check with your hosting provider
  • Service temporarily down - check status page or contact support

Authentication Errors

Symptoms: "Authentication failed" or "Invalid credentials"

Solutions:

  • Verify POP3 username and password are correct
  • Check if your email provider requires "app passwords" instead of regular passwords
  • Some providers (like Gmail) require enabling "less secure app access" for POP3
  • Verify the correct port (995 for SSL, 110 for non-SSL)

Oversized Messages

Symptoms: Sync stalls or error message about message size

Solutions:

  • Download oversized messages manually from the POP3 server
  • Delete them from the POP3 server to allow the sync to continue
  • Check Gmail for notification messages about oversized emails

Slow Sync Speed

Symptoms: Only a few messages synced per hour

Causes:

  • Large attachments take longer to upload to Gmail
  • POP3 server throttling connections
  • Gmail API rate limits (normal behavior)

Note: The service is designed for continuous, reliable sync rather than maximum speed. A slower sync ensures reliability and avoids overwhelming servers.

OAuth Token Expired

Symptoms: "Re-authentication required" message

Solution:

  1. Click "Sign out"
  2. Click "Sign in with Google"
  3. Grant permissions again
  4. Sync will resume automatically

Getting Help

If you encounter issues not covered here:

  • Check the FAQ section on the homepage
  • Review error messages in the application interface
  • Contact support with specific error messages and your configuration details (never share passwords)

Frequently Asked Questions

General Questions

How do I migrate POP3 email to Gmail?

Use our POP3 to Gmail Sync service. Sign in with Google, add your POP3 server credentials, and the service automatically syncs your emails in the background. The process is continuous and reliable, handling large mailboxes without timeouts.

Is my data secure during migration?

Yes. POP3 passwords are encrypted client-side in your browser before transmission using public-key cryptography. OAuth is used for Gmail access, so the service never sees your Google password. All connections use encryption (HTTPS, SSL/TLS).

Can I automatically sync POP3 to Gmail?

Yes. Once configured, the sync runs automatically in the background until all messages are transferred. You can add multiple POP3 accounts and they will all sync continuously.

Does it delete mail from the POP3 server?

Yes, after successful sync to Gmail. This prevents duplicates and gradually clears the source mailbox. Oversized or failed messages are left untouched for manual handling.

Can I stop a sync?

Yes. Delete the configuration from the interface and the service stops at the next sync cycle. Emails already synced remain in Gmail.

Technical Questions

Will Gmail show original dates?

Yes. The service preserves the original Date header from each message, so emails appear in Gmail with their original send dates.

What happens to attachments?

All attachments are preserved exactly as they appear in the original email. There's no modification or compression applied.

Is this only for one mailbox?

No. You can add multiple POP3 configurations per Gmail account and track them separately. Each configuration syncs independently.

How long does migration take?

It depends on the number and size of messages. The service processes emails in batches with pauses to ensure reliability. A mailbox with thousands of messages might take several hours to days, but the sync runs automatically in the background.

Do I need to keep my POP3 server running?

Yes, until the migration is complete. The service needs continuous access to the POP3 server to fetch messages. Once all messages are synced, you can safely shut down the server.

Can I use this with Gmail's native POP3 fetcher?

Yes. Gmail has deprecated their built-in fetcher, but if you do use both, they work together fine. This service deletes emails after syncing, so Gmail's fetcher won't see them again.

Does it work with IMAP servers?

No, this service is specifically designed for POP3 protocol. IMAP requires different handling and is not currently supported.

What if a message fails to import?

You'll receive an email notification when a message fails to import (e.g., oversized messages). This ensures you know to check and handle it manually—unlike Gmail's deprecated fetcher which fails silently.

Why does it delete emails from the POP3 server?

Deletion after successful sync ensures we don't need to store any metadata about your emails, protecting your privacy. It also prevents duplicates if you later use Gmail's native fetcher.

Troubleshooting Questions

Why isn't my sync starting?

Common causes: OAuth token expired (re-authenticate), incorrect POP3 credentials, server unreachable, or firewall blocking connections. See the Troubleshooting section for details.

What if I have messages larger than 10MB?

Oversized messages are left on the POP3 server and you'll receive an email notification. You can then handle them manually by downloading directly or removing large attachments.

Can I preview messages before they're synced?

No, the service is designed for automated, unattended syncing. Messages are synced directly from POP3 to Gmail without manual review.