We are excited to announce a new version of On Demand Migration for Email (ODME) 1.11 has been deployed.
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 are the highlights of what's new:
Release 184.108.40.20677 (10/30/2017)
For each successfully completed mailbox migration in a plan, ODME can send an email notification to the source and / or target recipient.
Scope: Microsoft Exchange, Microsoft Office 365, G Suite
Release 220.127.116.1186 (10/19/2017)
New migration source and target types are supported by migration template. With the migration template, now you can migrate to Exchange and Office 365 from these platforms:
· G Suite
· Office 365
Release 18.104.22.16884 (10/13/2017)
Now it is not required to enable IMAP for migrations from G Suite on the organization level unless you need 'Important' and 'Starred' target folders to have the same non-English localized names as the corresponding Gmail labels on the source.
Release 22.214.171.12498 (10/09/2017)
A number of mailboxes that can be migrated concurrently is not limited now. Total number of running plans with the same administrator account is not limited now.
Also, a number of mailboxes that can be migrated concurrently per single plan is configurable: it can be adjusted to any desired value or set to unlimited. The default value is 500.
Release 126.96.36.19985 (08/24/2017)
ODME is now able to migrate Recoverable Items from Exchange 2010 and higher.
Scope: Migration from Exchange 2010, 2013, 2016 and Office 365.
Release 188.8.131.5278 (08/04/2017)
Now you can create a migration plan from a template. The migration template was introduced to facilitate the creation of migration plan by specifying the connection properties and optional parameters for the migration.
Release 184.108.40.20665 (07/28/2017)
Microsoft Exchange Server 2000 is no longer supported as a migration source.
Release 220.127.116.1150 (07/19/2017)
Added possibility to configure various actions with forwarding on the source for migrations from Novell GroupWise:
· DELETE - When arrived, emails are deleted and meeting requests are declined
· KEEP - Emails remain in the Inbox folder
· MARK AS READ - Emails are marked as read in the Inbox folder
Release 18.104.22.16825 (06/22/2017)
ODME prompts users to install CPUU 5.7.2 for profile updates when migrating from Office 365 tenant to tenant with domain name transfer.
Release 22.214.171.12430 (06/12/2017)
Added support for migration of Sticky Notes.
Scope: Migration from Microsoft Exchange 2007, 2010, 2013, 2016 or Microsoft Office 365 to Microsoft Exchange 2010, 2013, 2016 or Microsoft Office 365.
Release 126.96.36.19994 (06/09/2017)
Message size limit:
· A message (including attachments if any) that exceeds the maximum message size (35 MB by default) will be skipped during the migration.
· If a message is smaller than the maximum message size, but it has attachments that break the size limit, the message will be migrated without the attachments.
Previously, the maximum message size was applied to a message body only.
Release 188.8.131.5296 (06/02/2017)
Migration of archive mailboxes from Exchange 2010 is now supported.
Scope: Migration from Microsoft Exchange 2010 to Microsoft Exchange 2010, 2013, 2016 or Microsoft Office 365
In case of the Move large attachments to OneDrive for Business option is not selected, both the migration throughput and content migration fidelity have been improved by using the Exchange Fast Transfer stream.
As a result, several product issues have been resolved. For details, see here.
Migration of mailboxes from Zimbra 6 and 7 is not supported anymore.
Release 184.108.40.20682 (05/24/2017)
The consumption of ODME resources was reduced for better scalability.
This enhancement was implemented to optimize the content of processing flow. As a result, the consumption of ODME resources per migrated mailbox has been decreased for the benefits of scalability.
Release 220.127.116.1134 (05/22/2017)
The volume of Azure storage that is used to facilitate gathering of migration statistics has been minimized. This lets you avoid excessive utilization of ODME resources in case of migration of extra-large mailboxes.
Scope: All supported migration scenarios.
Root-cause: ODME has the mechanism that facilitates gathering of migration statistics. This mechanism has the deficiency: excessive volume of Azure storage is consumed in case of migration of extra-large mailboxes. This deficiency leads to scalability issues that cause the migration slowdown.
For all supported migration scenarios, ODME internal application settings were aligned with Microsoft Azure best practices to ensure the best migration performance and scalability:
· ODME application settings are set to process concurrent user requests
· The Nagle’s algorithm that has a negative performance impact is turned off
Scope: Migration from G Suite to Exchange 2010, 2013 or 2016 and from Office 365 to Office 365
The migration performance has been increased up to 30 per cent by introducing multi-threaded upload operations.
Release 18.104.22.16841 (05/16/2017)
In order to allow connectivity to the source and target email service, it is required to ensure that your firewall is opened for the IP addresses used by ODME. The list of IP addresses in the About box from the ODME home page now includes only the product deployments for the current Azure region. So, the region cannot be changed once the customer account is registered.
Overall responsiveness of the ODME portal has been improved.
Release 22.214.171.12413 (04/28/2017)
Migration rescheduling strategy is improved for migrations from G Suite: Once the size of migrated content has achieved the value of Gmail daily throttling limit, ODME pauses. The duration of this pause is calculated to ensure that the migrated content size for the last 24 hours will not exceed Gmail daily throttling limit. This is especially beneficial for migration of extra-large mailboxes.
Release 126.96.36.19949 (04/25/2017)
ODME deployments now include Azure cloud data center in Australia.
Release 188.8.131.5219 (04/21/2017)
As for migration from G Suite, the overall migration rate has been improved due to change of the message extracting protocol from IMAP to GMAIL API. Therefore daily limit for the amount of data you can extract from your G Suite source during a migration has been safely increased from 2.2GB to 10GB.
The new value will be applied to all newly created plans by default. In order to safely apply the new value to an existing plan, you need to stop the plan and update this value manually.
For details refer to Managing Google Throttling.
ODME deployments now include Azure cloud data center in Canada.
Release 184.108.40.20652 (04/17/2017)
Migration performance improvement (up to 20%) through better resource utilization on Azure instance and significant enhancement of messages processing flow.
Migration to / from Office 365 China tenants (operated by 21Vianet) and Office 365 Germany tenants (operated by T-Systems) is fully supported now.
Release 220.127.116.1145 (03/31/2017)
Microsoft Azure components used in ODME have been upgraded to Azure SDK version 2.9.6 to comply with Microsoft Azure SDK retirement policies.
Release 18.104.22.16850 (03/28/2017)
· The Trusted API key generation tool for Novell GroupWise 7 has been rebranded to Quest.
· Introduced the digital signature for the Trusted API key generation tool for GroupWise 7 and Domino Web Service.
The full Migrator for Notes to Exchange Release Notes can be found on the technical documentation site.
For current customers, ODME 1.11 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.
As with all new releases, we love to hear any and all feedback. Tell us what you like, don't like, and if you have any ideas for future enhancements, please let us know on the discussion forums!