Filtering Mailbox Folders
ODME supports for filtering mailbox folders to narrow down the migration scope when you migrate emails.
|
|
Caution: Migrating Deleted Items and Junk Email could significantly increase migration time. Also, non-mail items are not migrated from the Deleted Items folder. |
To filter folders for email migration:
- Click the Options tab.
- In the Folders section, select an option from the following:
- Migrate All: Migrates all folders in the mailbox.
- Exclude: Excludes the folders you select or specify (and sub-folders if any) from migration.
- Migrate Only: Only migrates the folders that you select or specify (and sub-folders if any).
- Migrate content to a custom folder - select this option to migrate a Google mailbox to a custom folder.
- Custom folder name - specify the name of the custom folder. If a custom name is not provided, the default name will be used.
|
|
TIP: When you specify folders in the textbox, type one fully qualified path per line, for example, Accounting/Notice. Press Enter to add more paths. |
The folders Inbox, Drafts and Conversation History in the Exclude list, and the option Migrate Only are only available when you migrate from Exchange or Microsoft 365, to Exchange or Microsoft 365.
If your folders are localized to another language, you can still select the corresponding checkboxes in English to filter them. However, when you specify folders in the textbox, type the localized folder names for the path.
Migrating Delegate Access Permissions
ODME supports migration of delegate access permissions from Exchange server and Microsoft 365.
To set up delegates migration:
- Click the Options tab.
- Open the Migrate Permissions portion of the screen.
- Select the Delegates option.
Matching information for source and target users is taken from the migration plan. During the migration of the delegate list for the mailbox, ODME checks for the presence of a delegate in the mailbox list of the plan. If the delegate is not in the list, it will not be migrated.
We recommend the following migration approach:
- To migrate delegates, create one or several separate plans in which:
|
|
NOTE: The following statuses will be displayed for the groups:
- Completed status when Use end-user credentials option is not selected.
- Interrupted status when Use end-user credentials option is selected.
- Interrupted status when the admin user account that is used to grant the consent to ODME does not have a valid Exchange Online license.
The statuses do not mean that something goes wrong. |
- You can run these plans as many times as necessary to synchronize the delegate permissions.
|
|
NOTE: After migration, the migration status of groups will show as Interrupted instead of Completed when end-user credentials are used for migration. No negative effects are found besides the status. |
In case target delegate does not exist, delegate access permissions are migrated by ODME as is. If the target delegate exists, a maximal value of the source and target access permissions will be set .
In case a set of permissions was customized the following exceptions of this rule are applicable, see the tables below and the Known Limitations section for details:
| None |
N/A |
None |
| Reviewer |
N/A |
Reviewer |
| Author |
N/A |
Author |
| Editor |
N/A |
Editor |
| Customized set (except None, Reviewer, Author, Editor) |
N/A |
None |
| None or customized set (except None, Reviewer, Author, Editor) |
None or customized set (except None, Reviewer, Author, Editor) |
None |
|
Customized set (except None, Reviewer, Author, Editor) |
Reviewer or
Author or
Editor |
Reviewer or
Author or
Editor (value from target)
|
| Reviewer or
Author or
Editor |
Customized set (except None, Reviewer, Author, Editor) |
Reviewer or
Author or
Editor (value from source) |
| Reviewer or
Author or
Editor |
Reviewer or
Author or
Editor |
Maximal value of the source and target access permissions.
Possible values - Reviewer or
Author or
Editor |
Migrating Folder Permissions
ODME supports migration of folder permissions from Exchange server and Microsoft 365.
|
|
Note: Migration of folder permissions for Recoverable Items is not supported. |
To set up migration of folder permissions:
- Click the Options tab.
- Open the Migrate Permissions portion of the screen.
- Select the Folder Permissions option.
Matching information for source and target users is taken from the current migration plan.
We recommend the following migration approach:
- To migrate folder permissions, create one or several separate plans in which:
|
|
NOTE: The following statuses will be displayed for the groups:
- Completed status when Use end-user credentials option is not selected.
- Interrupted status when Use end-user credentials option is selected.
- Interrupted status when the admin user account that is used to grant the consent to ODME does not have a valid Exchange Online license.
The statuses do not mean that something goes wrong. |
You can run these plans as many times as necessary to synchronize the folder permissions.
-
For the content migration, use migration plans as usual and do not check the Folder Permissions option in these plans.
In case the target permission does not exist, permissions are migrated by ODME as is. If the target permission exists, a maximal value of the source and target access permissions will be set .
| None |
N/A |
None |
| Owner |
N/A |
Owner |
| Publishing Editor |
N/A |
Publishing Editor |
| Editor |
N/A |
Editor |
| Publishing Author |
N/A |
Publishing Author |
| Author |
N/A |
Author |
| Nonediting Author |
N/A |
Nonediting Author |
| Reviewer |
N/A |
Reviewer |
| Contributor |
N/A |
Contributor |
| Custom |
N/A |
Custom |
Migrating Rules
ODME supports rules migration from Microsoft 365, Exchange 2019, 2016, 2013, and 2010. This includes OWA (Outlook Web App) Inbox rules, and the rules created in an Outlook client version 2019, 2016, 2013, 2010, or Outlook for Microsoft 365.
|
|
NOTE: Migration of rules created in Outlook from Exchange 2010 is not supported yet. |
To migrate rules
- Create a separate plan in which:
- Only the Rules option is selected. Other items from the Select Items to Migrate partition are not selected.
- A list of mailboxes contains all mailboxes that planned to be migrated by ODME and groups that can potentially participate in the rules to be migrated. These groups will not be migrated, they will be used only for the matching operation.
|
|
NOTE: The following statuses will be displayed for the groups:
- Completed status when Use end-user credentials option is not selected.
- Interrupted status when Use end-user credentials option is selected.
The statuses do not mean that something goes wrong. |
- To migrate other content (such as messages, contacts), use migration plans as usual and do not check the Rules option in these plans.
Matching information for source and target users is taken from the migration plan. When the source email address is an Active Directory user or group, you must specify the email address with its primary domain name in the target, or rules may not work properly after migration. During the migration of the rules for the mailbox, ODME checks for the presence of a user or group in the mailbox list of the plan. If the user or group is not in the list, rules will not be migrated.
|
|
Caution: Every time you run the migration plan to migrate rules, ODME removes all the existing rules from your target first (including previously-migrated rules, and the rules you created in the target), and then migrates all the rules on the source to your target. |
|
|
Caution: If the rules in a user's target Outlook do not match the rules on the server, the following message appears when the user opens the target mailbox in Outlook after migration:
The rules on this computer do not match the rules on Microsoft Exchange. Only one set of rules can be kept. You will usually want to keep the rules on the server. Which rules do you want to keep?
In this case, the user has to select "Server" to avoid data loss. |
Rules that contain unsupported conditions or actions will not be migrated, or will not work after migration. So, you will need to set them up manually on the target. For other known limitations to migration of rules, see the Rules section in Microsoft Exchange or Microsoft 365
The following tables list the supported conditions and actions for rules created from Outlook:
| from people or public group |
Yes |
Yes |
Yes |
Yes |
Yes |
| with specific words in subject |
Yes |
Yes |
Yes |
Yes |
Yes |
| through the specified account |
No |
No |
No |
No |
No |
| sent only to me |
Yes |
Yes |
Yes |
Yes |
Yes |
| where my name is in the To box |
Yes |
Yes |
Yes |
Yes |
Yes |
| marked as importance |
Yes |
Yes |
Yes |
Yes |
Yes |
| marked as sensitivity |
Yes |
Yes |
Yes |
Yes |
Yes |
| flag for action |
Yes |
Yes |
Yes |
Yes |
Yes |
| where my name is in the Cc box |
Yes |
Yes |
Yes |
Yes |
Yes |
| where my name is in the To or Cc box |
Yes |
Yes |
Yes |
Yes |
Yes |
| where my name is not in the To box |
Yes |
Yes |
Yes |
Yes |
Yes |
| sent to people or public group |
Yes |
Yes |
Yes |
Yes |
Yes |
| with specific words in the body |
Yes |
Yes |
Yes |
Yes |
Yes |
| with specific words in the subject or body |
Yes |
Yes |
Yes |
Yes |
Yes |
| with specific words in the message header |
Yes |
Yes |
Yes |
Yes |
Yes |
| with specific words in the recipient's address |
Yes |
Yes |
Yes |
Yes |
Yes |
| with specific words in the sender's address |
Yes |
Yes |
Yes |
Yes |
Yes |
| assigned to specific category |
Yes |
Yes |
Yes |
Yes |
Yes |
| assigned to any category |
Yes |
Yes |
Yes |
Yes |
Yes |
| which is an automatic reply |
Yes |
Yes |
Yes |
Yes |
Yes |
| which has an attachment |
Yes |
Yes |
Yes |
Yes |
Yes |
| with a size in a specific range |
Yes |
Yes |
Yes |
Yes |
Yes |
| received in a specific date span |
Yes |
Yes |
Yes |
Yes |
Yes |
| uses the specific form |
Yes |
Yes |
Yes |
Yes |
Yes |
| sender is in specific Address Book |
No |
No |
No |
No |
No |
| with selected properties of documents or forms |
Yes |
Yes |
Yes |
Yes |
Yes |
| which is a meeting invitation or update |
Yes |
Yes |
Yes |
Yes |
Yes |
| from RSS feeds with specified text in the title |
Yes |
Yes |
Yes |
Yes |
Yes |
| from any RSS feed |
Yes |
Yes |
Yes |
Yes |
Yes |
| of the specific form type |
Yes |
Yes |
Yes |
Yes |
Yes |
| on this computer only |
Yes |
Yes |
Yes |
Yes |
Yes |
| move it to the specified folder |
Yes |
Yes |
Yes |
Yes |
Yes |
| move a copy to the specified folder |
Yes |
Yes |
Yes |
Yes |
Yes |
| assign it to the specific category |
Yes |
Yes |
Yes |
Yes |
Yes |
| delete it |
Yes |
Yes |
Yes |
Yes |
Yes |
| permanently delete it |
Yes |
Yes |
Yes |
Yes |
Yes |
| forward it to people or public group |
Yes |
Yes |
Yes |
Yes |
Yes |
| forward it to people or distribution list as an attachment |
Yes |
Yes |
Yes |
Yes |
Yes |
| redirect it to people or distribution list |
Yes |
Yes |
Yes |
Yes |
Yes |
| have server reply using a specific message |
No |
No |
No |
No |
No |
| reply using a specific template |
Yes |
Yes |
Yes |
Yes |
Yes |
| flag message for action in a number of days |
Yes |
Yes |
Yes |
Yes |
Yes |
| clear the Message Flag |
Yes |
Yes |
Yes |
Yes |
Yes |
| clear message's categories |
Yes |
Yes |
Yes |
Yes |
Yes |
| mark it as importance |
Yes |
Yes |
Yes |
Yes |
Yes |
| print it |
Yes |
Yes |
Yes |
Yes |
Yes |
| play a sound |
Yes |
Yes |
Yes |
Yes |
Yes |
| start application |
N/A |
No |
No |
No |
N/A |
| mark it as read |
Yes |
Yes |
Yes |
Yes |
Yes |
| run a script |
N/A |
No |
No |
No |
N/A |
| perform a custom action |
N/A |
N/A |
N/A |
No |
N/A |
| display a specific message in the New Item Alert window |
Yes |
Yes |
Yes |
Yes |
Yes |
| display a Desktop Alert |
Yes |
Yes |
Yes |
Yes |
Yes |
| apply retention policy |
No |
No |
No |
No |
No |
| stop processing more rules |
Yes |
Yes |
Yes |
Yes |
Yes |
The following tables list the supported conditions and actions for OWA Inbox rules:
| Message was received from the specified users or groups in GAL |
Yes |
Yes |
Yes |
Yes |
| Message was sent to the specified users or groups in GAL |
Yes |
Yes |
Yes |
Yes |
| Message contains the specified words |
in the subject |
Yes |
Yes |
Yes |
Yes |
| in the subject or body |
Yes |
Yes |
Yes |
Yes |
| in the sender's address |
Yes |
Yes |
Yes |
Yes |
| in the body |
Yes |
Yes |
Yes |
Yes |
| in the recipient's address |
Yes |
Yes |
Yes |
Yes |
| in the message header |
Yes |
Yes |
Yes |
Yes |
| My name is |
in the To or Cc box |
Yes |
Yes |
Yes |
Yes |
| the only recipient listed |
Yes |
Yes |
Yes |
Yes |
| in the To box |
Yes |
Yes |
Yes |
Yes |
| in the Cc box |
Yes |
Yes |
Yes |
Yes |
| not in the To box |
Yes |
Yes |
Yes |
Yes |
| Message is marked with |
Importance |
Yes |
Yes |
Yes |
Yes |
| Sensitivity |
Yes |
Yes |
Yes |
Yes |
| Message is |
accompanied by an attachment |
Yes |
Yes |
Yes |
Yes |
| of the type... |
Yes |
Yes |
Yes |
Yes |
| flagged as... |
Yes |
Yes |
Yes |
Yes |
| classified as... |
No |
No |
No |
No |
| Message size is within a specified range |
Yes |
Yes |
Yes |
Yes |
| Message was received within a specified date span |
Yes |
Yes |
Yes |
Yes |
| Apply to all messages |
Yes |
Yes |
Yes |
Yes |
| People |
From |
Yes |
| To |
Yes |
| My name is |
I'm on the To line |
Yes |
| I'm on the Cc line |
Yes |
| I'm on the To or Cc line |
Yes |
| I'm not on the To line |
Yes |
| I'm the only recipient |
Yes |
| Subject |
Subject includes |
Yes |
| Subject or body includes |
Yes |
| Keywords |
Message body includes |
Yes |
| Sender address includes |
Yes |
| Recipient address includes |
Yes |
| Message header includes |
Yes |
| Marked with |
Importance |
Yes |
| Sensitivity |
Yes |
| Classification |
Yes |
| Message includes |
Flag |
Yes |
| Type |
Yes |
| Has attachment |
Yes |
| Message size |
At least |
Yes |
| At most |
Yes |
| Received |
Before |
Yes |
| After |
Yes |
| All messages |
Apply to all messages |
Yes |
| Move message to folder |
Yes |
Yes |
Yes |
Yes |
| Copy message to folder |
Yes |
Yes |
Yes |
Yes |
| Delete message |
Yes |
Yes |
Yes |
Yes |
| Pin message |
Yes |
Yes |
N/A |
N/A |
| Mark message |
as read |
Yes |
Yes |
Yes |
Yes |
| as junk |
Yes |
Yes |
N/A |
N/A |
| with importance |
Yes |
Yes |
Yes |
Yes |
| with a category |
Yes |
Yes |
Yes |
Yes |
| Forward message to... |
Yes |
Yes |
Yes |
Yes |
| Forward message as an attachment to... |
Yes |
Yes |
Yes |
Yes |
| Redirect message to... |
Yes |
Yes |
Yes |
Yes |
| Send a text message to... [*] |
Yes |
Yes |
Yes |
Yes |
| Stop processing more rules |
Yes |
Yes |
Yes |
Yes |
[*] This action will not work after migrated to Microsoft 365 because Microsoft 365 does not support it.
| Organize |
Move to |
Yes |
| Copy to |
Yes |
| Delete |
Yes |
| Pin to top |
Yes |
| Mark message |
Mark as read |
Yes |
| Mark as Junk |
Yes |
| Mark with importance |
Yes |
| Categorize |
Yes |
| Route |
Forward to |
Yes |
| Forward as attachment |
Yes |
| Redirect to |
Yes |
| Stop processing more rules |
Yes |
