PST to Office 365 Migration FAQs

Download and install EdbMails, then select 'Start Your Free Trial'. Use the trial to validate PST scanning, target connection, mapping, and the migration workflow before purchasing a license. The EdbMails trial allows up to 30 items per folder for evaluation.

EdbMails does not require a separate license key to be entered in the application. After purchase, sign in with the EdbMails account associated with the license. The available migration features and limits are applied to that account according to the purchased edition.

Yes. EdbMails can read supported PST files, preview mailbox data, connect to Microsoft 365, map source PST data to the required target mailbox, and migrate selected items directly to the target.

No. Outlook is not required for the direct PST-to-Microsoft-365 migration path. EdbMails reads the PST source and migrates supported data directly to the connected Microsoft 365 destination.

The workflow is: install EdbMails, select PST to Office 365, add the source PST, preview and select mailbox data, connect to Microsoft 365 with the current supported authentication method, map the source to the target mailbox, start migration, and verify the migration log and target mailbox.

 See the complete PST to Office 365 migration guide.

Use the current EdbMails modern-authentication workflow shown in the application. Older Exchange Online EWS impersonation instructions should not be treated as the current default connection method. Microsoft began globally disabling Exchange Web Services in October 2026 and plans full disablement by April 2027.

 See Microsoft's Exchange Online EWS deprecation guidance.

Confirm that you are using the current authentication method supported by your EdbMails version, that administrator consent and required Microsoft Entra app permissions are configured where applicable, that MFA or Conditional Access requirements are being satisfied, and that the connected account has access to the intended target mailboxes. If you use manual app registration, recheck the app ID, tenant configuration, permissions, and consent.

After connecting to Microsoft 365 and loading target mailboxes, review the mapping screen. EdbMails can suggest source-to-target matches where identifiers align, and you can manually change a target when the PST filename or source name does not match the destination mailbox.

Yes, when the shared mailbox exists and the connected account has the required access. Map the PST source to the corresponding shared mailbox before starting the migration and verify the destination after completion.

Yes, when Online Archive is enabled for the target user. Enable the archive first, map the required PST data to the archive destination, and verify the resulting folders after migration.

Yes. EdbMails supports adding multiple PST files to a bulk restore job and mapping each source to the correct target mailbox. See how to import multiple PST files to Office 365.

Yes. Preview the PST and select the required folders or items. Available migration filters can narrow the migration by criteria such as date, sender, recipient, subject, attachment, or folder selection.

For supported re-runs from the same source/computer to the same target, EdbMails uses incremental migration tracking to avoid reprocessing items already recorded as migrated. Review the migration log after each re-run, especially if mappings or source data changed.

EdbMails can scan damaged or inaccessible PST files and display mailbox data that remains recoverable. Validate the recoverable data before migration. Recovery depends on what is still present and readable in the source PST. For recovery-specific information, see the Outlook PST Recovery and Repair Tool.

Yes. Microsoft 365 enforces message-size and other service limits. Exchange Online documents a 150 MB migration message-size limit for supported plans, while tenant, mailbox, client, or other service limits can be lower. Review the migration log for skipped or failed oversized items.

 See Exchange Online limits.

Microsoft's organizational PST Import service supports bulk import through network upload to temporary Azure Storage and drive shipping. EdbMails provides an application-based workflow where you can preview PST data, apply filters, map PST sources to target mailboxes, and start migration from the application. Choose the method that fits your administrative, compliance, and migration-control requirements.

Review the EdbMails migration log for folder and item status, then sign in to the target Microsoft 365 mailbox and verify representative messages, attachments, contacts, calendars, folders, and other important data. Keep the source PST until validation is complete.