This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

The latest version of On Demand Migration for Email is 1.12

Quest® On Demand Migration for Email securely migrates data to Office 365 and on-premises Exchange or hosted Exchange email platforms leveraging a hosted infrastructure to minimize the footprint within each organization. From a single console, you can migrate multiple mailboxes simultaneously, including data such as email, calendar, contacts, and tasks.

Sign up for a free trial of On Demand Migration for Email here.

Here is a summary of what's new:

  • Migration of Outlook Web App Inbox rules is now supported
  • Migration of Exchange folder permissions are now supported
  • New "Role Groups" have been created within ODME to control permissions within your ODME account: Manage Migration Plans, Execute Migration Plans, Manage Migration Plans From Templates, and Execute Migration Plans From Templates

Below is an exhaustive list of the new features and enhancements since the last minor release of ODME:

Release (08/07/2018)


Migration of Outlook Web App Inbox rules is now supported.

Migrations from Office 365, Exchange 2016, 2013, and 2010.

For more details, see Migrating OWA Inbox Rules in On Demand Migration for Email User Guide.


Migration of mailbox rules is now supported by Client Profile Updating Utility for the scenarios when Outlook is used to create and manage rules (together with Outlook Web App or not). For details, see Updating Outlook Client Profiles.

Release (07/26/2018)


Migration of folder permissions is now supported.

Migrations from Exchange or Office 365

Release (07/20/2018)


Manage Migrations permission is now ready to deprecation and we introduce 4 new permissions: Manage Migration PlansExecute Migration PlansManage Migration Plans From Templates, and Execute Migration Plans From Templates to replace Manage Migrations permission. These permissions are automatically granted to the default roles Full Administrator and Migration for Email Admin.

TIP: Now you can optimize the permission set for more granularity. For details see Roles and Permissions.

Release (07/04/2018)


Added support for migration of mailboxes that are hidden from the Exchange Global Address List.

Migrations from Exchange or Office 365

Release (07/02/2018)


IBM Notes and Domino is no longer supported as a migration source.

Release (06/01/2018)


If the full paths to the Conversation History folder are not the same between the source and target (for example, you moved the Conversation History folder to another location in the source), the folder will be migrated as a normal folder, unless you move it back to its default location in the source before migration.

Migrations from Exchange or Office 365

Release (05/21/2018)


Azure AD Single Sign-On is now supported to access On Demand Migration for Email.

Release (05/06/2018)


For on-premises migrations only.

There are additional IP addresses that On Demand Migration for Email connects from. Please read this KB article for more details.

Release (05/01/2018)


Introduced a new user role "Read" providing the following abilities:

·         View the existing migration plans (including those created from a template) and templates.

·         Download and view audit logs for a migration template.

·         Download and view all types of reports for migration.

For more details, see Roles and Permissions in On Demand Migration for Email User Guide.

Release (04/20/2018)


Migration of delegate permissions is now supported. Some limitations are applicable, for details see herefor Microsoft Exchange and here for Microsoft Office 365.

Release (04/03/2018)


ODME now migrates from Lotus Notes using the MIME method by default (the latest version of Quest Domino Web Service is required).

NOTE: If you do NOT want to migrate using the MIME method, add the following to the <appSettings> section in the file web.config for the Domino Web Service, and restart Internet Information Services:

<add key="UseMimeMigration" value="false" />

Release (03/16/2018)


Support for Microsoft Office 365 F1.

Release (02/05/2018)


This specific instance of ODME is designed for United States Public Sector customers only and addresses their requirements of:

·         Content is stored within the United States.

·         Content is restricted to Quest personnel that are US Citizens and these personnel undergo background investigations in accordance with relevant government standards.

Release (01/29/2018)


Maximum size limit for a message can be changed on the Options | Advanced tab.

Release (01/23/2018)


Improved the method to calculate the migration time: If a migration is completed by several parts (e.g., paused and resumed), the migration time will calculate a total for every part of the migration (the duration that the migration stays in the Rescheduled state will NOT be counted).

Release (12/19/2017)


ODME now migrates color categories from the source mailbox to the target mailbox with incremental merge.

·         Only the color categories and shortcut keys that do not exist in the target mailbox will be migrated or merged.

·         The name and color of categories that already exist in the target mailbox will not be changed.

Migration from Exchange 2007, 2010, 2013, 2016 or Office 365 to Exchange 2010, 2013, 2016 or Office 365

Release (12/13/2017)


Active Directory Federation Services (AD FS) is now supported to access ODME. For more details, see here.


Provided online help for setting up mail forwarding for GroupWise as the source on the Options tab > Forwarding (Optional), and removed information about the forwarding actions from the documentation.

Release (12/08/2017)


The user notification settings have been moved to the new tab Notification where you can now specify different 'From display names' and 'From email addresses' for the source and target mailboxes.

NOTE: For existing migration plans with the option Send notification to target mailbox selected previously, the 'From display name' and 'From email address' need to be specified again after this release.


ODME now supports an IMAP migration using user names only.

Migration from IMAP


Enhancements to migration plans that were copied from a plan that was previously created using a template:

·         The new plan has a subtitle "Created from [template_name]" on the Dashboard.

·         The new plan will keep the connection properties and optional parameters specified by the template, and the same read only fields as the source plan.

Release (12/06/2017)


Moving large attachments to OneDrive for Business is no longer supported.

Release (12/01/2017)


Microsoft Exchange Server 2003 is no longer supported as a migration source.

Release (11/29/2017)


The message filters processing is optimized to reduce number of Gmail API queries. It helps diminish the risk of exceeding the Gmail API daily usage quota.

Migration from G Suite


Release (11/28/2017)


The number of queries to Gmail API per each migrated message is reduced. It helps diminish the risk of exceeding the Gmail API daily usage quota.

Migration from G Suite


The full On Demand Migration for Email Release Notes can be found on the technical documentation site.


For existing customers, ODME 1.12 has already been deployed. Any new migrations will be using this new version of ODME.

For customers that are interested in evaluating ODME, you can sign up for a trial here.