Migrate from Google Workspace (Bulk)

Use Bulk Import to copy several Google Workspace mailboxes to TrekMail. Each CSV row uses the source mailbox's own IMAP credentials. This is an email migration only: contacts, calendars, rules, and account settings are not copied.

Check access before collecting passwords

The TrekMail importer signs in to Gmail over IMAP with an App Password. Each source mailbox needs its own app password; one administrator password cannot be used for every user.

Before you build the CSV, ask the Google Workspace administrator to confirm that the intended mailboxes can use IMAP and App Passwords. Google can restrict this for an organization or a particular account. For personal Gmail, IMAP is normally enabled by default, but Workspace administrators may control it.

Ask every mailbox owner to:

1. Sign in to their Google Account and open Security.
2. Turn on 2-Step Verification if the account is allowed to use it and it is not already enabled.
3. Create an App Password for this migration.
4. Send the app password to the migration owner through an approved secure channel, not chat or email.

An App Password can be unavailable because of organization policy, Advanced Protection, or the account's two-step verification setup. In that case, do not substitute the user's normal Google password. Resolve the policy with the Workspace administrator first.

Create the CSV

All Gmail rows use the same source server, so use the simple three-column format:

source_email,source_password,destination_email
alice@old-company.example,alice-app-password,alice@new-company.example
bob@old-company.example,bob-app-password,bob@new-company.example

• source_email is the Google Workspace mailbox being copied.
• source_password is that mailbox's app password.
• destination_email is an existing TrekMail mailbox in your account.

The CSV contains credentials. Keep it in a restricted location, never upload it to a ticket or repository, and delete it after the migration is verified. See Bulk Migration CSV Format for quoting, limits, and templates.

Run the batch

1. Open Import > Bulk Import.
2. Select Gmail. TrekMail fills in the Gmail server settings.
3. Paste or upload the CSV.
4. Select Preview & validate. Resolve every invalid row before you start.
5. Choose a folder strategy. Preserve folder tree is the right choice when you need users' labels and custom folders. Only INBOX + Sent is useful for a deliberately limited migration.
6. Keep Skip duplicates on for an initial import and any later catch-up pass.
7. Start the batch and use its detail page to monitor individual mailboxes.

Google may limit IMAP activity while a large group is being imported. The batch can queue or take longer without indicating that the CSV is wrong. Use the status and error shown for an individual mailbox before changing credentials or creating another batch.

If a row fails

• Authentication failed: Confirm the full Google email address and create a new App Password. Do not use the normal Google password.
• App Password unavailable: Ask the Workspace administrator to check the account and organization policy. A standard user cannot override that restriction in TrekMail.
• Connection problem: Re-select Gmail in the import form so the standard settings are restored, then preview again.
• Partly completed or failed after starting: Open the batch row, resolve the reported issue, then use the available Continue action. It preserves completed work where possible.

Finish the cutover

Check representative user mailboxes and their important labels before changing MX records or cancelling Google Workspace licenses. For a phased cutover, you can run a later import with Skip duplicates selected to catch up source mail that arrived after the first pass.