Answer:

This article provides details on specific items that cannot be migrated from each Source system.

Notes:

  • Big Green cannot migrate items that are not supported by a 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
    Notes:
    • 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.
  • 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 What are exceptions to recurring calendar meetings, and are they migrated?).
  • Customization of individual events in a series of 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 What are Dynamic Distribution Lists and are they migrated? 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 fonts)
  • 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 this TechNet article). For linked mailboxes, Exchange creates a disabled user account in the local forest that is used as a stand-in for the foreign account. Our tool 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. Exchange to Office 365, 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.
  • Tasks
  • Chats and chat history
  • Google Groups for Business, including forums and collaborative inboxes
  • Google Categories (i.e. 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

Google Drive:

  • Google Team Drives are not supported
  • 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
  • Scripts/Macros – Scripts are not converted to macros when going to documents
  • Document History
  • Comments
  • Items/folders in “Shared with Me” (items/folders must be in “My Drive” to be migrated)
  • Version history
    Note:     Free Google Drive accounts are not a supported Source for Google Drive migrations.

 

Google Sites:

  • Not supported.

 

GroupWise (Source):

  • 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
  • Document history
  • Version history

 

Office 365 Groups:

  •  Notebooks

 

Office 365 Planner:

  •  Data

SharePoint Online:

  • Site logos and customization
  • Task lists
  • Custom tasks
  • Newsfeed
  • Versioning
  • Metadata

Lotus Notes:

  • Lotus Distribution Groups
  • Lotus Mail Groups
  • Journals
  • Items in the Trash folder

Box.com:

  • Box Notes
  • Box Bookmarks
  • Box Tags
  • Version history
  • Shared Links

 

Dropbox:

  • Dropbox shared folder permissions
  • Dropbox Notes
  • Dropbox Bookmarks
  • Dropbox Tags
  • Version history

 

Amazon Storage:

  • Items with the Storage Class “Glacier” – Items archived to cold storage by Amazon’s retention policy

 

Exchange:

  • Email templates
  • Email flags (if the destination is G Suite)

 

Zimbra Tags

  • Zimbra Tags are not migrated.

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
  • IPF.StickyNote folders are not migrated

Collaboration Migrations: 

  • Private chats
  • Private group chats
  • 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.

Additional Notes:

Our tool is a content migration solution. Our service does not perform any of the following:

  • Creation of Outlook profiles.
  • Migration of client-side settings.
  • Provisioning of accounts.
  • Active Directory-related object creations or synchronization.
  • .NK2 file 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.