GSMME FAQ

No. There's a single location for configuration files. If you run multiple instances of G Suite Migration for Microsoft^® Exchange (GSMME) on a single client, those instances overwrite each other's configuration files. If you want to increase the number of users migrated by a client machine, increase the number of users processed. See the GSMME Administration Guide.

You can, but it isn't recommended. If the client machine can run multiple virtual machines, we recommend you take advantage of the machine. Run one instance of the client and increase the number of users that are processed simultaneously.

No. Each instance has to reference a unique list of users. If you reference the same list of users, the users' data becomes corrupt.

GSMME uses MAPI. For details, see How a GSMME migration works.

No. You only need to open HTTPS and ensure Google IP addresses aren't blocked.

GSMME follows the proxy configuration defined in Microsoft Internet Explorer^® and uses those settings for all network connections to Google. Authenticated proxies aren't supported by GSMME.

Although GSMME supports proxy connections, you might need to enable a direct connection to make sure issues aren't caused by the proxy server. Since the proxy configuration depends on your local setup, Google Cloud Support won't be able to assist you with this configuration. Contact your network administrator if you encounter proxy issues.

Yes. Create all user accounts in G Suite before running a migration.

For details, see Migrate data from Exchange or Migrate mail from Google Accounts or IMAP.

No. You don't need to change your MX records.

No. Only include usernames. For details, see Create a control CSV file.

Yes. For details, see Create a control CSV file.

If the file meets the format requirements, you can use an automated CSV file. For details, see Create a control CSV file.

Yes. For details, see Authorize GSMME for your account.

Yes. In the Review GSMME Settings dialog, if you check Estimate (without checking Migrate all data or Migrate) GSMME scans the data of the source users on the source environment. It then estimates the amount of items to migrate.

Other than having their email, calendar, or contact data available in G Suite rather than your legacy server, your users aren't impacted by a migration.

Yes. Use the command line version of GSMME and run it as a Windows^® scheduled task. For details, see Run GSMME from the command line.

Yes.

Yes. You can run personal storage table (PST) file migrations using the GSMME desktop interface or the command line. For details, see Migrate data from PST files.

Yes. For details, see Migrate mail from Google Accounts or IMAP.

Yes. For details, see Migrate public folders.

Yes. GSMME is designed to migrate data for multiple users from an Exchange or IMAP-compatible server to G Suite. It's implemented from the server side. G Suite Migration for Microsoft Outlook (GSMMO) migrates data for only a single user. It's implemented from the client side.

Note: If you migrate data from both the server side and the client side, users could end up with duplicate data.

No. GSMME is designed to allow only one migration at a time to a specific user.

We don't recommend having multiple concurrent API requests migrating data into single account.

Yes. For details, see the "Test" section in the Deploy chapter of the GSMME Administration Guide.

Yes. You can use G Suite Sync for Microsoft Outlook (GSSMO) for this purpose.

Yes. For details, see the GSSMO in the G Suite Learning Center.

Yes. After you migrate your data and set up your mail flow to G Suite, you can stop using your Exchange Server.

No. GSMME is designed to migrate data from Exchange to G Suite. It isn't designed for synchronization.

Yes. When they open the GSSMO tool, they’ll create a new profile that points their Outlook account to Gmail. No other configuration is necessary.

Yes. For details, see Check Gmail through other email platforms.

Yes, but it isn't a supported client. For details, see Check Gmail through other email platforms.

No. You can use a third-party gateway for email delivery.

No.

If you're using Microsoft Active Directory^® you can use G Suite Password Sync (GSPS) to sync user passwords from Active Directory to your Google domain.

No, but administrators can. For details, see the "Viewing migration reports" section in the Troubleshooting chapter of the GSMME Administration Guide.

Yes. The archived messages must be moved to Exchange first and then migrated.

Yes. In Gmail, the corresponding labels are separated by a slash character to indicate the folder hierarchy. For example, Receipts/2019 Q1.

If you choose the Migrate all data option, the message is migrated again. It's displayed in Gmail with a new label that corresponds to the new Exchange folder.

No. Any flags on an Exchange message are mapped as a single star in Gmail.

No, but your users can create new rules in Gmail. See Create rules to filter your emails.

Yes. The limit for a message, including any attachments, is 25 MB.

No.

Perhaps.

If you want to let individual users take control of their migrations, G Suite Migration for Microsoft Outlook (GSMMO) lets users migrate email, calendar, or contact data from an Exchange account or local PST file into a G Suite account.

If your organization has switched to G Suite but you'd like to keep using Outlook, G Suite Sync for Microsoft Outlook (GSSMO) lets users synchronize mail, calendar events, contacts, notes, and tasks between Outlook and a G Suite account.

For additional migration options, see the G Suite migration tools product matrix.

Yes. Outlook can automatically send read receipts for the synchronized messages, which results in unnecessary non-delivery reports. Disabling read receipts in Outlook prevents them from being sent automatically.

Yes. Users can continue to work in Outlook when an internet connection is unavailable. Data is synced between Outlook and G Suite when the internet connection is restored.

Yes. You can use Google Vault, which includes email archiving.

Yes.

Yes.

No.

No. You need to recreate those in G Suite.

No. However, you can use Google Cloud Directory Sync (GCDS). See also Manage your Global Address List, if you are using GSSMO.

The addresses should appear in Gmail when a contact name or email is entered in the To, Cc, or Bcc fields.

No. You can use GCDS to migrate mailing list memberships (not archives) to Google Groups.

Yes. For details, see the GSMME Administration Guide or the G Suite migration tools product matrix.

No, but you can set up delivery so messages are sent to G Suite and Exchange.

Yes. You can implement similar functionality by using Google Groups to create a collaborative inbox, or by using shared files and folders in Google Drive. You can also create calendars to share with a group.

Maybe. You can route incoming messages to Gmail or another external server based on user settings. Then, you can use Calendar Interop to share free and busy information between Exchange and G Suite. Consult with your deployment specialist to find out if this is the best approach for your organization.

Yes.

Archiving data

GSMME allows you to add users’ migrated email messages to Google Vault, instead of storing them in their Gmail mailbox, using the Migrate to Google Vault feature. You can migrate email to Vault from PST files or any supported mail server, including Exchange, IMAP, and Gmail. Note that migrated messages are not visible in users’ Gmail inboxes.

For details, see the "Add migrated email to Google Vault" section in the Migrate data chapter of the GSMME Administration Guide.

Setting a date range

If you want to migrate only a portion of email messages, you can specify a date range. For example, you can migrate all mail messages except for the past two weeks into Google Vault using the Migrate to Google Vault feature along with a date range.

For details, see the "Select the data to migrate" section in the Migrate data chapter of the GSMME Administration Guide.

No. We have successfully tested conversions with up to 226 characters.

No. Empty folders aren't migrated. And, the corresponding labels aren't created.

Yes. The corresponding labels in Gmail indicate the folder hierarchy by inserting slash characters in the label names. For example, Receipts/2019 Q1.

If you choose the Migrate all data option, the message is migrated again. It's displayed in Gmail with a new label that corresponds to the new Exchange folder.