Contact Support
Start with BitTitan Perform a Migration Solve a Problem

Which Items Are and Are Not Migrated by MigrationWiz?

Avatar
Jaym Gates
  • Updated
Follow

Introduction

MigrationWiz has different interactions with each supported environment based on connectors and permissions. As a result, the items migrated also differ by environment.

The best way to use this article is to check items migrated by your source, and ending with your destination. However, if you are migrating email environments, there are many properties which migrate no matter the source or destination. So, if you’re migrating from Exchange 2006 to G Suite, you would want to navigate to Special Note: Email Items, then to Exchange Migrated Items, followed by G Suite Migrated Items.

As environment permissions and settings change frequently, and we are always adding new functionalities and options to MigrationWiz, we suggest checking back regularly to see if new items have been added.

This is not a comprehensive list. There are subsettings and some items which will also migrate which are not listed here. If you have questions or concerns about a specific item not listed here, Support can answer your questions and help you choose the best migration path.

 

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.

MigrationWiz 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
  • Color categories for calendars

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
  • Linked mailboxes
  • 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.

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 accounted for by MigrationWiz and 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 BitTitan migration metadata (author, editor, created time, modified time, name, filesize, type, MigrationWizId, MigrationWizPermissionId)
  • 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
  • Channels - All public channels are migrated. Important: MigrationWiz does not migrate private Teams channels by default. If the global administrator is an owner of a private channel, the migrated channel will be created as public channel at Destination with no content migrated. Note that once a private channel is migrated as a public channel, it cannot be made into private and cannot be deleted and recreated.
    • 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: MigrationWiz only supports document migrations from SharePoint for Collaboration migrations. We do not support migrations from any other storage point.

  • All private data
  • 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)

Google Drive

Migrated

  • Folders
  • Folders you have shared
  • Permissions
  • G Suite native files (except Google Forms)
  • Code Files
  • Documents
  • Images
  • Executables
  • Videos
  • Audio Files
  • Templates (files that the template had been applied to are migrated)
  • Creation Date (Creation date gets changed to the "date of migration" date)
  • Scripts/Macros (Scripts are not converted to macros when going to documents)
  • Document History
  • Comments
  • File/Folder permissions
  • Items/folders in "Shared with Me”. These folders must be added to the user’s “My Drive” and Moderate Mode must be used in order to migrate these items/folders. 

Not Migrated

  • Google Shared Drives (also known as Team Drives) are not supported

    • This is largely because Shared Drives use a different root folder than Google Drive does. Shared Drives also follow different organization, sharing, and ownership models, so the same methods used to migrate Google Drive will not work to migrate Shared Drives.

  • Personal / Free Google Drive is not supported

 

Google Vault (Source Only)

Migrated

  • Folders
  • Email

 

G Suite

Migrated - IMAP or G Suite (Gmail API) endpoints

  • Inbox
  • Folders/Labels
  • Email
  • Muted Email (as regular email)
  • Contacts
  • Calendars (including links for Google Hangouts within calendar meetings)
  • Calendar Notifications

Note: Links for Google Hangouts are a new default feature added to Google Meeting. Microsoft Office 365 doesn't have the corresponding property to map. Therefore, when migrating to Office 365, the links for Google Hangouts are added to the beginning of the meeting description body text on Office 365.

Not Migrated in Any Instance

  • Calendar Reminders
  • Appointments

Not Migrated As Source

  • Calendar Attachments
  • Calendar Reminders
  • Tasks
  • Chats and chat history
  • Google Groups for Business (including forums and collaborative inboxes)
  • Google Categories (i.e., the Google category flags: Social, Promotions, Updates, Forums)
  • Email attachments that are links to Google Drive
  • Some calendar colors

Note: All color category meta tags are transferred over, but Office 365 does not have direct color mappings from Google G Suite, and so certain colors do not get mapped over, thus the colors are not displayed in Office 365 for the calendar entries.

Not Migrated As Destination

  • Calendar Attachments
  • Exceptions of recurring appointments
  • Google Groups for Business (including forums and collaborative inboxes)

 

With Google API Endpoint at Source

With this endpoint, all items listed above migrate as before. However, utilizing the API endpoint enables migration of the following items as well. The following items are not migrated via the IMAP endpoint. 

Migrated

  • Google Categories (Category flags, i.e. Social, Promotions, Updates, Forums)
  • Snoozed and Scheduled emails - these are migrated like regular emails to custom destination labels. Their properties are not migrated.

Not Migrated

  • Chats & chat history

 

G Suite Archive (Destination Only)

Migrated

  • Folders
  • Email

 

Exchange

Not Migrated in Any Instance

  • Inactive mailboxes

Exchange Server 2003 (Source Only)

Migrated

  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes
  • Post (when the destination is Exchange or Office 365)

Exchange Server 2007+

Migrated

  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes
  • BCC Recipients
  • Post (when the destination is Exchange or Office 365)

 

Exchange Server 2010 SP1+

Migrated

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

Not Migrated in any Exchange Instance

  • Email templates
  • Email flags (if the destination is G Suite)
  • Safe Sender/Block Lists
  • Mail Settings
  • Standalone documents stored in Public Folders
  • System Public Folders
  • IPF
  • StickyNote folders

Not migrated in Exchange 2003: Public Folders, BCC recipients on email items or optional attendees of calendar entries (Microsoft Exchange Web DAV API does not return this information for items)

Not Migrated in Exchange 2007: Public Folder Permissions

 

Exchange Public Folders

Note: Public Folders can only be migrated to other public folders or shared mailboxes. We do not migrate Public Folders to individual user mailboxes or vice versa.

Exchange 2003 & 2007

Migrated

  • Public Folders
  • Subfolders

Exchange 2010 SP1+ & Office 365

Migrated

  • Public Folders
  • Subfolders
  • User Permissions
  • Mail-Enabled Security Group Permissions (Default and Anonymous User Permissions are not supported)

 

Exchange Archive

Exchange Server 2003 and Exchange Server 2007+ archives are not supported

Exchange Server 2010 SP1+

Migrated

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

 

Dropbox

Note: When Dropbox is configured as the Source, shared folders and items are migrated to the Destination but their shared permissions are not. Likewise, when Dropbox is configured as the Destination, shared folders and items are migrated from the Source but their shared permissions are not.

Migrated

  • Folders
  • Shared Folders
  • Code Files
  • Documents
  • Images
  • Forms
  • Executables
  • Videos
  • Audio Files

Not Migrated

  • Dropbox shared folder permissions
  • Dropbox Notes
  • Dropbox Bookmarks
  • Dropbox Tags
  • Version history
  • .paper files

 

File Server

(Source Only)

Migrated

  • Folder structure
  • Files
  • Permissions

 

GroupWise 7+ (Source Only)

Migrated

If the Destination is Exchange, or Office 365:

  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks

If the Destination is not Exchange or Office 365:

  • Inbox
  • Folders
  • Email

Not Migrated

  • Shared folders
  • Contact and Calendar items to G Suite Destination(s)
  • Multi-user folders
  • Frequent contacts
  • Suggested contacts

 

IMAP & POP

Migrated

  • Inbox
  • Folders
  • Email

 

IMAP Archives (Destination Only)

Migrated

  • Folders
  • Email

 

POP (Source Only)

Migrated

  • Inbox
  • Email

 

Lotus Notes 6.5+ - 9.0.1 (Source Only)

Migrated

  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks

Not Migrated

  • Lotus Distribution Groups
  • Lotus Mail Groups
  • Journals
  • Items in the Trash folder
  • Resources field inside a Calendar event

 

PST Archives (Source Only)

PST Files from your own Azure storage.

Migrated

  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes

 

PST BitTitan Storage (Source Only)

PST Files uploaded to BitTitan Storage using the UploaderWiz tool.

Migrated

  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes

 

Amazon Storage

Items with the Storage Class "Glacier" - Items archived to cold storage by Amazon's retention policy - are not migrated

 

Zimbra 6+ (Source Only)

Migrated

  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks

Not Migrated

  • Zimbra Tags

 

 

 

Related articles

Comments

0 comments

Please sign in to leave a comment.