PST to Exchange Migration FAQs

Download and install EdbMails, then select 'Start Your Free Trial'. Use the trial to validate PST scanning, Exchange connectivity, mailbox mapping, filters, and the migration workflow before purchasing a license.

EdbMails does not require a separate license key to be entered in the application. Sign in using the EdbMails account associated with the purchase; the purchased edition and migration entitlement are applied to that account.

Yes. EdbMails PST to Exchange Migration Tool can read supported PST data, preview mailbox items, connect to a supported on-premises Exchange environment, map the PST source to the intended target mailbox, and migrate selected data directly to Exchange.

Install EdbMails, select PST to Live Exchange, add and preview the PST, connect to the target Exchange Server using the connection method supported by that environment, map the source to the correct mailbox, start migration, and verify the migration log and target mailbox.

 View the complete PST to Exchange step-by-step guide.

No. The direct PST-to-Exchange migration path reads supported PST data directly and does not require Outlook to be installed.

Only when the selected EdbMails connection method and target on-premises Exchange version require impersonation. Do not treat impersonation as a universal prerequisite. Follow the connection option documented for your Exchange version and EdbMails build.

Use the instructions that match your Exchange Server version and connection method:

• Exchange Server 2007 and earlier

• Exchange Server 2010, 2013 and 2016 using cmdlet

• Exchange Server 2010, 2013 and 2016 using GUI

Because these are legacy Exchange versions, also review Microsoft's current support lifecycle before production use.

No. Microsoft's announced EWS retirement applies to Exchange Online. It does not by itself retire EWS in on-premises Exchange Server. Use the connection method supported by your target Exchange version and the EdbMails build you are running.

Check the Exchange server address and reachability, the selected connection method, credentials, required role or impersonation settings where applicable, SSL/TLS trust, mailbox access, server availability, and any firewall or proxy restrictions. If automatic mailbox discovery does not return the required targets, use the supported CSV mailbox-loading option.

After loading target mailboxes, review the mapping screen before migration. EdbMails can suggest matches when source and target identifiers align, and you can manually change the destination when the PST owner or filename does not match the intended mailbox.

Yes, when the target Public Folder hierarchy and required permissions are prepared and the selected Exchange connection workflow supports that destination. Review the mapping before migration.

Yes. Preview the PST, select only the required folders or mailbox items, and apply available filters such as date, sender, recipient, subject, attachment, or folder criteria where appropriate.

For supported re-runs from the same source/computer to the same target, EdbMails uses incremental migration tracking to avoid needlessly reprocessing items already recorded as migrated. Review the migration log after every re-run.

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.

No. Microsoft ended support for Exchange Server 2016 and Exchange Server 2019 in October 2025. Exchange Server Subscription Edition is Microsoft's currently supported on-premises Exchange release. EdbMails compatibility with a legacy Exchange version does not change Microsoft's support lifecycle.

Review the EdbMails migration log for folder and item status, then verify representative messages, attachments, contacts, calendars, folders, and item counts on the target Exchange mailbox. Keep the source PST until validation is complete.