EDB Archive Mailbox to Office 365 Migration FAQs

Yes. EdbMails scans and recovers an offline Exchange EDB file, identifies archive mailbox content and supports direct migration to a prepared Microsoft 365 archive mailbox. This avoids using an intermediate PST for the supported archive workflow. Follow the EDB archive mailbox migration guide.

No. The offline EDB recovery workflow reads the source database without requiring it to be mounted on its former Exchange Server. Keep a preserved copy of the EDB and preview the recoverable archive data before starting the destination connection.

Create or identify the intended destination user mailbox, assign the appropriate Microsoft 365 license and enable its Online Archive. Check that the archive is provisioned and has enough capacity. Confirm modern-authentication permissions before mapping source archive items.

In the Exchange admin center, select the licensed user mailbox and enable archiving according to the current Exchange Online administration interface. Wait until the archive is provisioned, then confirm it appears as the intended archive destination before migration.

You can select the available archive content in the offline EDB and migrate it through the archive workflow independently of unnecessary primary-mailbox content. Ensure the destination Online Archive is enabled and map it to the corresponding source archive rather than the primary mailbox.

After scanning the EDB and connecting to Microsoft 365, review each source archive and its target mailbox assignment in EdbMails. Use the appropriate destination archive mapping, especially when source and target email addresses differ. Verify the mapping before selecting Start Migration.

Yes. Select the recovered archive folders you need and use supported include/exclude filters to limit mailbox items by date or other available conditions. Test the filters on one archive first so required messages are not unintentionally excluded.

EdbMails can scan a damaged or dismounted EDB and migrate archive items it is able to recover. Preview the detected folders before migration; badly damaged or missing source content cannot be guaranteed. EdbMails extracts mailbox data rather than repairing the source EDB database in place.

Check the destination license, provisioned archive capacity and any eligible auto-expanding archive configuration before starting. If the target does not have enough space, address that limitation before a large migration. Test with a representative archive and monitor the destination usage.

EdbMails supports incremental behavior in eligible migration workflows. For repeat passes, retain the same migration computer and source-to-target mapping so locally stored migration metadata remains available. Review the outcome rather than assuming every previously migrated item will be ignored in all scenarios.

The EdbMails free trial allows testing with up to 30 items per folder for supported archive migration workflows. Preview and validate a representative destination archive before purchasing the required license. Review the EdbMails migration guide.

Review the EdbMails migration report, then open the destination Online Archive and check representative folders, messages, attachments and dates. Confirm that the data went into the archive instead of the primary mailbox, and investigate any discrepancy before retiring the source. See the related archive migration guidance.