Special Note - Email Items

Certain email items are always migrated, regardless of source or destination. As this is a long article with many lists, we have collected these items and organized them by migration type.

This is not an exhaustive list. It includes only the typical Destinations. The complete list of supported Destinations can be seen under Destination settings when creating the project.

We cannot migrate items that are not supported by the Destination, although, in some cases, we can convert items from the Source to something that is accepted on the Destination, e.g., Google Docs in Google Drive to Microsoft Word in OneDrive for Business.

Always Migrated

• Date/Time
• Subject
• Body
• Importance
• Sensitivity
• Size
• Item Class
• Exceptions to recurring meetings
• Linked mailbox data (if accessible via EWS)

Note: The default colors will be maintained during migration. However, if additional color categories have been defined at the Source, other than those supported at the Destination, they will not be migrated. Instead, they will be converted to the default calendar color at the Destination. For example, Google supports more calendar colors than Office 365. Any calendar colors on Google that are not any of the six (6) default colors on Office 365 (blue, orange, green, purple, red, yellow) will be converted to the default color on Office 365 (light red).

Never Migrated

• Items that do not match folder types, i.e. calendar responses within a mail folder. Important: If an item type is migrated into a folder of a different type at the destination, the item will not be visible.
• Custom items that do not inherit from the core system types
• InfoPath Forms
• Calendar permissions
• Calendar notifications
• Modified description text & modified attendee lists for exceptions to recurring meetings
• User-defined/custom fields for Contact items
• Acceptance status for meeting participants
• Personal distribution lists ("Contact groups" in Office 365)
• Server-based and dynamic distribution lists
• Bounce notifications
• RSS feeds
• Mailbox sharing settings (aliases; delegates; client settings)
• Mailbox rules and folder permission settings (these are only supported from Exchange Server 2010 SP1+ and later to Exchange Server 2010 SP1+ and later)
• Personal Messaging Resource Management (MRM) Tags
• Outlook Quick Steps
• Client-side rule
• Color-coding for categories
• Pictures that have been added within a Business Card, under Contacts.
• Calendar meeting links: Lync, Skype or Teams events will be migrated but will usually not work in the destination because the links are for the source environment. These events will need to be recreated at the destination. There are exceptions to this rule, but they are not consistent.
• Encrypted Emails: For all Source email systems, any email sent or received using encryption methods will not migrate. The emails will need to be decrypted before they can be migrated.

Pictures are included in the migration in migration scenarios with high fidelity, e.g., for Exchange to Office 365, and Office 365 to Office 365.

If Exchange is the Source, and an account exists in the Destination that matches the UPN prefix of an account with Calendar Permissions in the Source prior to submitting a migration, Calendar Permissions will be migrated, except for Resource Calendars. Resource Calendars permissions are not migrated.

If Exchange is the Source, and an account does not exist in the Destination that matches the UPN prefix of an account with Calendar Permissions in the Source prior to submitting a migration, Calendar Permissions will not be migrated.

 

Office 365

Migrated

• Inbox
• Folders
• Email
• Contacts
• Calendars
• Tasks
• Journals
• Notes
• Server-Side Rules
• Folder Permissions
• Post (when the destination is Exchange or Office 365)
• Calendar acceptance status emails

Not Migrated

• Safe Sender/Block Lists

Groups

Not Migrated

• Notebooks

Planner

Not Migrated

• Data

 

Office 365 Archive

Migrated

• Folders
• Email
• Contacts
• Calendars
• Tasks
• Journals
• Notes
• Server-Side Rules
• Folder Permissions
• BCC Recipients

 

OneDrive

Permissions Migrations

When OneDrive for Business is configured as the source on a document migration, the only permissions migrated are for files and folders that are shared with specific people.

Files or folders in OneDrive for Business can be shared in one of three ways:

• With specific people
• With anyone
• With an organization

When files or folders are shared with anyone or with an organization, a link is generated for the items. These links are not migrated to any destinations, including other OneDrive for Business accounts.

Migrated

• Folders
• Shared Folders
• Permissions
• Code Files
• Documents
• Images
• Forms
• Executables
• Videos
• Audio Files
• Original metadata and migration metadata (author, editor, created time, modified time, name, filesize, type)
• Document attributes (Created by (person) and (time)
• Modified by (person) and (time))

Not Migrated

• Creation date (Creation date gets changed to the "date of migration" date)
• Document history
• Version history
• Links giving access
• Shared permissions for files/folders with symbols in name

SharePoint

Migrated

• Document libraries
• Permissions

Not Migrated

• Site logos and customization
• Task lists
• Custom task
• Newsfeed
• Versioning
• Metadata
• Shared permissions for files/folders with symbols in name

 

Teams

 

Migrated

• Teams
  • Public
  • Organizational
  • Archived teams - moved as public teams and must be re-archived at destination.
• Channels - All public channels are migrated. 
  • Conversations
  • Structure
  • Format
  • Root messages
  • Replies
  • Fonts
  • Bullets
  • Lists
  • Colors
  • Quotes
  • Emojis
  • Inline images and stickers
  • Code snippets
  • Hyperlinks
  • GIFs
  • Deleted message notifications;
  • Mentions (as plain text to prevent duplicate notification after migration)
  • Timestamps (in UTC)
• Files (except files in private chats): All files outside of private chats are migrated.
• Memberships: All memberships are migrated.

Not Migrated

Note: We only support document migrations from SharePoint for Collaboration migrations. We do not support migrations from any other storage point.

• All private data
• Private conversations and files under the Chat tab
• Likes/Reactions
• Links to files and meeting requests in conversation threads
• File previews
• Hyperlink previews
• Calendar previews
• User-specific settings (Favorites, Profile pictures, Status messages, and saved messages)
• Dynamic groups (the groups will be migrated, however, they will be migrated as static groups)
• Tabs (for example: Planner, Yammer, etc. No custom tabs will be migrated, either)
• Customized Team settings (these include team picture, member permissions, guest permissions, mentions, etc. New Teams will be created with the Default settings)
• Team list order (after migration, Teams will not appear on the Destination in the same order as on the Source. Users can drag and drop to reorder the list of teams)
• Wikis
• Tags (after migration, the name of the tag will be in plaintext if it was included in a conversation)
• Due to Microsoft limitations, private channels are not migrated for GCC High Tenants.