How EdbMails Office 365 Migration Works

EdbMails migration workflow at a glance

Source & target connection → Authentication & permissions → Object discovery & selection → Source-to-target mapping → Data transfer & processing → Repeat migration if required → Post-migration validation

This page explains what happens at each stage. Detailed configuration, migration scenarios, and feature-specific instructions are linked to their dedicated pages so that administrators can go directly to the procedure they need.

1. Connect and authenticate the source and target

Start by connecting the source and target environments used for the migration. The migration accounts must have the roles and permissions required for the selected workload and destination. For Microsoft 365 connections, EdbMails supports modern authentication/OAuth-based authorization, including environments where multi-factor authentication is enabled.

 For authentication configuration, see Office 365 MFA authorization. If you need to check access before migration, see validate Office 365 mailbox permissions.

2. Discover and select migration objects

After a successful connection, EdbMails loads the migration objects available to the authenticated account. Administrators can select the mailboxes or supported workloads required for the job rather than treating every available object as part of one migration.

Workload-specific requirements are covered on their own pages. For example, use the dedicated guidance for shared mailbox migration, Office 365 public folder migration, and archive mailbox migration when those objects are in scope.

3. Map source objects to the target

Before data transfer begins, source objects must be associated with the correct destination. EdbMails provides mailbox-mapping options to help administrators pair source and target mailboxes. When the default mapping does not match the required destination, custom mapping can be used to define the source-to-target relationship.

Target preparation depends on the migration scenario and tenant configuration. Confirm that the required destination objects, permissions, and licenses are available before starting the transfer.

 For custom assignments, see user-defined mailbox mapping.

4. Transfer and process the selected data

Once mapping is confirmed, EdbMails processes the selected supported data from the source and writes it to the mapped destination. Migration filters can be applied when only a defined subset of data should be transferred. Multiple mailbox jobs can also be processed concurrently according to the configured environment and service conditions.

Microsoft 365 can apply service throttling during migration. EdbMails is designed to continue migration processing around service responses and retry conditions, while the service itself controls the applicable limits. Administrators planning larger batches should account for Microsoft service limits and monitor migration progress.

 See migration filter settings, parallel mailbox migration, and Exchange Online migration limits for detailed guidance.

5. Run incremental passes when required

A migration can be run again when new or changed source data needs to be transferred after the initial pass. Incremental processing helps administrators synchronize subsequent changes without treating the repeat run as a completely new migration.

 For the dedicated procedure and behavior, see Office 365 incremental migration.

6. Validate the migration result

After migration, review the migration status and reports, confirm that the intended source objects were mapped to the correct targets, and verify the migrated mailbox data required for the project. Any failed or skipped items should be reviewed before the migration is considered complete.

 Use the Office 365 mailbox migration validation guidance for post-migration checks.

Where to go for a specific Office 365 migration scenario

The workflow above explains how EdbMails processes a migration. Use the appropriate dedicated page when you need scenario-specific planning or instructions:

• Office 365 tenant-to-tenant migration - for migrations between Microsoft 365 tenants.
• Cross-tenant Office 365 migration - for cross-tenant planning and execution considerations.
• Office 365 migration with the same domain - for same-domain tenant migration planning.
• Multiple Office 365 mailbox migration - for bulk mailbox workloads.
• Shared mailbox migration - for shared mailbox workloads.
• Office 365 public folder migration - for public folder workloads.
• Office 365 to IMAP migration - for IMAP destinations.
• Office 365 to Exchange migration - for Exchange destinations.