MigrationWiz: Migrated and Not Migrated Items

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. 

Which items are migrated?
  • 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.
Which items are not migrated?
  • 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 and Report Mailbox Migrated Items
The following item types and message categories are exported from the source during migration.
  • 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
IPM and Report Mailbox Not Migrated Items

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
The destination may affect which items may be migrated. Not all item types will migrate to all destinations. For such special cases, read the migration guide for details on management.

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.

Microsoft 365 Items
Migrated Not Migrated
  • Inbox
  • Folders
  • Email
  • 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)
Microsoft 365 Archive
Migrated Not Migrated
  • Folders
  • Email
  • 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

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.

OneDrive for Business Items
Migrated Not 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))
  • Versions & Metadata migrations only: Creation Date

 

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. 

SharePoint Items
Migrated Not 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. 

Migrated Not Migrated
  • Document libraries
    • Folders
    • Files
    • Permissions
    • Versions
    • Metadata (refer to the migration guide for more details)

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 Items
Migrated Migrated Team Settings Not Migrated

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
  • PDF
  • Website
  • Planner
  • OneNote

Google Drive

Google Drive Items
Migrated Not Migrated
  • 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
Google Vault (Source Only)
Migrated
  • Folders
  • Email

G Suite

Migrated - IMAP or G Suite (Gmail API) endpoints

G Suite Items
Migrated Not Migrated With Google API Endpoint at Source
  • Inbox
  • Folders/Labels
  • Email
  • Muted Email (as regular email)
  • Contacts
  • Calendars (including links for Google Hangouts within calendar meetings)
  • Calendar Notifications 
  • Google Categories (e.g., the Google category flags: Social, Promotions, Updates, Forums)

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

Limitations

  • When migrating from G Suite as a source, contacts in Contact Groups (which look like subfolders of the Contacts folder) will migrate to the top-level contacts folder on the destination. Folders will be created for each group but the contacts will not be sorted into those folders.
  • Calendars can have multiple Owners. An Owner is anyone with "Make changes and manage sharing" permissions, so shared calendars will be migrated to users with these permissions by default.
  • When migrating from G Suite as a source to Microsoft 365, although the calendar event is migrated for the organizer, the organizer’s attendance status for the calendar event is not migrated.

Google Shared Drive

Google Shared Drive Items

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

GSD_1.png

  • 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 Items
Migrated Not Migrated in Any Instance

Exchange Server 2007+

  • Inbox
  • Folders
  • Email
  • 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
  • Email
  • 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 Public Folders Items

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.

Migrated Not Migrated in Any Instance

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)
Exchange Archive Items

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

Migrated Not Migrated

Exchange Server 2010 SP1+

  • Folders
  • Email
  • 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

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.

Dropbox Items
Migrated Not Migrated

Migrated

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

File Server

(Source Only)

File Server Items
Migrated
  • Folder structure
  • Files
  • Permissions

GroupWise 7+ 

Groupwise 7+ Items
Migrated Not 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

IMAP & POP

IMAP & POP Items
Migrated
  • Inbox
  • Folders
  • Email

POP

POP (Source Only) Items
Migrated
  • Inbox
  • Email

Lotus Notes 6.5+ - 9.0.1 

Lotus Notes Items
Migrated Not Migrated
  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks

PST Archives

PST Items

PST Files from your own Azure storage.

Migrated Not Migrated
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes
PST BitTitan Storage

PST Files are 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
  • Items located in the root folder of the mailbox

Zimbra 6+

Zimbra Items
Migrated Not Migrated
  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
Was this article helpful?
3 out of 5 found this helpful