IMAP to G Suite Migration Guide
- This is the complete onboarding task flow for migrating mailboxes from IMAP systems to G Suite.
- Complete each step in order. Links to corresponding Knowledge Base articles are provided.
- Due to API limitations, IMAP migrations will only migrate mail items.
- The MSPComplete section includes steps to deploy the Device Management Agent (DMA) to end users. This is an Agent which includes multiple modules, e.g., for HealthCheck for Office 365 and DeploymentPro. It is not required to install DMA for this migration scenario. However, BitTitan will be adding several modules to DMA, and these will be important to power MSPComplete feeds (which will provide further information to you about upsell and cross-sell opportunities).
- Note: We can only migrate mail items that are stored on the IMAP server. Verify that a copy of the mail remains on the server. If there is no mail on the IMAP server and it is stored in a local PST, use the PST migration process. If the data is stored in a local Outlook OST file (Outlook 2013 and Outlook 2016), export the mailbox to a PST and use the PST migration process.
- There are many different versions of IMAP mail systems available. For this reason, we recommend running a trial migration on one or more mailbox(es) prior to the actual full migration project.
- Once the trial migration completes, check on the folder structure at the Destination to ensure that the directory structure is as desired. KB004671
- This guide includes a folder mapping under the MigrationWiz Steps section, which will ensure that folders are mapped to the root label on the Destination mailboxes, rather than under inbox/labelname.
Prepare the Source Environment
- Test connectivity to the IMAP server, by going here. Fill in the form, and click on the Test button.
- Export the user list to a CSV file.
- Administrator accounts with at least read rights can export a user list.
- If you do not have an administrator account, you need to ask your IMAP host to provide you with a complete user list, in CSV file format.
- This CSV file will be used to bulk add users into your MigrationWiz mailbox project.
Prepare the Destination Environment
- Create users on G Suite. Refer to G Suite admin help article here.
- Grant MigrationWiz OAuth 2.0 access to G Suite. For guidance, see Enable access to G Suite using OAuth 2.0.
- If you are migrating to multiple domains, repeat these steps for each domain.
- G Suite as the Destination (full scopes):
https://mail.google.com/, https://www.google.com/m8/feeds, https://www.googleapis.com/auth/contacts, https://www.googleapis.com/auth/calendar, https://www.googleapis.com/auth/admin.directory.group, https://www.googleapis.com/auth/admin.directory.user, https://www.googleapis.com/auth/drive, https://sites.google.com/feeds/
- For the Source endpoint:
- Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select IMAP.
- Server Name should follow format: imap.example.com
- Enter server port. As a general rule, the server port will be either 143 or 993 (if using SSL). Note: If you are using SSL, checkmark the Use SSL box.
- For the Destination endpoint:
- Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select G Suite/Gmail.
- It is necessary to add ALL domains that will be migrated to. This means that if there are users in one project with domain names Sourcedomain.com and Destinationdomain.com, it is important to ensure that both of these are added under Your Domains when creating the endpoints. When you add a domain, you need to click on the "+" button.
- Enter Administrative email address. Note: This is the account that has admin access level to the Google admin portal.
- Via Group Policy Object (GPO). Note: This is the recommended methodology, because no end user interaction is required. KB005412 video
- Via email. KB005411
Watch this video to see a walk-through of the steps below.
- Create the Mailbox Migration project. KB004380
- Create the Mailbox Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
- Use Bulk Add, with a CSV file that contains your user list.
- If you have an admin account on the Source IMAP system, the format will be as follows. Note: Most IMAP systems do not support administrative credentials. Refer to KB004344 for a list of supported IMAP systems.
- Source Email: SMTP email address.
- Source Login Name: Consists of two combined names: the user name of the person whose email is being migrated, and the user name of the mailbox admin account. For example, for Exchange IMAP: Domain/Admin_UserName/User_UserName. Important: To determine the correct format to follow for this value, refer to KB005830.
- Source Password: Enter the administrator's password.
- If you do not have an admin account, enter the Source Email addresses in the Source Email column, and checkmark the I don't know the login name and password for the Source mailboxes box. Note: Users will then be asked to provide their credentials during the migration process. Video
- For the Destination, you only need to enter the Destination email address of each user.
- The following options are the most valuable for this migration scenario:
- Add folder mapping: FolderMapping="^INBOX/->" under Support/Support options. Note: This will map folders to the root label on the Destination mailboxes, rather than under inbox/labelname. KB005068
- Note: If errors are listed in the MigrationWiz dashboard with the following error message: "Unexpected extra arguments to Examine Context: FolderNameWithQuote", then follow the steps below to add the support option flag AllowQuoteInFolder=1 at the item level, and run retry errors. KB005859
- Steps: Click the Edit Item icon to the right of the item that you wish to edit > Under the Support section, enter the support option: AllowQuoteInFolder=1 > Click Save Item > Select the line item in your MigrationWiz dashboard > Click Start > Retry Errors