Understanding the EdbMails Office 365 Migration Application
Before starting an Office 365 migration, it helps to understand the EdbMails application and the main areas you will use during a migration. This page explains the application interface and its core components, including source and target connections, mailbox selection, mapping, migration settings, progress monitoring, and reports. It is intended to help administrators become familiar with the application before configuring a migration job.
Main Components of the Application
Source and Target Connection
The source and target connections are used to establish access to the Office 365 environments involved in the migration. After the required authentication and permissions are configured, you can connect the source and target accounts separately and continue with mailbox selection and migration setup.
For connection instructions, see Office 365 source server connection and Office 365 target server connection.
Mailbox Loading and Selection
Once the source and target environments are connected, EdbMails can load the available mailboxes for the migration job. You can review the mailbox list and select the users that need to be processed. Depending on the migration scenario, mailbox information can also be supplied through a CSV file.
Mailbox Mapping
Mailbox mapping connects each source mailbox with its corresponding target mailbox. EdbMails supports automatic and user-defined mapping options, allowing administrators to review the source-to-target relationship before the migration begins. Verify the mapping carefully when mailbox names, addresses, or environments differ between the source and destination.
For more information, see Map the Mailboxes.
Migration Settings
Migration settings control how the selected mailbox data is processed. Depending on the migration scenario, administrators can configure the data types and other available migration options before starting the job. Review these settings before migration so the selected configuration matches the requirements of the project.
Include and Exclude Filters
Filters can be used when you need more control over the data included in a migration. They help administrators define the scope of the migration instead of processing every supported item in the source mailbox. The available filter options depend on the selected migration scenario and application settings.
Migration Job Configuration
After connections, mailbox selection, mapping, and migration settings have been reviewed, the migration job can be configured and started. The application keeps these settings together so administrators can review the job configuration before transferring mailbox data.
Migration Progress
During a migration, the application displays the progress of the job so administrators can monitor the selected mailboxes and identify completed, pending, or failed operations. Reviewing the progress information during a migration can help identify issues that need attention before the job is completed.
Migration Reports and Logs
Migration reports and logs provide information about the results of the migration. Administrators can use them to review mailbox status, processed items, errors, warnings, and other job details. Keep the relevant reports after migration so the results can be checked during validation or troubleshooting.
Incremental Migration
When a migration needs to be run again before cutover, incremental migration can be used to process new or changed items from the source. For the same source and target setup on the same computer, subsequent runs can transfer items that were not included in the earlier pass. Review the migration reports after each run and perform a final incremental pass close to cutover when required.
For details, see Office 365 Incremental Migration.
Understanding the Migration Interface
The application brings the main migration tasks together in a single workflow. Administrators can connect the source and target environments, load and select mailboxes, verify mapping, configure available settings, start the migration, and review progress and reports. The exact options displayed can vary according to the migration scenario and the type of source and destination selected.
When to Use Each Application Component
| Application component | What it is used for |
|---|---|
| Source connection | Connect to the environment from which mailbox data is being migrated. |
| Target connection | Connect to the destination environment where the selected data will be migrated. |
| Mailbox loading | Retrieve and select the mailboxes that should be included in the migration. |
| Mailbox mapping | Match source mailboxes with their corresponding target mailboxes. |
| Filters | Control the supported data included in the migration. |
| Migration settings | Configure the available options for the selected migration job. |
| Progress window | Monitor migration activity and review the status of the job. |
| Reports and logs | Review migration results, errors, warnings, and mailbox status. |
| Incremental migration | Process new or changed source items during a repeat migration run. |
System Requirements and Setup
Before using the application, review the current Office 365 Migration system requirements and the EdbMails Installation Process. The required operating system, application components, permissions, and connectivity can vary according to the migration scenario.
Migration Scenarios
EdbMails supports different Office 365 migration scenarios, including tenant-to-tenant migration, Office 365 to Exchange, PST-related migrations, and other supported migration paths. Before configuring the application, review the Office 365 Migration Scenarios page to identify the workflow that matches your environment.
