Possible Changes to Migrated Items

CloudM Migrate takes great care to ensure your messages and other items are migrated with the highest possible fidelity. In some cases changes can be made to items to allow migration to be possible. It is possible to disable these modifications but in many cases items may fail to migrate due to requirements of the destination platforms. The default settings are recommended to ensure that as many items migrate as possible.

Due to differences between the ways that the source and destination platforms store information, there may be some small changes made to migrated items.

Some source systems such as GroupWise and Lotus Notes do not store all email messages as RFC822 messages. Messages therefore have to be reconstructed from the source message and therefore are not in the exact same format that the messages are stored in the source system. This reconstruction is necessary to allow for messages to be migrated to any of the destination platforms. Messages are migrated from other platforms as RFC822 messages, as presented via the various platform APIs.

If you move an email on your source platform that that has previously been migrated, the email will appear in both the Inbox and folder that it was moved to on your destination platform if you attempt to migrate again. For example, if you delete an already migrated email on your source platform, the original email will still appear in the Inbox folder in the destination and a copy of the email will appear in the Deleted folder.

All Destination Platforms

• For GroupWise messages, any forwarded messages are embedded in the message that forwarded them.  If you have a message 'A' which forwards message 'B', then the body of message 'B' is appended to the body of message 'A' and any attachments that were attached to message 'B' are attached to message 'A'.
• Any OLE embedded objects cannot be transferred to the destination system and are removed.
• Rarely, embedded images in some HTML emails may be migrated as attachments.
• The 'From' header will be constructed from the migration user if the header is missing. Note: this will only occur if 'Modify Invalid Messages' is set to true.
• If no recipients are specified, one will be added using the migration user. Note: this will only occur if 'Modify Invalid Messages' is set to true.

Google Workspace as Destination

• The maximum message size in Google Mail is 50MB.  Messages within the source system may be greater than this due to attachment sizes.  To enable the message to be imported into Google Workspace attachments will be removed from the message and replaced with an empty attachment with the same name as the removed attachment, with '.removed' appended to the filename. Note: this will only occur if 'Modify Invalid Messages' is set to true.
• Google always changes the 'Received' headers of messages to be the date and time the message was received in GSuite during migration. This always changes the Received headers and there is no way to avoid this.
• If the body of a message is larger than approximately 50MB it is removed and replaced with text explaining that the body has been removed.  This is because the maximum message size of a message with Google Mail is 50MB and it is not possible to reduce the message body size. Note: this will only occur if 'Modify Invalid Messages' is set to true.
• Certain files, including executable files (and executable files contained within zip files) are not permitted in the Google system.  If a message is found in the Exchange or GroupWise system that contains an executable file as an attachment (including inside zip files), the attachment filename is renamed and '.renamed' appended to the filename.  Note that if there is a zip file contained within a zip file then the attachment will also be renamed. Note: this will only occur if 'Modify Invalid Messages' is set to true.
• Certain emails may not be imported if they do not conform to the RFC822 standard.  With all genuine messages this is not a problem, but some spam messages are sometimes not formed correctly and will not be transferred.
• Any attachments to appointments are not included with the appointment within Google Workspace.  This is due to a limitation of the Google Calendar API, where no attachments are permitted.If Email attachments have been migrated to Google Drive and the original attachments dropped from messages, the Email messages will no longer contain the attachments.
• If Email attachments have been migrated to Google Drive and the configuration option to add links into the Email messages to the migrated documents is turned on, then links will be added into the body of the message (both text and html parts).
• Recurring appointments are expanded and are migrated as single appointments to Google Workspace from GroupWise.  Other platforms migrate recurring appointments with the correct recurrence in place in most cases.  Some recurrence patterns from Lotus Notes are not compatible with the destination systems and therefore require expansion into individual appointments, or several recurring appointments.
• Recurring tasks are not migrated to Google Workspace as no recurrence for tasks exists in Google Workspace.  The main task is migrated as a single item.
• Email-based tasks are not linked to the email. The email body is included in the task body.
• Only the following Metadata will be attempted to be applied in a migration: Modified Date.  This can be enabled by setting Destination Platform / Advanced Settings / Preserve Modified Date to True and Source Platform / Advanced Settings / Document Sharing is set to 'Share Documents' or 'Share Documents and Send Notification email'.

Google Vault as Destination

• Depending on the maximum message size set in the configuration options attachments may be removed from the message and replaced with an empty attachment with the same name as the removed attachment, with '.removed' appended to the filename as per the description for Google Workspace. Note: this will only occur if 'Modify Invalid Messages' is set to true.
• If the body of a message is larger than the specified maximum message size it is removed and replaced with text explaining that the body has been removed.  Note: this will only occur if 'Modify Invalid Messages' is set to true.

Microsoft 365/Exchange 2007/2010/2013/2016 as Destination

• Depending on the maximum message size set in the configuration options attachments may be removed from the message and replaced with an empty attachment with the same name as the removed attachment, with '.removed' appended to the filename. Note: this will only occur if 'Modify Invalid Messages' is set to true.
• If the body of a message is larger than the maximum message size it is removed and replaced with text explaining that the body has been removed. Note: this will only occur if 'Modify Invalid Messages' is set to true.
• Currently, appointment or contact attachments are not supported.
• Recurring appointments are expanded and are migrated as single appointments to Exchange from GroupWise. Other platforms migrate recurring appointments with the correct recurrence in place in most cases. Some recurrence patterns from Lotus Notes are not compatible with the destination systems and therefore require expansion into individual appointments, or several recurring appointments.
• When migrating documents from Google Workspace, Google specific documents will be converted. e.g. Google Documents will be converted to Word Documents.
• If a 'Received' header does exist, CloudM Migrate will add one.  Exchange, Microsoft 365 and Outlook use Received headers for sorting email by date in the user interfaces.
• Only the following Metadata will be attempted to be applied in a migration: File Created and Modified Dates.  This can be enabled by setting Destination Platform / Advanced Settings / Preserve File Created and Modified Dates to True.

Google Groups as Destination

• If a message size is greater than 16MB attachments may be removed from the message and replaced with an empty attachment with the same name as the removed attachment, with '.removed' appended to the filename. Note: this will only occur if 'Modify Invalid Messages' is set to true.
• If the body of a message is larger than the maximum message size it is removed and replaced with text explaining that the body has been removed. Note: this will only occur if 'Modify Invalid Messages' is set to true.