Understanding the Office 365 Migration program
EdbMails Office 365 Migration tool helps you migrate your organization’s mailboxes, public folders, shared mailboxes, and archive mailboxes. It automates tasks such as mailbox mapping and mailbox creation on target servers, thereby improving migration efficiency.
The application does not require any component installation on the target server. It passively accesses your source mailboxes using Microsoft APIs to read data and migrates items to the target mailboxes in a single transaction. For the migration to work, the mailboxes or public folders must already exist and be active on the target server. The user accounts used for migration should have the required roles and permissions, depending on whether they are connected to the source or target server.
Regarding data safety, the application does not delete or modify any content on the source server. It only reads the data passively and migrates it, ensuring complete security.
Types of data migrated using EdbMails Office 365 Migration
Mailboxes – No matter how many mailboxes you want to migrate, the application transfers them completely. It reads the selected source mailboxes and migrates their data to the target server. Every folder and item is moved to the corresponding folders on the target mailbox, preserving the original structure. Permissions (delegates) associated with the source mailboxes are also migrated.
Public Folders – The application replicates the source public folder structure and migrates all items to the target server. You must create public folders on the target server and assign the admin account in the application. During migration, connect to the target public folder with the assigned admin account to ensure all data is migrated. The tool migrates selected folders, their items, and associated permissions (delegates). Supported item types include emails, calendars, contacts, notes, tasks, journals, and more.
Different migration scenarios supported
- Office 365 tenant to tenant migration
- Office 365 to Office 365 migration
- Office 365 to Exchange 2007, 2010, 2013, 2016 and 2019 migration
- Office 365 Public folder to Exchange migration
- Office 365 Public folder to Shared mailbox migration
- Archive/export Office 365 tenant to Outlook PST
Incremental migration support
The application includes a built-in incremental migration feature. For subsequent migrations, it performs an incremental check and only migrates new items from the source server to the target server. If an item has already been migrated but is later modified on the source, the updated version will be migrated again to the target.
Migration of public folders to Office 365 and Exchange Online
To migrate public folders, create them on the target Office 365 environment. Assign the admin account Owner permissions on the root public folder and all its subfolders to enable migration.
Can I migrate data between servers with different display languages?
Yes. EdbMails Migration supports mailbox and public folder migration regardless of the display language on the source or target server. Standard Outlook folders such as Inbox, Drafts, Sent Items, Contacts, and Calendar are automatically mapped to their respective equivalents. For example, content from the “Boîte de réception” (Inbox) in French will migrate to the “Posteingang” (Inbox) in German.
Automatic mailbox creation
EdbMails can automatically map mailboxes if they already exist on the target server. If they do not exist, you can either manually create them on your Office 365 server or use the application to create new mailboxes directly on the target and map them automatically.
Support for Office 365 MFA (Multi-Factor Authentication)
EdbMails supports MFA for Office 365 login, adding an extra layer of security. Once MFA is enabled, every time you log in with your Office 365 password, you must verify your identity by providing a confirmation code received via text message, phone call, or the Microsoft Authenticator app.
