Exchange EDB to Office 365 migration FAQs

Download EdbMails and install it, then launch the application and select Start Your Free Trial on the sign-in screen. Open an offline Exchange EDB file, choose the mailboxes you want to test, connect to Microsoft 365, and verify the result. The trial can migrate up to 30 items from each folder, so you can check mailbox mapping and the destination data before purchasing. See the EDB to Office 365 migration guide.

EdbMails does not send a separate activation key. After purchasing the appropriate EDB migration edition, sign in to the application with the same registered email address and password used for the purchase. Your account provides access to the licensed features. If the application was already open, close and reopen it, then sign in again. Review the EdbMails pricing options if you need to confirm your license edition.

Yes. EdbMails reads an offline Exchange EDB file and migrates recovered mailbox data directly to Microsoft 365 without creating an intermediate PST file. You can select emails, attachments, contacts, calendars, tasks, and other mailbox items available in the source database. Preview the recovered content before migration, and verify representative folders and items in the destination after completion. Learn more about EDB to Office 365 migration features.

Open EdbMails and select EDB Recovery (Offline) and Migration, followed by EDB to Office 365. Browse to the offline EDB file, preview its mailboxes, and select the data to migrate. Connect to Microsoft 365 using modern authentication, map each source mailbox to its intended destination, and click Start Migration. Review the report and destination mailbox after the transfer. Follow the EDB to Microsoft 365 step-by-step guide for the application screens.

Confirm that the computer running EdbMails can reach Microsoft's sign-in and Microsoft 365 services over HTTPS. If the connection fails, check the selected tenant, administrator permissions, MFA or Conditional Access requirements, and Microsoft Entra application registration and consent. Retry the destination connection after correcting the identified issue. See the modern authentication troubleshooting guide for further checks.

If a source EDB mailbox uses localized system folder names, such as Boîte de réception for Inbox, check the destination mailbox language settings and review the source-to-target folder mapping before migration. A language mismatch can affect where standard folders appear. If necessary, update the destination regional settings and verify the mapping again. Follow the Microsoft 365 mailbox language settings guide.

On the EdbMails destination connection screen, choose Auto Registration or Manual Registration. Auto Registration uses the appropriate administrator permissions to register the application and obtain consent. For Manual Registration, configure the EdbMails application and required permissions in Microsoft Entra ID before connecting. Complete the Microsoft sign-in and confirm that the destination mailboxes load. See the Connect to target Office 365 guide.

EdbMails provides automatic mailbox matching and lets you change mappings manually. On the Mailbox Mapping screen, review each source EDB mailbox and select the intended Microsoft 365 destination, even when the source and target email addresses differ. You can also reuse mappings from a previous migration where available. Confirm every pairing before starting. See the EDB to Office 365 migration steps for the complete workflow.

An HTTP 407 response means a proxy server between EdbMails and Microsoft 365 is asking for authentication. Ask your network administrator to check the proxy address, authentication method, required credentials, and whether Microsoft 365 endpoints are allowed through the firewall. A 407 response does not, by itself, indicate a DNS problem. Review the EdbMails system and network requirements.

Not necessarily. You can create the target mailboxes manually or use the EdbMails option to create and map new mailboxes in Microsoft 365. If a destination mailbox already exists, EdbMails can map it automatically or let you select it manually. Newly created mailboxes must be properly provisioned and licensed before their data can be migrated; allow time for mailbox provisioning when required. See the Microsoft 365 mailbox creation and mapping guide.

No. EdbMails uses Microsoft 365 modern authentication and the application permissions required for its current destination connection workflow. Administrators do not need to configure the retired Exchange Online ApplicationImpersonation role for this connection. Select Auto Registration or Manual Registration and grant the documented permissions. See modern authentication in Office 365.

Yes. Select multiple mailboxes from the offline EDB file and map each source mailbox to a separate Microsoft 365 destination on the Mailbox Mapping screen. Review the source-to-target assignments before clicking Start Migration. EdbMails processes the selected mailboxes within the migration job without combining them into a single target mailbox. See the EDB to Office 365 migration guide.

Yes. EdbMails uses locally retained migration metadata to identify items already processed during repeat migration runs. Use the same computer and keep the source EDB selection and destination mailbox mapping consistent. If the source EDB has additional eligible content, a subsequent pass can process it without repeating the entire transfer. An unchanged offline EDB copy will not receive new live-server emails. Review the EdbMails incremental migration guidance.

After migration, open the EdbMails report and review the item counts and operation status for each selected mailbox. Sign in to Microsoft 365 to check representative email folders, messages, attachments, contacts, and calendar entries. Also confirm that every source mailbox was mapped to the intended destination. If the review identifies a problem, check the relevant settings before running another pass. See the EDB to Office 365 migration guide.

Yes. EdbMails opens offline EDB files and migrates recovered mailbox data directly to Microsoft 365 without a working original Exchange Server, Active Directory connection, or Microsoft Outlook installation. Install EdbMails on a Windows computer, browse to the EDB, connect to the target tenant, and map the mailboxes. Outlook is required for EDB to PST export, not for direct EDB to Office 365 migration. See the EDB recovery system requirements.

Yes. EdbMails scans offline EDB files affected by corruption, damage, dismounting, or Dirty Shutdown and can migrate the recovered mailbox data directly to Microsoft 365. Preview the available items, select the required mailboxes, and map them to the target tenant. The amount of data recovered depends on the condition of the source EDB. This extracts mailbox content; it does not repair the original database into a mountable state. See the Exchange Dirty Shutdown recovery guide.

EdbMails supports offline EDB databases from Exchange Server 2003, 2007, 2010, 2013, 2016, and 2019 for direct migration to Microsoft 365. The original server does not need to be running. Open the EDB, preview the available mailboxes, and map the selected data to Microsoft 365. For older Exchange databases, review the source files and migration prerequisites before starting. See the EDB to Office 365 Migration Tool.

Yes. EdbMails lets you select individual mailboxes and folders from the offline EDB rather than migrating everything. You can also apply Include and Exclude filters using criteria such as date range, sender, recipient, subject, and attachment details. For example, select a department's mailboxes and migrate messages within a required date range. Review the filter settings before starting. See the EDB filter settings guide.

Yes. EdbMails offers workflows to migrate recovered archive mailbox data, shared mailbox content, and Exchange public folders from an offline EDB to Microsoft 365. Prepare the appropriate target mailbox, online archive, or public folder destination and verify the required permissions and mapping before migration. See the EDB archive mailbox migration guide and EDB public folder migration guide.

For direct EDB to Microsoft 365 migration, choose the EdbMails EDB Recovery and Migration Corporate Premium or Technical Edition. The Personal Edition covers EDB to PST export, but not direct EDB to Office 365 migration. Choose the edition based on the intended usage and migration scope. Destination Microsoft 365 licenses are separate. See the EdbMails pricing and license editions.

An email larger than the effective Microsoft 365 destination message-size limit may not transfer. Exchange Online commonly has a default receive limit of 36 MB, and administrators can configure higher limits within Microsoft's supported settings, up to 150 MB where applicable. The effective migration limit may also depend on the chosen transfer method. Check mailbox settings and review the EdbMails migration report when large attachments are involved. See the Office 365 message-size limits guide.

EdbMails migrates recovered mailbox items while retaining their folder hierarchy, email attachments, and available message properties such as sender, recipients, subject, and timestamps. It also supports contacts, calendars, tasks, and other Exchange mailbox data. The result depends on the information present in the offline EDB and destination capabilities. After migration, compare representative items in Microsoft 365 with the source EDB preview. See the EDB to Office 365 migration features.