What data GSMME migrates
G Suite Migration for Microsoft® Exchange (GSMME) is a utility that migrates mail, calendar, and contact data from Microsoft Exchange, an IMAP server, or a PST file to your G Suite domain. During the migration, contacts are processed first, followed by calendar data then email.
Consider the following data and whether or not it's migrated, when you're setting up a migration to G Suite with GSMME.
Email| Source data | Migrated to G Suite | Notes |
|---|---|---|
| Email messages | ✔ | All email in top-level folders is migrated. A top-level folder is any folder that resides at the same level as your Inbox folder.
You have the option to exclude specific top-level folders from migration. |
| Email state such as read and unread | ✔ | |
| Deleted items | ✔ | Migration is optional. Deleted items are labeled Trash in Gmail. |
| Folders | ✔ | Folders map to labels in Gmail. You can elect to omit top-level folders from migration. If you omit a folder, its subfolders are also omitted.
There is a 255 character limit per label. If you migrate a folder with a title that’s over 255 characters, the mail will still migrate, but it will be put with the prior label. |
| Subfolders |  |
Subfolders in your Exchange inbox don't migrate as nested labels in Gmail. Instead, the subfolders appear as Inbox/folder-name in an unnested state. |
| Junk email | ✔ |
Migration is optional. Junk email is labeled "Junk email" in Gmail. |
| Public folders | ✔ | For details, see Migrate public folders with GSMME. |
| Large messages and attachments | ✘ | Messages that are bigger than 25 MB (message plus attachments) aren’t allowed in Gmail.
Messages that are bigger than 16 MB (message plus attachments) are not migrated into Google Groups. |
| Attachments | ✔ | Most attachments are migrated, except when the message and attachment are larger than 25 MB, or when there is an executable file in the attachment. |
| Executable files in compressed attachments | ✘ | These types of attachments aren’t allowed in Gmail. |
| Posts in mailbox folders | ✘ | Not available in Gmail. |
| Importance levels of messages | ✘ | Not imported into Gmail. |
| Message flags | ✔ | Flags appear as stars in Gmail. |
| Rules | ✘ | Rules (both server and client) aren’t migrated. But you can create equivalent filters in Gmail. |
| Signatures | ✘ | Not migrated but can be re-created in Gmail. |
| POP messages | ✔ | |
| POP or IMAP account | ✘ | Account settings don’t import, but you can re-create the account in your G Suite profile. |
| Shared mailboxes | ✘ | Gmail does not support shared messages. |
| Category definitions | ✘ | Categories aren’t available in Gmail. |
| Category assignments | ✘ | Categories aren’t available in Gmail. |
| Microsoft Exchange data | Migrated to G Suite | Notes |
|---|---|---|
| Default calendar | ✔ | Includes all events, descriptions, attendees, and locations.
If you are using an exported or archived PST file, it's not possible to identify the primary root folder for Google Calendar and Contacts. Therefore, all calendars are migrated as “additional calendars” into Calendar, instead of any default calendar. You can avoid this by using a PST migration for mail only and use an Exchange server migration for migrating calendars. |
| Additional calendars | ✔ | Shared calendars are migrated for the owner, but not for other users who have access. |
| Event reminders | ✔ | |
| Free or busy status | ✔ | Only other G Suite users can see the availability status in Google Calendar. You can use the Calendar Interop tool to allow Exchange users to see the availability status of G Suite users. Learn more about Calendar Interop. |
| Calendar resources | ✔ | Use a comma-separated value (CSV) file to migrate calendar resources (such as meeting rooms) to G Suite. You can also change event attendees from email addresses in Exchange to G Suite email addresses. For details, see Create a CSV file for calendar resources. |
| Rich content in event descriptions | |
Descriptions created in Outlook 2016 are converted to plain text. |
| Tentative or Out of Office status | ✘ | Any special status for calendar data is not migrated. |
| Optional attendees | ✘ | Not migrated |
| Calendar attachments | ✘ | Not migrated |
| Category definitions | ✘ | Not available in Google Calendar. |
| Category assignments | ✘ | Not available in Google Calendar. |
| Microsoft Exchange data | Migrated to G Suite | Notes |
|---|---|---|
| All personal contacts | ✔ | Includes all fields (File As, images, notes, and so on). |
| Personal distribution lists | ✘ | Mailing lists don’t migrate to G Suite. But you can still email a list from G Suite by creating a Google group. |
| Multiple contact folders | |
Separate contact folders don’t migrate to G Suite. Instead, all contacts from all folders are migrated and then appear together in G Suite under My Contacts. You can reorganize them using Google Groups. |
| Rich formatting in personal contact notes | ✘ | Notes in contacts are migrated as plain text. |
| Notes larger than 16 KB | ✘ | Larger notes are truncated in G Suite. |
| Follow-up flags, dates, and reminders.
|
✘ | Flags aren’t available in Google Contacts. |
| Category definitions | ✘ | Not available in Google Contacts. |
| Category assignments | ✘ | Not available in Google Contacts. |
| Microsoft Exchange data | Migrated to G Suite | Notes |
|---|---|---|
| Domain contacts | ✘ | You need to migrate domain contacts separately. |
| Out-of-domain contacts | ✘ | You need to migrate out-of-domain contacts separately. |
| Microsoft Exchange data | Migrated to G Suite | Notes |
|---|---|---|
| Notes | ✘ | Not migrated. |
| Tasks | ✘ | Not migrated. |
| Journal entries | ✘ | Not migrated. |
| RSS feeds | ✘ | Not migrated. |
