About On Demand Migration for Hybrid Exchange
Quest® On Demand Migration for Hybrid Exchange (ODMHE) cloud application securely migrates data between a Microsoft 365 tenant and an on-premises Microsoft Exchange without requiring organizations to install or maintain any software for the move. From a single portal, you can migrate multiple mailboxes simultaneously, including data such as email, calendar, contacts, and tasks.
Quest® On Demand Migration for Hybrid Exchange (ODMHE) is a part of Quest On Demand – a single SaaS console for managing your cloud environment in Microsoft Azure. For more information, see Quest On Demand documentation.
What We Migrate
The list below indicates mailbox components that can and cannot be migrated. Some limitations appear in unique customer migration scenarios, or arise due to platform or legacy support restrictions, and may not appear in the list below. In some cases, a solution to a limitation may already be on the product roadmap or available as a knowledge-based article.
ODMHE migrates the following Mailbox components:
| User mailbox |
✔ |
|
| Shared mailbox |
✔ |
|
| Resource mailbox |
✔ |
e.g. conference rooms, equipment |
| Inbox |
✔ |
|
| Folders |
✔ |
|
| Email |
✔ |
|
| Contacts |
✔ |
|
| Calendars |
✔ |
|
| Tasks |
✔ |
|
| Journals |
✔ |
|
| Notes |
✔ |
|
| Rules |
✔ |
|
| Folder Permissions |
✔ |
|
| Public folders |
✖ |
|
| Calendar acceptance status emails |
✔ |
|
| Resource calendar permissions (e.g. for conference rooms) |
✔ |
|
| Personal distribution lists |
✔ |
|
| Personal contacts |
✔ |
|
| Bounce notifications such as non-delivery reports or receipts (NDR) |
✔ |
|
| Delivery Status Notifications (DSN) |
✔ |
|
| Custom rules like color categorization of emails, specific logic, sub-calendars and flags |
✔ |
|
| Calendar notifications such as invites, responses, cancellations, etc. |
✔ |
|
| PST Connection to Outlook Profile |
✔ |
|
| Pictures that have been added within a Business Card |
✔ |
|
| Deleted items including recoverable deleted items. |
✔ |
|
| Mailbox permission settings, sharing settings (such as aliases; delegates) and other mailbox related setting |
✔ |
|
| Full Access permissions |
✔ |
|
| Send As permissions |
✔ |
|
| Receive As permissions |
✔ |
|
|
PST personal archives |
✖ |
Quest Offers a solution for PST to M365 migration |
| Safe Sender or Blocked Lists |
✖ |
|
| RSS Feeds |
✖ |
|
| Client settings (e.g, default fonts), folder views, outlook customizations |
✖ |
|
| User defined or custom fields |
✖ |
|
| Notifications scheduled more than one week in the future |
✖ |
Default notifications that are set to 15 or 30 minutes will be migrated. |
| Outlook Quick Steps |
✖ |
|
Signing up for Quest On Demand
To get access to On Demand Migration for Hybrid Exchange, you must sign up for the Quest On Demand service. Go to Quest On Demand and use one of the following options:
You must accept the Software Transaction Agreement before using this product.
Product Licensing
Use of this software is governed by the Software Transaction Agreement found at www.quest.com/legal/sta.aspx and the SaaS Addendum at www.quest.com/legal/saas-addendum.aspx. This software does not require an activation or license key to operate.
You can sign in to On Demand as a Guest user and review the solutions that the product offers. As a Guest user, you can add your Microsoft Entra ID tenant and look for problems that can be solved by On Demand. To sign in as a Guest user, go to quest-on-demand.com and click Continue as Guest.
Trial subscriptions are available. Visit Quest® On Demand Migration for Hybrid Exchange page for more information and pricing: https://www.quest.com/products/on-demand-migration/
In this topic:
To purchase a commercial subscription
- Open https://www.quest.com/products/on-demand-migration/.
- Click Request Pricing and fill in the necessary details.
- Click Contact Sales to request pricing and get help with your business needs.
The product licensing is based on the number of unique source mailbox types that are processed by the migration tasks. The licenses are only consumed once the migration task is started.
