On Demand Migration for Email Current - User Guide

Introduction Preparing Migrations Test and Pilot Migrations Configuring and Running Migrations Post Migration Glossary

Microsoft Exchange

Microsoft Exchange

General

  • When viewing migrated data in OWA, there may be slight differences in the received time of emails when comparing the source to the time recorded in the target. This affects all Exchange source environments and Exchange 2013/2016 target email services.
  • When migrating from an Exchange server, any email addresses associated with existing users will be converted to SMTP addresses based on the source system. This means that X500 addresses will not be migrated for items, and the SMTP address on the migrated items will not be updated to the new SMTP address. In order to get Exchange to update to the new address the primary SMTP address on the source system should be an alias on the target system.
  • For appointments migrated from Exchange 2007 to Office 365, the acceptance date on the target will be the date/time of the migration. Also, appointment owners will see “invitation not sent” for appointments with multiple attendees.
  • For Exchange-based targets, Groups are treated as Distribution Lists and cannot contain a contact with no email address. Because of this, any group members that do not have an email address on the source will not be migrated as a member of that group on an Exchange/O365 target. The contact will still migrate, it just cannot be a member of a group without an email address.
  • InfoPath items are not migrated from Office 365 and Exchange server.
  • Profile switch is not supported for Exchange Server 2010 as a target.

Rules

  • For OWA Inbox rules migration from Exchange server,
    • Using OWA together with Outlook to manage source rules may lead to duplication of rules on the target.
    • Autodiscover must be enabled on your target for successful rules migration.
    • During the migration, the name of a group participating in a source rule will be converted to an SMTP email address. The address is retrieved from the mailbox list of the migration plan, and will be used in the corresponding target rule.
    • Migration of OWA Inbox rules from or to personal archive is not supported.

    • ODME sets the "Stop processing rules" option for some OWA Inbox rules during migration.

Delegates

  • Migration of security groups as delegates is not supported for Exchange 2013 or earlier.
  • For migrations from Exchange server and Office 365, migration of customized set of delegate permissions is currently not supported:
    • Custom folder permissions are migrated as None (lack of any permissions) when the target delegate does not exist.
    • In case when the target delegate exists, source and target delegate permissions are merged and the predefined Roles (Editor, Author, Reviewer and None) take precedence over any Custom permission set.
    • In case when the target delegate exists and both source and target permissions are set to Custom, the target permissions will be set to None.

    See Migrating Delegate Access Permissions for details.

Folder Permissions

  • Migration of folder permissions for Recoverable Items is not supported.

  • Migration of folder permissions from personal archive and to personal archive is not supported.

GroupWise

GroupWise

  • In GroupWise 7, web page information and comments within contacts are not migrated. With all other supported versions, contact comments are merged into Outlook contact notes.
  • Task invites and items from the Search Folders do not migrate.
  • GroupWise tasks do not always contain time zone information. ODME infers a time zone based on the migrated mail data, which allows most tasks to appear on the correct day and time. However, in rare instances, a task may appear one day earlier after migration.
  • Outlook contacts only display three GroupWise contact email addresses. If there is a primary email address then it becomes the first email address listed.
  • Outlook contacts only display one IM address for each GroupWise contact. If there is a primary IM address, it becomes the only IM address.
  • Personalized subjects specified in the My Subject field of the GroupWise Personalize tab are not migrated.
  • ODME does not migrate folders that have the ProxyFolder type with the following message in the log: "The type of the <folder_name> folder is ProxyFolder, it will be skipped".
  • ODME does not migrate the Contacts folders shared by other users when migrating one user’s mailbox.

Office 365

Office 365

General

  • For Office 365/Exchange 2010, or Office 365/Exchange 2013, or Office 365/Exchange 2016 hybrid deployments, if your Office 365 configuration utilizes a shared domain configuration, On Demand Migration for Email will not able to locate your mailboxes.
  • InfoPath items are not migrated from Office 365 and Exchange server.
  • ODME does not migrate retention policies and retention tags from one Office 365 tenant to another Office 365 tenant.
  • ODME does not migrate some Contact fields from G Suite to Office 365.
    Fields that are currently supported:

    • Name

    • Job title, Company

    • Phone Numbers

    • Picture

    • Notes

    • Email Address

    • IM

    • Birthday

    • Relationship

    Custom G Suite fields that cannot be migrated from G Suite to Office 365:

    • Phonetic Last

    • Phonetic First

    • URL

    • Internet Call

    • Custom Fields

Rules

  • For OWA Inbox rules migration from Office 365,
    • Using OWA together with Outlook to manage source rules may lead to duplication of rules on the target.
    • Autodiscover must be enabled on your target for successful rules migration.
    • During the migration, the name of a group participating in a source rule will be converted to an SMTP email address. The address is retrieved from the mailbox list of the migration plan, and will be used in the corresponding target rule.
    • Migration of OWA Inbox rules from or to personal archive is not supported.
    • ODME sets the "Stop processing rules" option for some OWA Inbox rules during migration.

Delegates

  • Migration of security groups as delegates is not supported for Exchange 2013 or earlier.
  • For migrations from Exchange server and Office 365, migration of customized set of delegate permissions is currently not supported:
    • Custom folder permissions are migrated as None (lack of any permissions) when the target delegate does not exist.
    • In case when the target delegate exists, source and target delegate permissions are merged and the predefined Roles (Editor, Author, Reviewer and None) take precedence over any Custom permission set.
    • In case when the target delegate exists and both source and target permissions are set to Custom, the target permissions will be set to None.

    See Migrating Delegate Access Permissions for details.

Folder Permissions

  • Migration of folder permissions for Recoverable Items is not supported.

  • Migration of folder permissions from personal archive and to personal archive is not supported.

POP/Windows Live Hotmail

POP/Windows Live Hotmail

  • Only content located in the source inbox is accessible and migrated.
Related Documents