Office 2016 End of Life: What Happens to Your Files

Microsoft ended extended support for Office 2016 in October 2025. If your organization is still running Office 2016 — or still has files created with it in legacy formats — the clock has been ticking. Here's exactly what end of life means, what doesn't change immediately, and what you need to do about your legacy .xls and .mdb files before compatibility deteriorates further.

What "End of Life" Actually Means for Office 2016

Microsoft's support lifecycle for Office products has two phases: mainstream support and extended support. Mainstream support for Office 2016 ended in October 2020. Extended support — which covered security patches and critical bug fixes — ended in October 2025.

After extended support ends:

• No more security patches. Vulnerabilities discovered after October 2025 will not be fixed.
• No more bug fixes. Existing issues remain unresolved.
• No more technical support from Microsoft.
• Microsoft 365-connected features (OneDrive sync, Teams integration, live collaboration) have already been degraded or removed.

Your Files Don't Disappear — But Their Usability Does

Here's what often confuses people: end of life doesn't make your files inaccessible overnight. An .xls file you created in 2018 will still exist after Office 2016 goes end of life. The issue is what happens when you or your colleagues try to open those files on updated systems.

The Office Version Compatibility Problem

As organizations upgrade from Office 2016 to Microsoft 365 (Office 365), they encounter a chain of compatibility issues:

• .xls files open in "compatibility mode" — a degraded state where certain features are disabled
• VBA macros may be blocked by updated security settings in newer Office versions
• ActiveX controls created with older tooling may fail to initialize
• 32-bit VBA code often fails in Office 365 without PtrSafe declarations
• Some .xls files won't open at all in Excel 365 if they use features Microsoft removed

The Windows 11 Compounding Factor

Windows 11 adds another layer of complexity. Microsoft deprecated several legacy runtime components in Windows 11 that older Office files depended on. This means even if you have a newer version of Office, files created with Office 2016-era tooling may fail due to OS-level changes. The Windows 11 24H2 update in particular broke many Excel 2016-format files that had been opening without issue.

The Timeline: From Office 2003 to Office 365

If your organization upgraded from Office 2016 or earlier, every file that was saved in .xls or .mdb format during that time is now a migration candidate.

What You Need to Migrate Before It's Too Late

The migration priority depends on what your files contain. Not all .xls files are equal.

Migrate Immediately

• Any .xls workbook with VBA macros your team depends on
• Any .mdb Access database in active use
• Any .xls file with ActiveX controls (buttons, combo boxes, custom forms)
• Any file opened by multiple people across different Windows or Office versions

Migrate Soon

• Archive .xls files you occasionally reference but don't actively edit
• .xls files with complex formulas that use removed or deprecated functions
• Any file that's been displaying the "compatibility mode" banner in newer Excel

Lower Priority

• Pure-data .xls files with no macros or ActiveX (though still worth converting for consistency)
• .xls files that are true archives and will never be opened again

The Migration Approach That Works

The naive approach — opening .xls in Excel 365 and saving as .xlsx — works for simple files. It fails consistently for files with VBA code, because Excel 365 will either strip the code or save it in .xlsm format without properly updating 32/64-bit API declarations.

The right process for macro-enabled files:

1. Audit first. Know what's in each file before you convert. Surprises are expensive.
2. Audit VBA for deprecated APIs. Any Declare statement using the old 32-bit calling convention will need PtrSafe added for 64-bit Office.
3. Convert with a tool that understands VBA. LegacyLeaps handles the PtrSafe migration automatically and preserves all module code.
4. Validate after conversion. Open the converted file, run any macros, and verify all data and functionality is intact.

What Happens If You Do Nothing

The temptation is to wait. The files still open (mostly), the team knows how to work around the issues, and migration feels risky. But inaction compounds the problem:

• Each Windows or Office update is another opportunity for more files to break
• New team members on modern machines can't open files the legacy team takes for granted
• Compliance audits increasingly flag unpatched, end-of-life software as a risk
• The person who knows how the VBA works eventually leaves

The worst migrations we see are emergency migrations — triggered by a critical file suddenly failing, with no time to do it properly. Planned migration preserves more, costs less, and takes less time.

For a complete guide to the migration process, see the Complete Guide to Legacy Excel Migration and the Windows Upgrade Survival Guide for Office Files.

← Back to all posts