Exchange EDB Guides

Exchange 2019 End of Support What to keep from old mailbox databases as Exchange 2016 and 2019 patching ends

Leena Taylor Paul By Updated October 21, 2026 8 min read

Exchange 2016 end of support arrived on October 14, 2025. Paid security updates stop when October 2026 ends.

Export the mailboxes you must keep to PST or PDF files. Store dismounted copies of your .edb files with their logs. Do both while your server still answers.

Support ended October 14, 2025
Paid patches end October 2026
Mail to keep PST or PDF + .edb copy

Exchange 2019 end of support and Exchange 2016 end of support fell on the same day. Microsoft then sold paid Extended Security Updates (ESU) for six months and added six more. Those updates stop when October 2026 ends.

If you moved users to Exchange Online or Exchange Server Subscription Edition (Exchange SE), your old server still stores their past mail. Auditors and lawyers can ask for a mailbox from 2019 long after the move.

Here is what to do with old Exchange databases before you switch the server off, from mailbox exports to cold copies.

What Happened at Exchange 2016 End of Support?

Exchange 2016 end of support and Exchange 2019 end of support both fell on October 14, 2025. Microsoft lists the end of extended support in October 2025 under Exchange Server 2016 and Exchange Server 2019.

ESU coverage came in two periods of six months. Period 2 exists for customers who need extra time to migrate to Exchange SE, per Announcing Period 2 Exchange 2016/2019 Extended Security Update (ESU) program.

Period 2 ends in October 2026, according to Reminder: Exchange 2016 and 2019 ESU Program Ends in October 2026. Microsoft says no updates follow after that, even for Period 2 customers. October 2026 updates are already out for ESU customers, per Released: October 2026 Exchange Server Security Updates.

Version Status in October 2026 Way forward
Exchange 2016 Out of support, paid ESU ends Legacy upgrade to Exchange SE or move to Exchange Online
Exchange 2019 Out of support, paid ESU ends In-place upgrade from CU14 or CU15 to Exchange SE or move to Exchange Online
Exchange SE In support since July 1, 2025 Stay here as your live server
Exchange 2013 and older Out of support, 2013 since April 2023 Export data and retire server

Your server does not stop working in October 2026. Security fixes stop, so new flaws stay open on that machine. Exchange SE stays in support, per Exchange Server Subscription Edition.

What are Your Options for Old Mailbox Data?

Exchange 2016 end of support leaves three options for old mailbox data. Most teams use two of them.

  1. Leave the server online. Mail stays searchable in Outlook and the admin center. Cut the server off from the internet and from user networks if you choose this path.
  2. Export chosen mailboxes. Create one PST per mailbox for people who come back and PDF files for records you only need to view. Files from this step open without an Exchange server.
  3. Store a cold copy of the databases. Copy the .edb files with their log folders to protected storage. Cold copies cost disk space and cover the mailbox nobody thought to export.

Options 2 and 3 work best together. Exports cover the mailboxes you know about. Cold copies cover questions nobody can predict yet, like a legal request three years from now.

Univik covers both file formats in How to Convert EDB to PST and Export Exchange Mailbox to PDF.

“Export what people already ask for, then keep the database copy for the questions nobody has asked yet. That second part costs almost nothing.”

Nick Rogers, Founder of Univik

Why is a Cold .edb Copy Hard to Open Later?

Exchange opens a cold .edb copy through two paths. Both have strict limits.

Recovery databases take Exchange 2016 and later databases only. Microsoft says the target mailbox must sit in the same Active Directory forest as that database, per Recovery databases in Exchange Server.

Database portability has tighter limits. Microsoft says source and target must share one Exchange version and one Windows Server version. Databases created in older Exchange releases cannot move to Exchange 2016 or 2019 either, per Move a mailbox database using database portability in Exchange Server.

Point Recovery database Database portability Univik Software
Exchange versions 2016 and later only Same version on source and target 2000 to 2019
Server needed Mailbox server with target mailbox in same forest Mailbox server in same organization None, only a Windows workstation
Mail leaves as Restore or export request Mailboxes in place, users connect PST, MSG, EML, MBOX, PDF, HTML, CSV index or upload

Cold copies need a plan for the day your last server and forest are gone. Univik Software opens the .edb offline and leaves the source file unmodified. Exchange Recovery Database lists the recovery database limits in full.

What Should You Check Before You Switch the Server Off?

After Exchange 2016 end of support, seven checks protect your data while the server can still answer questions.

  1. List databases and paths with Get-MailboxDatabase and Format-List Name,EdbFilePath,LogFolderPath.
  2. Save a mailbox list with Get-Mailbox -ResultSize Unlimited | Select-Object DisplayName,PrimarySmtpAddress,Database | Export-Csv mailboxes.csv.
  3. Look for disconnected mailboxes of people who left. Microsoft says a disconnected mailbox is purged after the MailboxRetention period, 30 days by default, per Disable or delete a mailbox in Exchange Server.
  4. Dismount the databases with Dismount-Database before you copy files.
  5. Copy the .edb files and full log folders to protected storage.
  6. Confirm Clean Shutdown on the copy with eseutil /mh. Exchange 2007 documentation from Microsoft says a database shut down correctly has detached from its log files, per Reference for Common Eseutil Errors.
  7. Note the Exchange version and cumulative update. Old databases are easier to support when you know both.

Dismount first. Databases in dirty shutdown stay attached to their logs and need them applied before they start. Exchange Database Dirty Shutdown explains that state.

How do You Export Old Exchange Mailboxes Without the Server?

Open the copied .edb offline and export what you need. When ESU patches stop, you export your copied 2016 or 2019 database to PST with Exchange EDB Converter from Univik. Windows 11 or 10 desktops need no Exchange or Outlook install.

While your server stays online, the New-MailboxExportRequest cmdlet exports to PST too. New-MailboxExportRequest Guide explains the Mailbox Import Export role and network share it needs.

1
Copy the database
Move the dismounted .edb with its log folder to a workstation with Windows 11 or 10. Reserve 256 MB more than the database size in your working folder, since Univik Software copies dirty or locked databases first.
2
Open it offline
Start the trial app and select Open an EDB file. Dragging the .edb onto the window works too. Use the log folder option if E00*.log files sit elsewhere.
3
Choose mailboxes and format
Click Export and choose Everything or one account. Select PST for people who come back or PDF for records.
4
Export and save the report
Choose a destination and click Start Export. Select Save report as for a copy of the export report next to the files.
Export step 3 with destination folder, file naming and PST split
In the app. Step 3 of the export sets the destination folder and names PST files after their mailboxes. Large PST output splits at a size you choose.
Key Takeaways
  • Exchange 2016 end of support and Exchange 2019 end of support both fell on October 14, 2025.
  • Paid ESU patches stop when October 2026 ends, so an online archive server grows riskier.
  • Exchange 2019 upgrades in place to Exchange SE from CU14 or CU15. Exchange 2016 needs a legacy upgrade.
  • Export known mailboxes and store cold copies of your .edb files with their logs.
  • Recovery databases accept Exchange 2016 or later databases with target mailboxes in the same forest, so plan how you open cold copies.
  • Dismount before you copy and confirm Clean Shutdown with eseutil /mh.
Open Your Old Exchange Database Offline

Test an export in Univik Software from a duplicate of your database before the server goes off. Trial edition saves 10 messages per folder. Licences start at $99 for 2 PCs.

Free Download See all features

Questions About Exchange 2016 and 2019 Retirement

Does Exchange 2016 end of support stop the server from working?

No. Your server keeps serving mail and stops receiving security updates. Exchange 2019 behaves the same way after October 2026, so new flaws stay open on that machine.

Can I upgrade Exchange 2019 to Exchange SE in place?

Yes, from Exchange 2019 CU14 or CU15. Microsoft says Exchange SE RTM is code equivalent to Exchange 2019 CU15 apart from licensing, product name and build number, per What's new in Exchange Server SE.

Can I upgrade Exchange 2016 straight to Exchange SE?

No for an in-place upgrade. Microsoft says in-place upgrades from versions earlier than Exchange 2019 are not supported, per What's new in Exchange Server SE. Legacy upgrades to Exchange SE work and mean new servers with moved mailboxes.

Can I upload old .edb mail to Exchange Online?

Yes. Univik Software uploads mailboxes from an offline .edb to Office 365. Import EDB to Office 365 lists the steps.

How long should I keep old Exchange databases?

Retention depends on your legal and industry rules, not on Exchange. Ask whoever owns records policy in your company. Keep the cold copy as long as the longest rule that applies.

Is a PST file a good archive for old mail?

Yes for mail people reopen in Outlook. Univik Software splits PST output at a size you set with 50 GB as the default. Store two copies and export PDF for records people only need to view.

Do I need log files if I dismounted the database?

No for a database in Clean Shutdown. Exchange 2007 documentation from Microsoft says a database shut down correctly has detached from its log files, per Reference for Common Eseutil Errors. Copy the logs anyway, because a database in dirty shutdown needs them applied before it starts.

Can I open an old .edb after the Active Directory forest is gone?

No, not with Exchange. Recovery databases need the target mailbox in the same Active Directory forest, per Recovery databases in Exchange Server. Univik Software opens a retired 2016 or 2019 database file on a plain Windows desktop with no Exchange or Outlook installed.

Leena Taylor Paul

Leena Taylor Paul covers Exchange server retirement for the Univik team, which has shipped Windows mail tools since 2013. Last checked October 2026. Contact our support team if an old Exchange database will not open.

More Exchange EDB Guides

All Univik guides for Exchange mailbox databases, grouped by what you need to do next.