Migration Tool Limitations

The following table describes the items that we migrate for various systems.

All Mail Systems (Source):

First, users that hidden from the address list, suspended or otherwise disabled, will not be migrated.

The following is a list of items that we do not migrate between mailboxes, due to API limitations and depending on the tool used; this is a general list:

• Local PST files and archived items (they can be reattached manually to the new Outlook profile)
• 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
  • Lone files and documents that are not attachments (attachments are migrated along with the email)
  • InfoPath Forms
• Calendar notifications such as invitations, cancellations, etc.
• Calendar permissions
• Modified description text and modified attendee lists for exceptions to recurring meetings are not migrated (although exceptions to recurring meetings are migrated).
• Customization of individual events in a series recurring events (e.g. notes) are updated in some of the individual events. 
• Acceptance status for meeting participants (accepted, declined, tentative)
  • From Exchange 2003: BCC recipients and resource attendees for appointments 
• Personal Distribution Lists.
  • Also known as "Contact Groups" in Outlook. They can be migrated manually via a PST file.
• Server-based Distribution Lists
• Dynamic Distribution Lists
• Distribution Groups / Memberships
• Bounce notifications such as Non-Delivery Report/Receipt (NDR) or Delivery Status Notification (DSN)
• RSS feeds
• Mailbox settings, sharing settings, delegates, client settings, e.g.:
  • Default font, Auto Archive settings 
  • Junk E-mail Safe Senders, Safe Recipient and Blocked Senders lists*, Signatures*, Client-side rules*

* Outlook Rules, Junk Email settings and Signatures can be migrated manually.

• Mailbox rules and folder permission settings. These are only supported from Exchange Server 2010 SP1+ and later to Exchange Server 2010 SP1+ and later (only if replicated to server, local Outlook only Rules will not migrate).
• Personal Messaging Records 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. We may can be able to migrate linked mailboxes only if the mailbox is accessible via web access (OWA/EWS). 
• Color-coding for categories
• Pictures added within a Business Card, under Contacts. Note:Pictures are included in the migration for the migration scenarios with high fidelity, such as:
  • From Exchange to Office 365
  • From Office 365 to Office 365
• AutoComplete cache
  • In Outlook 2010 and 2013, the Suggested Contacts folder will be migrated 
  • The LegacyExchangeDN can be imported if provided, to avoid internal bounce backs 
• Items 150MB or larger (Text, attachments, signature and pictures combined in the item) 
  • This is a server-wide limitation on our end that cannot be increased 
  • This size-limit may be smaller depending on the original server’s configuration

From 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 Apps, and so certain colors are not mapped over, thus the colors are not displayed in Office 365 for the calendar entries.
• Tasks
• 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
• Free Gmail.com & G Suite Legacy accounts cannot be migrated 

Lotus Notes:

• Lotus Distribution Groups
• Lotus Mail Groups
• Lotus Notes Archives
  
  

Additional Notes:

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 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 (depends on method).
• Migration of version history for any system

Special Note about calendars post migration:

This is an old known issue where calendar events cannot be updated post-migration. The actual origin of the issue is unknown.

This issue is not specific to Migration, it is a defect in Microsoft products. Please refer to the following Microsoft links:

• Outlook, Exchange and Out-of-Date meeting updates that are NOT OUT OF DATE! 

• Meeting request is out of date 

• Outlook Calendaring Issue : Meeting "Not Current", unable to accept meetingupdates. 

• Recurring Meeting "Not Current," unable to accept meeting requests 

• "This meeting request was updated after this message was sent" 

There are some indications this may be caused by a difference in clock times between the Outlook client, and the Exchange server.   It may also occur in some scenarios where cell phones update calendar items during synchronization.

This issue has been confirmed to occur with Microsoft migrations as well, using the Microsoft Exchange Mailbox Replication Service (MRS) Proxy service. In fact, there has been an open case where a premier customer who has had this issue using MRS since May 2014. Microsoft has not yet been able to provide a solution. Based on the information provided in the URLs above, this problem has been randomly affecting users for years.

The only workaround we've found is to have the organizer recreate the calendar event and send it out to all the recipients.