What items are not migrated with CloudM Migrate?

This article provides details on specific items that have limitations or cannot be migrated with CloudM Migrate.

CloudM Migrate 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 limitations or what is not migrated from all mail systems. The subsequent sections include details on limitations or what is not migrated from specific systems.

All Mail Systems (Source)

The following is a list of items that we do not migrate between mailboxes, due to API limitations:

  • Calendar: Modified description text and modified attendee lists for exceptions to recurring meetings are not migrated (although exceptions to recurring meetings are migrated).
  • Calendar: Customization of individual events in a series recurring events, e.g., Notes, are updated in some of the individual events.​​

Exchange / Office 365 (Source)

  • Mail: Copies of emails which exist in multiple folders will only be migrated once, from the first folder in which they are found. For all other folders, they will be skipped as "Already Exists". This may result in whole folders contents not being migrated.
  • Mail: Items that do not match folder types, i.e., calendar responses within a mail folder
  • Mail: 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
  • Calendar: Notifications such as invitations, cancellations, etc.
  • InfoPath Forms
  • Mail: Server-based Distribution Lists
  • Mail: Dynamic Distribution Lists
  • Mail: Bounce notifications such as Non-Delivery Report/Receipt (NDR) or Delivery Status Notification (DSN)
  • RSS feeds
  • Mail: Personal Messaging Resource Management (MRM) Tags
  • Mail: Outlook Quick Steps
  • Settings: 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
  • Settings: Server-side rules are not migrated - these include rules created by a user within the Outlook Web App or via the Exchange Admin Centre.
  • Settings: 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. CloudM Migrate can migrate linked mailboxes only if the mailbox is accessible via web access (OWA/EWS).
  • Mail: Color-coding for categories
  • Contacts: 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
  • Settings: Delegation - This is an EWS limitation, the setting cannot be exported
  • Contacts: Contact categories.
  • Contacts: Outlook Autocomplete list.
  • Contact Group ACLs.
  • OneDrive: Direct/Individual link sharing 

Exchange / Office 365 (Destination)

  • Calendar: Acceptance status for meeting participants (accepted, declined, tentative)
  • Mail: Email Signatures from Google are not supported in Office 365.

Google Workspace (Source)

  • Calendar: Calendar Reminders
  • Mail: Google Categories (i.e., the Google category flags: Social, Promotions, Updates, Forums)
  • Mail: Google 'Starred' messages are not 'Flagged' in Outlook.
  • Mail: Gmail "Snoozed" emails. This is a limitation with the Gmail API.
  • Mail: Gmail "Scheduled" emails are migrated to Office 365, but only as a draft in the 'All Mail' folder, scheduling is not migrated.
  • Google Keep Notes
  • Google Spaces cannot be migrated.

Google Workspace (Destination)

  • Google Templates - However, files that the template had been applied to are migrated
  • Drive: Document Scripts/Macros - Scripts are not converted to macros when going to documents
  • Drive: Document Version history

Free Google Drive accounts are not a supported source for Google Drive migrations

Google Workspace to Google Workspace

In relation to recurring events for a Google to Google migration, the below items are not supported for migration. the items below are supported for migration.

  • The recurring event itself
  • Change date / time into future of the event

In relation to recurring events for a Google to Google migration, the items below are not supported for migration.

  • Event titles on a recurring event
  • Event description
  • Shortening or lengthening of an event (1hr to 2hrs)
  • Adding / removing attendees
  • Specific event reminder times
  • Event is not migrated if moved to previous time or date behind the original event timestamp

OneDrive for Business

  • Creation date - Creation date gets changed to the "date of migration" date.
  • Document history
  • Version history
  • Direct/individual shareable links cannot be migrated to Google Drive. For more information about shareable links see here.

SharePoint Online

  • Site logos and customizations
  • Task lists
  • Custom tasks
  • News feed
  • Versioning
  • Metadata

Lotus Notes

  • Mail: Email categories - These are no longer a standard feature of the Lotus Notes mail database
  • Mail: Copies of emails which exist in multiple folders will only be migrated once, from the first folder in which they are found. For all other folders, they will be skipped as "Already Exists". This may result in whole folders contents not being migrated.
  • Mail: Lotus Distribution Groups

Box.com

  • Box Notes
  • Box Bookmarks
  • Box Tags
  • Version history​
  • Sharing links

Dropbox

  • Dropbox Paper Documents
  • Dropbox Notes
  • Dropbox Bookmarks
  • Dropbox Tags
  • Version history​
  • Team Spaces (Refer to this Dropbox article)
  • Sharing links

Exchange

  • Mail: Email templates

Exchange Public Folders

  • Mail: Only mail migration is supported from mail-enabled Exchange Public Folders.

Additional Notes

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

  • Creation of Outlook profiles
  • Migration of client side settings
  • 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.
  • Migration of version history for any system
Was this article helpful?
0 out of 0 found this helpful