What items are not migrated with MigrationWiz?
This article provides details on specific items that cannot be migrated from each Source system.
- 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 > Microsoft Word in OneDrive for Business.
- The first section of this article includes details on what is not migrated from all mail systems. The subsequent sections include details on what is not migrated from specific systems; these include mail and document systems, and also Exchange Public Folders.
All Mail Systems (Source):
The following is a list of items that we do not migrate between mailboxes, due to API limitations:
- Items that do not match folder types, i.e., calendar responses within a mail folder
- Custom items that do not inherit from the core system types
- Example: Items which are not true email, calendars, contacts, journals, mail, notes, or tasks
- InfoPath Forms
- Calendar notifications such as invitations, cancellations, etc.
- Calendar permissions
- 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.
- 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.
- Modified description text and modified attendee lists for exceptions to recurring meetings are not migrated (although exceptions to recurring meetings are migrated). Further details can be found in KB005105).
- Customization of individual events in a series recurring events, e.g., Notes, are updated in some of the individual events.
- User-defined/custom fields for Contact items
- Acceptance status for meeting participants (accepted, declined, tentative).
- Note: From Exchange 2003: BCC recipients and resource attendees for appointments.
- Personal Distribution Lists. These are known as "Contact Groups" in Office 365.
- Server-based Distribution Lists
- Dynamic Distribution Lists.
- Note: Refer to KB005378 for more information.
- Bounce notifications such as Non-Delivery Report/Receipt (NDR) or Delivery Status Notification (DSN)
- RSS feeds
- Mailbox settings, sharing settings, aliases, delegates, client settings, e.g., default font
- 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 rules are not migrated. Client-only rules do not execute until the user who created the rules logs into the Outlook client with the same profile used to create the rule.
Linked mailboxes (described in: https://technet.microsoft.com/en-us/library/bb123524.aspx). For linked mailboxes, Exchange creates a disabled user account in the local forest that is used as a stand-in for the foreign account. MigrationWiz can migrate linked mailboxes only if the mailbox is accessible via web access (OWA/EWS).
Color-coding for categories
Pictures that have been added within a Business Card, under Contacts. Note: Pictures are included in the migration for the migration scenarios with high fidelity, e.g., for Exchange to Office 365, and Office 365 to Office 365.
G Suite (Source):
- Calendar Attachments
- Calendar Reminders
- Some calendar colors
- Note: All color category metatags 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.
- 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)
We can only migrate items that are visible through IMAP
Email attachments that are links to Google Drive
G Suite (Destination):
- Calendar Attachments
- Exceptions of recurring appointments
- Google Groups for Business, including forums and collaborative inboxes
- Personal Google Drive is not supported
- Google Forms
- Google Templates - However, files that the template had been applied to are migrated
- Creation Date - Creation date gets changed to the "date of migration" date
- Modification Date
- Scripts/Macros - Scripts are not converted to macros when going to documents
- Document History
- Version history
- Note: Free Google Drive accounts are not a supported Source for Google Drive migrations.
- Pages that are not of template type "File Cabinet"
- Files attached to a page that is not a File Cabinet
- Subpages that are File Cabinet
There are three types of Google sites. These are listed below, along with explanatory text and the expected migration results.
Explanation: These are sites that were created many years ago. The current Google Sites REST API is unable to access these legacy sites, and thus they cannot be migrated using MigrationWiz.
Migration result: If a migration attempt is made, no sites will discovered, and an error message will be returned. The error will state: "No sites are under this domain."
Explanation: The existing Google Sites REST API only works with the sites created prior to Nov. 2016.
Migration result: Google calls these "Classic Sites" and they are fully supported for migration.
Explanation: Any site created after Nov. 2016 is automatically considered to be a New site. The existing Google API does not work properly with a New site, and so New Sites are not supported for migration.
Migration result: If a migration attempt is made, the file cabinets within the Site will become anonymous, so there will not be an ID/Name to use to retrieve the file folder via the Google API.
- Shared folders
- Contact and Calendar items to G Suite Destination(s)
- Multi-user folders
- Frequent contacts
- Suggested contacts
OneDrive for Business:
- Creation date - Creation date gets changed to the "date of migration" date
- Modification date
- Document history
- Version history
Office 365 Groups:
Office 365 Planner:
- Site logos and customizations
- Task lists
- Custom tasks
- News feed
- Lotus Distribution Groups
- Lotus Mail Groups
- Items in the Trash folder
- Box Notes
- Box Bookmarks
- Box Tags
- Version history
- Dropbox shared folder permissions
- Dropbox Notes
- Dropbox Bookmarks
- Dropbox Tags
- Version history
- Items with the Storage Class "Glacier" - Items archived to cold storage by Amazon's retention policy
- Email templates
Exchange Public Folders:
- Mail Settings
- Standalone documents stored in Public Folder
- Exchange 2003: Public Folders
- Exchange 2007: Public Folder Permissions
- System Public Folders are not migrated, as they do not reside in the IPM_Subtree and are not discoverable with Migration Wiz
IPF.StickyNote folders are not migrated
MigrationWiz is a content migration solution. Our service does not perform any of the following:
- Creation of Outlook profiles (DeploymentPro handles this)
- Migration of client side settings
- Provisioning of accounts
- Active Directory-related object creations or synchronization
- NK2 files migration
- Propagation of updates, deletes, or moves of items previously migrated from prior migration passes, because we do not have “live” monitoring of changes (as with a sync agent), and we cannot handle scenarios such as conflict resolution without user interaction.
- Migrations from individual user mailboxes to Public Folders or vice versa. Public Folders can only be migrated to other Public Folders or shared mailboxes.
- Migration of version history for any system