This article covers a general overview of what items are and are not migrated for each environment when it is the source. However, every migration scenario is slightly different. MigrationWiz has different interactions with each supported environment based on connectors and permissions. As a result, the items migrated also differ by environment.
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 subsetting and some items which will also migrate which are not listed here. Scenarios that have specific item exceptions will have those exceptions noted in the migration guide. 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.
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.
Mailbox Items
Certain mailbox items are always migrated, regardless of source or destination.
- Date/Time
- Subject
- Body
- Importance
- Sensitivity
- Size
- Item Class
- Exceptions to recurring meetings
- Linked mailbox data (if accessible via EWS)
- Pictures are included in the migration in migration scenarios with high fidelity, e.g., for Exchange to Microsoft 365, and Microsoft 365 to Microsoft 365
- Personal Folder and Calendar Permissions (Exception for Exchange sources outlined below)
- Server-SideRules
Important
Consider that server-side rules are limited to Exchange On-Premise 2010+. Additionally, they may not be migrated if the destination does not accept the rule.
- Items that do not match folder types, e.g. 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
- Folder Calendar notifications
Important
We can only Export the content of mailboxes and folders to PST files. Will not be able to export other features like Folder and calendar permissions as PST files. - Modified description text and 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)
- Bounce notifications
- RSS feeds
- Mailbox sharing settings (aliases; client settings; delegates e.g. SendAs and SendOnBehalf rights)
- Personal Messaging Resource Management (MRM)
- Tags
- Outlook Quick Steps
- Client-Side Rules
- Custom color coding for categories
- Pictures added within a Business Card, under Contacts
- Server-based and dynamic distribution lists
- Private Chats
Warning
MigrationWiz no longer supports Teams private chat history as part of Mailbox migrations due to Microsoft's restriction on Teams data access through EWS. For more information please review this article.
- IPM.Appointment
- IPM.Contact
- IPM.Note
- IPM.Note.CommVault.Galaxy.Stub
- IPM.Note.GroupMailbox.WelcomeEmail
- IPM.Note.Microsoft.Conversation
- IPM.Note.Microsoft.Conversation.Archive
- IPM.Note.Microsoft.Conversation.Voice
- IPM.Note.Microsoft.Missed
- IPM.Note.Reminder.Event.2
- IPM.Note.Rules.OofTemplate.Microsoft
- IPM.Note.SMIME.MultipartSigned
- IPM.Note.Receipt
- IPM.Schedule.Inquiry
- IPM.Schedule.Meeting.Notification.Forward
- IPM.StickyNote
- IPM.Task
- REPORT.IPM.Note.CommVault.Galaxy.Stub.IPNNRN
- REPORT.IPM.Note.Delayed.DR
- REPORT.IPM.Note.DR
- REPORT.IPM.Note.IPNNRN
- REPORT.IPM.Note.IPNRN
- REPORT.IPM.Note.NDR
- REPORT.IPM.Note.Relayed.DR
The following item types and message categories are not exported from the source during migration.
- IPM.AbchPerson
- IPM.CalendarSharing.CalendarUpdate
- IPM.CalendarSharing.EventDelete
- IPM.CalendarSharing.EventUpdate
- IPM.ControlFlowMessage
- IPM.ControlFlowMessage.DocumentAnalyticsPropagation
- IPM.ControlFlowMessage.GraphTransactionMessage
- IPM.ControlFlowMessage.ModifyActionPropagation
- IPM.ControlFlowMessage.SharePointItemMaintenance
- IPM.ControlFlowMessage.SharePointItemRevokeAccess
- IPM.ControlFlowMessage.SharePointItemSecurityUpdate
- IPM.ControlFlowMessage.UserSubscriptionPropagation
- IPM.DistList IPM.Document.Word.Document.12
- IPM.File
- IPM.File.Document
- IPM.Document
- IPM.GroupMailbox.AddMemberRequest
- IPM.GroupMailbox.JoinRequest
- IPM.Outlook.Recall
- IPM.Recall.Report.Failure
- IPM.Recall.Report.Success
- IPM.Schedule.Meeting.Canceled
- IPM.Schedule.Meeting.Request
- IPM.Schedule.Meeting.Request.AttendeeListReplication
- IPM.Schedule.Meeting.Resp.Neg
- IPM.Schedule.Meeting.Resp.Pos
- IPM.Schedule.Meeting.Resp.Pos.SilentResponse
- IPM.Schedule.Meeting.Resp.Tent
- IPM.Sharing
- IPM.TaskRequest
- REPORT.IPM.Schedule.Meeting.Canceled.NDR
- REPORT.IPM.Schedule.Meeting.Request.IPNRN
- REPORT.IPM.Schedule.Meeting.Request.NDR
- REPORT.IPM.Schedule.Meeting.Resp.Pos.IPNNRN
- REPORT.REPORT.IPM.Note.IPNNRN.NDR
Special cases in email migrations
Hidden folders
If a system folder exists on both the source and the destination, MigrationWiz will detect it and migrate items to that location. For example, Exchange stores attachments in a hidden system folder called 'Files'. If the destination also has this folded, MigrationWiz will automatically migrate the items. As these are hidden, it may appear they did not migrate.
If the content needs to migrate to a different folder, use folder mapping to specify the new destination folder.
Encrypted Content
We migrate MIME content in an as-is state. S/MIME messages can be migrated and will remain encrypted at the destination. Viewing them on the destination requires the same certificate used to encrypt them, including their corresponding private key.
Messages with Azure Information Protection will be migrated, but will not be viewable at the destination, as the source tenant policies will not be available on the destination. To migrate in a viewable format, decrypt these messages on the source and migrate the decrypted emails. To encrypt them at the destination (this is optional), simply recreate the security policies on the destination and then reapply the policies to the migrated messages. Our data retention and security policies can be reviewed at our BitTitan Data Security and Privacy Policy page.
Color Categories
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 Microsoft 365. Any calendar colors on Google that are not any of the six (6) default colors on Microsoft 365 (blue, orange, green, purple, red, yellow) will be converted to the default color on Microsoft 365 (light red).
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.
Microsoft 365
The items below are migrated when Microsoft 365 is the source environment.
- Inbox
- Folders
- Contacts
- Calendars
- Tasks
- Journals
- Notes
- Server-Side Rules
- Folder Permissions
- Post (when the destination is Exchange or Microsoft 365)
- Automatic Replies (Out of Office Messages)
- Calendar acceptance status emails
- Safe Sender/Block Lists
- In-line images in Tasks
- Client-Side Rules (See the migration guide for limitations)
Groups
- Notebooks
- For Group documents: anything not in a document library (See SharePoint)
- Folders
- Contacts
- Calendars
- Tasks
- Journals
- Notes
- Server-Side Rules
- Folder Permissions
- BCC Recipients
- In-line images in tasks
- Items located in the root folder of the mailbox
- Save Sender/Block lists
- Calendar acceptance status email
OneDrive for Business
Important
In OneDrive to Google Drive migrations, OneNote files will be created as a folder containing .onetoc2 and .one files. This is expected behavior.
OneDrive to SharePoint document migration is not yet supported. The development team is fixing the bugs and will be supported near future.
Permissions Migrations
When OneDrive for Business is configured as the source of a document migration, the only permissions migrated are for files and folders that are shared with specific people using Direct Access
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.
- 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))
- Versions & Metadata migrations only: Creation Date
- Non-Versions & Metadata migrations:
- Creation date (Creation date gets changed to the "date of migration" date)
- Version History
- Links giving access
- Shared permissions for files/folders with symbols in name
SharePoint
SharePoint to OneDrive document migration is not yet supported. The development team is fixing the bugs and will be supported near future.
SharePoint Endpoint
The following items also pertain to Teams SharePoint migrations. However, only Document Libraries related to the Files tab will be migrated.
- Document libraries
- Permissions - individual folders and items only
- Versioning
- Metadata
- File/Folder name
- Modified date (based on the modified date of the latest version migrated)
- Modified by (based on the modified date of the latest version migrated)
- Created date (based on the created date of the latest version migrated)
- The description is migrated to the ‘Title' column at the destination. Migrated value is limited to the existing character limit of the 'Title’ field
- ‘Creator’ metadata is migrated but in some cases, this value may not be accurate.
- Site logos and customization
- Task lists
- Custom task
- Newsfeed
- Shared permissions for files/folders with symbols in name
- Site Pages
- Site/Site collection
- Permissions at site or library level
SharePoint migrations vary by endpoint combination and path followed. The following is an example of migrated items, but may not contain all items for your migration type. For specific migrated and non-migrated items, see your migration guide.
- Document libraries
- Folders
- Files
- Permissions
- Versions
- Metadata (refer to the migration guide for more details)
- Site/Site collection
- Site logos and customization
- Task lists
- Custom tasks
- Newsfeed
- Shared permissions for files/folders with symbols in the name
- Site Pages
- Any metadata referencing information from outside the document library (such as lists or other site-level data) is not migrated. For example external data, managed metadata, lookup, retention policy tags/retention labels
Teams
Due to Microsoft's limitations, private channels are not migrated.
To see what items are moved in Teams SharePoint migrations, see the SharePoint section.
Teams: Migrated teams may not appear in the same order. Users may drag and drop to reorder the lists.
- Public
- Private
- Organization-wide - these teams appear as public teams at the destination. Admin can change the privacy to organization-wide via the UI
- Team picture
- Team description
Channels
- Public and Private channels only. Shared channels are not migrated.
Conversations
- 60 messages per team will be displayed in the destination team. Channel conversation history is downloadable as an HTML file in the Conversation History tab.
- Conversation structure
- Root messages
- Replies
- Formatting - fonts, bullets, lists, colors
- Quotes
- Emojis
- Inline images & stickers
- Code snippets
- Hyperlinks
- GIFs
- Mentions (as plain text)
- Deleted message notifications - Messages will remain as deleted on the destination and show "Original message has been deleted."
Files
- Files in public teams and channels
- Files in private channels
Memberships
- Static memberships are migrated
The following tabs are migrated:
- Word
- Excel
- PowerPoint
- Website
- Planner
- OneNote
- Team description
- Team picture
- Guest permissions - guest access on the source will be migrated if the guest exists at the destination and guest permissions are enabled before migration. This may be done via the Teams of Office 365 admin portal
- Member permissions
- Create and update channels
- Create private channels
- Delete and restore channels
- Add and remove apps
- Create, update, and remove tabs
- Create, update, and remove connectors
- Delete messages
- Edit messages
- Tag @team or @[team name] (this will send a notification to everyone on the team)
- Tag @channel or @[channel name]. This will notify everyone who's shown the mentioned channel in their channel lists
- Guest permissions
- Create and update channels
- Delete channels
- Other permissions
- Enable Giphy
- Enable stickers and memes
- Allow memes to be uploaded
- Filter inappropriate content
Channel settings (Public channels)
-
- Channel moderation
- New post permissions
- Allow members to reply to channel messages
- Allow bots to submit channel messages
- Allow connectors to submit channel messages
OneNote
- OneNote tabs
Planner
- Tabs
- Plans
- Title
- Owner
- Settings (labels, descriptions, shared with)
- Buckets
- Title
- Order: 1-1 mapping of order will not be present between delta-passes. See the ‘Limitations’ section for more info
- Plan (which plan the bucket belongs to)
- Tasks
- Title
- Assignees
- Labels/Categories
- Parent Bucket
- Progress
- Start Date
- Due Date
- Task Details
- Notes
- Show on Card
- Checklist
- Attachments*
- Attachment preview
- Description
- Comments
- Priority
- Charts
*Only attachment links on the team's SharePoint site will be automatically remapped.
- Files that are uploaded directly at the task (files are eventually stored in the team's SharePoint site) will be automatically remapped
- SharePoint file links (links to files already in the team's SharePoint site) will be remapped
- No other links, including external links, will be remapped
Teams
- Team order - Teams may be manually reordered at the destination via drag and drop
Conversations
- Tags
- Likes & reactions
- Links to files and meeting requests
- Files previews
- Hyperlink previews
- Teams meeting invites in conversations
- Calendar previews - Calendar is an attachment and the Graph API does not support sending messages with attachments.
- Teams recordings
- Private chats
Memberships
- Dynamic memberships - all memberships are migrated as static, the user must recreate dynamic memberships
Settings
- User-specific settings - favorites, profile pictures, status messages, saved messages
- Allow members to upload custom apps
- Team code
- Channel settings: general/private. This is an API limitation. Default settings will be retained after migration
- Global/organization-wide and custom Teams messaging policy is currently not supported. These policies are used to control which chat and channel messaging features are available to users in Microsoft Teams
Other
- Wikis
- Yammer
- PowerBi reports
- Other apps/tabs
- Microsoft Teams Connect (aka shared channels). If the migrated teams contain shared channels, the shared channels will be skipped and conversations in them will not be migrated
Planner
- Task Details (Microsoft Graph API limitation)
- Created by
- Created date
- Last modified by
- Last modified date
- Completed by^
- Completed timestamp
- Assignee priority
The following tabs are not migrated:
- Document Library
- Wiki
- Stream
- PowerBI
- SharePoint page and List
- Yammer
- Flow
- Custom tabs
- Public or Private channel tabs linking to any location outside the team's document library.
- No EDU or Government (GCC High) tenant tabs are migrated. This includes tabs in public channels, private channels, 1:1 chats, group chats, and meeting chats
Google Drive
- Folders
- Folders you have shared
- Permissions
- G Suite native files
- Google Forms - migrated as a zip file containing the form as HTML and the responses as a CSV. Versions are not supported
- 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)
- 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 to migrate these items/folders
- Shortcuts (Migrated in Google Drive to Google Drive scenarios only.)
- Google Shared Drives (also known as Team Drives)
- Only when SharePoint Online is the Destination
- Personal / Free Google Drive is not supported
- File/folder shortcuts
- Google Photos (when Google Drive is the source)
- Folders
G Suite
Migrated - IMAP or G Suite (Gmail API) endpoints
Google Shared Drive
Migrated
- Files
- Folders
- Permissions
- Versions (up to 25)
- Metadata
- File/Folder name
- Modified (based on the modified date of the latest version migrated)
- Modified by
- Created (based on the created date of the latest version migrated)
- The description is migrated to the ‘Title' column at the destination. Migrated value is limited to the existing character limit of the 'Title’ field
- ‘Creator’ metadata is migrated but in some cases, this value may not be accurate. This is a current limitation without a workaround
- Shortcuts are migrated as a .URL file to the destination document library - if the target file exists within the same shared drive. Shortcuts are to be migrated as a subsequent migration step, after migrating all relevant documents & permissions
Not Migrated
- For some Google proprietary format files (e.g. Docs, Sheets, Slides), Google allows you to provide a custom name for a version of the file. Such version names are not migrated
- Minor revisions available for Google proprietary format files are not migrated
- Google Sites, Maps, and Apps Script files are not supported
- Embedded video/hyperlinks in Google docs, sheets, or slides may not be migrated accurately when these Google proprietary files are converted to Microsoft 365 format
- .TMP files are not supported
- Shortcuts will not be migrated if the target file doesn’t exist at the destination
- Versions are not supported by Google Forms
- Versions of Google drawing files (converted to images) are not migrated accurately. All migrated versions may display the same content as that of the latest version. This is due to a current API limitation. without a current workaround
Exchange
Migrated items vary by version.
If Exchange is the Source, and an account exists in the destination whose Primary SMTP prefix matches the Primary SMTP prefix of an account with Calendar Permissions in the Source, Calendar Permissions will be migrated, except for Resource Calendars. Resource Calendar permissions are not migrated.
If Exchange is the Source, and an account does not exist in the destination whose Primary SMTP prefix matches the Primary SMTP prefix of an account with Calendar Permissions in the Source, Calendar Permissions will not be migrated.
Exchange Server 2007+
- Inbox
- Folders
- Contacts
- Calendars
- Tasks
- Journals
- Notes
- BCC Recipients
- Post (when the destination is Exchange or Microsoft 365)
- Automatic Replies (Out of Office Messages)
Exchange Server 2010 SP1+
- Inbox
- Folders
- Contacts
- Calendars
- Tasks
- Journals
- Notes
- Post (when the destination is Exchange or Microsoft 365)
- Server-Side Rules
- Personal Folder and Calendar Permissions
- Automatic Replies (Out of Office Messages)
Exchange Server 2003 (Source Only)
- Inactive mailboxes
- Mailbox Rules
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 Mailbox Folders or Public Folders (Example: IPM.Document item types)
- System Public Folders
- 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), Automatic Replies (Out of Office Messages), Personal Folder and Calendar Permissions
Not Migrated in Exchange 2007: Public Folder Permissions
Important
Public Folders can only be migrated to other public folders or shared mailboxes. We do not migrate Public Folders to individual user mailboxes or Microsoft 365 Group mailboxes or vice versa. Mail-enabled public folders are not supported for destination endpoints that are Exchange On-Premise and will need to be mail-enabled manually.
Exchange 2007
- Public Folders
- Subfolders
Exchange 2010 SP1+ & Microsoft 365
- Public Folders
- Subfolders
- User Permissions
- Mail-Enabled Security Group Permissions (Default and Anonymous User Permissions are not supported)
- Automatic Replies (Out of Office Messages)
- Server-Side Rules
- Client-Side Rules
-
Print
-
Play a sound
-
Desktop Alerts
-
PintoTop -PintoTop action property exists in Outlook Wizard, but Service API doesn’t support
-
Display a specific message Alert window
-
Clear the Message
-
Permanently Delete
-
Exchange Server 2003 and Exchange Server 2007+ archives are not supported
Exchange Server 2010 SP1+
- Folders
- Contacts
- Calendars
- Tasks
- Journals
- Notes
- Server-Side Rules
- Client-Side Rules
-
Print
-
Play a sound
-
Desktop Alerts
-
PintoTop -PintoTop action property exists in Outlook Wizard, but Service API doesn’t support
-
Display a specific message Alert window
-
Clear the Message
-
Permanently Delete
-
- Folder Permissions
- BCC Recipients
Exchange Server 2010 SP1+
- Items located in the root folder of the mailbox
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
- Dropbox shared folder permissions
- Dropbox Notes
- Dropbox Bookmarks
- Dropbox Tags
- Dropbox Teams
- Version History
- Last Modified
- .paper files
File Server
(Source Only)
- Folder structure
- Files
- Permissions
GroupWise 7+
If the destination is Exchange, or Office 365:
- Inbox
- Folders
- Contacts
- Calendars
- Tasks
If the destination is not Exchange or Office 365:
- Inbox
- Folders
- Shared folders
- Contact and Calendar items to G Suite destination(s)
- Multi-user folders
- Frequent contacts
- Suggested contacts
IMAP & POP
- Inbox
- Folders
POP
- Inbox
Lotus Notes 6.5+ - 9.0.1
- Inbox
- Folders
- Contacts
- Calendars
- Tasks
- Lotus Distribution Groups
- All Documents view
- Lotus Mail Groups
- Journals
- Items in the Trash folder
- Resources field inside a Calendar event
- Task alarms & reminders
PST Archives
PST Files from your own Azure storage.
- Folders
- Contacts
- Calendars
- Tasks
- Journals
- Notes
- Follow Up flags
- Items located in the root folder of the mailbox
PST Files are uploaded to BitTitan Storage using the UploaderWiz tool.
- Folders
- Contacts
- Calendars
- Tasks
- Journals
- Notes
- Items with the Storage Class "Glacier" - Items archived to cold storage by Amazon's retention policy - are not migrated
- Items located in the root folder of the mailbox
Zimbra 6+
- Inbox
- Folders
- Contacts
- Calendars
- Tasks
- Zimbra Tags