The data migration service migrates email, calendar, or contact data to Google Workspace using the Google Admin console. Consider the following data, and whether it's migrated, when you're setting up the data migration service.
Migration status of source data
EmailYou can migrate email using the data migration service if you're migrating from these source accounts.
Supported email features
These features apply across all source accounts.
| Email data | Notes |
|---|---|
| Email messages | All email in top-level folders is migrated. A top-level folder is any folder that is at the same level as your inbox folder.
You can exclude some types of email messages and top-level folders from a migration. For details, go to Exclude data that doesn't need to be migrated. |
| Email state, such as read or unread | |
| Deleted items | Migration is optional and can be excluded. Deleted items are labeled Trash in Gmail. |
| Junk email | Migration is optional and can be excluded. Junk email is labeled Spam in Gmail. |
| Large messages and attachments | Most attachments are migrated, unless the message plus attachment is larger than 25 MB, or when Gmail blocks certain types of file attachments, such as executable files. For details, go to File types blocked in Gmail. |
| Message flags | Flags appear as stars in Gmail. |
| Folders |
Folders are migrated as distinct labels in Gmail. Usually the labels have the same name as the source. If there’s a naming conflict between a folder and a Gmail reserved system label (such as Sent, Trash, or Unread), the messages are migrated to the reserved label. You can exclude specific top-level folders from a migration by individually selecting them. If you exclude a folder, its subfolders are also excluded. A Microsoft Exchange mailbox and some IMAP servers allow subfolders under default email folders. This includes Exchange default folders such as Sent Items, Drafts, or Deleted Items. Subfolders under these default folders don't migrate as nested labels. Your Exchange mailbox might also have other folders created by you. These top-level folders exist at the same hierarchy level as your default email folders. Subfolders under other folders do migrate in a nested state. For example, Financial/Q1 Invoices. During migration, a folder's full path becomes the label name. Folders with folder paths longer than 225 characters aren’t migrated. The messages inside the folders are also not migrated. |
Supported Exchange Server or Exchange Online (Microsoft 365) features
| Email data | Notes |
|---|---|
| Shared mailboxes | Shared mailboxes migrate as regular mailboxes. You can allow Gmail delegation after the migration. For details, go to Turn Gmail delegation on or off. |
Supported Google Workspace & Gmail email features
| Email data | Notes |
|---|---|
| Gmail labels | Labels are replicated. Emails located in the Inbox label of the source account transfer to the Inbox label of the destination account. |
Unsupported email features
| Email data | Notes |
|---|---|
| Public folders in Exchange or Exchange Online | |
| Posts in mailbox folders | |
| Importance levels of messages | |
| Rules or filters | Rules (both server and client) or filters aren’t migrated but you can create equivalent filters in Gmail. |
| Signatures | Signatures aren’t migrated but can be recreated in Gmail. |
| Category definitions or assignments |
You can migrate calendar events and resources using the data migration service if you're migrating from these Exchange or Exchange Online source accounts.
Supported calendar features
| Calendar data | Notes |
|---|---|
| Default calendar | Includes all events, descriptions, attendees, and locations. |
| Additional calendars | Shared calendars are migrated for the owner, but not for other users who have access. |
| Event reminders | |
| Free or busy status | Free/Busy visibility information is migrated for statuses such as busy, tentative, out of office, free, working elsewhere, etc. |
| Event response status | Event response information is migrated for statuses such as accepted, rejected, tentative, no response, deleted, etc. |
| Calendar resources | Examples include a meeting room, projectors, company fleet cars, guest offices, recreation equipment, or any other resource people might schedule a time to use. Learn more |
| Attendees | If you import events for users who are not an original organizer or initial attendee for the event, the event successfully migrates into Google Workspace and the target user is shown as an attendee of the event in Google Calendar. |
| Rich content in event descriptions | Rich text descriptions are converted to plain text. |
Unsupported calendar features
| Calendar data | Notes |
|---|---|
| Calendar attachments | |
| Category definitions or assignments |
You can migrate contacts using the data migration service if you're migrating from these Exchange or Exchange Online source accounts.
Supported contact features
| Contact data | Notes |
|---|---|
| Personal contacts | Fields migrated include name, organization, birthday, website, email, phone, and addresses. |
Unsupported contact features
| Contact data | Notes |
|---|---|
| Multiple contact folders | |
| Contact groups or personal distribution lists | You can still email a list from Google Workspace by creating a Google Group. |
| Follow-up flags, dates, and reminders | |
| Category definitions or assignments | |
| Notes | |
| Global domain contacts | Domain contacts appear in the Global Address List (GAL) in Microsoft Active Directory. To import these contacts, you must use a different product. For details, go to About Google Cloud Directory Sync. |
Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.
