October 14, 2025 came and went. Windows 10 reached end of life. Office 2016 and Office 2019 hit the same wall the same day. For organizations that were already on Windows 11 and Microsoft 365, it was a non-event. But for the tens of millions of businesses that delayed the upgrade — or were in the middle of migrating when EOL hit — the aftermath is still very much a work in progress.
If your organization is in the middle of that migration right now, this post is for you. Not a warning about what's coming — that ship has sailed. This is a practical checklist for what to do with your legacy Office files when you're already on (or moving to) Windows 11 and things are already breaking.
Most EOL coverage focused on Windows 10. But October 14, 2025 was actually a triple EOL event:
Organizations running Windows 10 + Office 2016 or Office 2019 lost security update coverage across both their OS and their productivity suite simultaneously. If that's your situation, the migration pressure isn't just about features — it's about running unsupported software in an increasingly hostile threat environment.
The confusion a lot of teams face is this: the files worked perfectly on Windows 10 with Office 2016. The hardware is the same. The files haven't changed. So why do things break on Windows 11?
A few reasons:
Microsoft 365 installs the 64-bit version of Office by default on 64-bit Windows. Office 2016 installed 32-bit by default on most systems. VBA macros written for 32-bit Office — particularly those that call Windows API functions — will fail silently or crash on 64-bit Office without the PtrSafe attribute on their Declare statements.
This is the single most common reason IT teams get support tickets after upgrading: "the macro that has worked for 8 years just stopped working."
Windows 11 and Microsoft 365 apply stricter macro security and ActiveX controls policies by default. Controls that ran automatically on Office 2016 may now require explicit user trust, be blocked entirely, or fail to initialize when the file opens.
Opening a .xls file in Microsoft 365 on Windows 11 triggers Compatibility Mode. You lose access to dynamic arrays, XLOOKUP, LET, and other modern functions. The file works, but it's capped at Excel 2003 functionality. For users expecting full M365 features, this is frustrating — and invisible if they don't know to look for the "[Compatibility Mode]" notice in the title bar.
If your organization used Access 2016 Runtime to distribute Access applications, that runtime is now unsupported. Depending on how your files were built, they may require the exact runtime version they were compiled against. Access 2016 Runtime on Windows 11 can produce errors that weren't present on Windows 10.
LegacyLeaps scans your .xls and .mdb files and flags every compatibility issue — VBA API calls, ActiveX controls, format mismatches — before they bite you in production.
Run the Free ScanWork through these steps with your IT team. They're ordered by urgency — start at the top and work down.
.xls files across shared drives, OneDrive, and SharePoint.mdb and .accdb files in use.xlsm or open .xls files and check the VBA editor)Declare Function or Declare Sub without PtrSafe.xls files with no macros → .xlsx (safe to batch).xls files with macros → .xlsm using a tool that preserves VBA.mdb databases → .accdb (use the Database Compact and Repair tool first)Declare statements — add PtrSafe attributeThe most challenging legacy files are the ones that have been running quietly for years with no one clearly owning them. A payroll calculator written in 2009 by someone who left the company. An invoice template that "just works" until one day it doesn't. A contract register that an admin has been maintaining manually in Excel 2003 format because nobody ever told her to update it.
These files exist in every organization. They show up when you do the inventory phase and someone says "I didn't know that was still being used." They often have the most complex macros and the most fragile dependencies, because they were never designed to be maintained — they were designed to solve a problem once.
The approach for these is the same: scan first, fix what's broken, convert to modern format. But expect more surprises. Budget extra time for files that have no documentation and no original author.
Some files genuinely can't be automatically migrated. These typically fall into two categories:
Excel 4.0 macros (XLM), legacy DDE connections, or features removed entirely in modern Excel. These files need to be rebuilt from scratch or decommissioned. There's no converter that can resurrect Excel 4.0 macro logic.
Complex Access databases that use ActiveX automation to drive external applications (Word, Outlook, third-party software via COM) are fragile across major version upgrades. If the COM objects they depend on have changed or been removed, the automation breaks regardless of the database format.
For these cases, consider whether the underlying process can be rebuilt in a more modern stack — Power Automate, a lightweight web app, or a purpose-built SaaS tool. The file migration question becomes a business process modernization question.
For Access databases specifically heading toward a full rebuild, see our guide on migrating Access databases to web applications.
For organizations with hundreds of files to assess, manual triage isn't practical. LegacyLeaps is built for exactly this situation:
.xls or .mdb files and get a categorized report — which ones have macros, which have ActiveX controls, which have 32-bit API issuesThe free scan gives you the full inventory report at no cost. You only pay for conversions. For IT teams, that means you can scope the whole problem before committing to a budget.
For organizations with more than 20–30 complex files, our Done-For-You service has an IT team option where our specialists handle the audit, conversion, and validation — with a full report delivered to you at the end.
Download LegacyLeaps and scan your legacy files for free. No upload required — everything runs on your machine. See exactly what needs to be fixed before you convert a single file.
Download Free ScannerWindows 10 EOL didn't immediately break Office files. The issues surface during the upgrade: when organizations move to Windows 11 and Microsoft 365, .xls files open in Compatibility Mode, .mdb databases may fail if they depend on older Access Runtime versions, and VBA macros written for 32-bit Office fail on 64-bit Windows 11 machines.
Yes. Office 2016 and Office 2019 both ended extended support on October 14, 2025 — the same date as Windows 10. Organizations running Windows 10 + Office 2016/2019 faced a simultaneous triple EOL event. Microsoft no longer provides security patches for any of these products.
The most likely cause is a 32-bit to 64-bit compatibility issue. Windows 11 machines running 64-bit Microsoft 365 will reject VBA macros that use 32-bit Windows API declarations without the PtrSafe attribute. The fix requires updating the Declare statements in VBA. LegacyLeaps audits for this automatically during the scan.
You can install Office 2016 on Windows 11, but Microsoft won't provide security updates and some functionality may degrade over time. The bigger issue is that Office 2016 files stay in legacy formats that block Microsoft 365 features like Copilot, co-authoring, and Power Automate integrations. The recommended path is to move to Microsoft 365 and convert legacy file formats.
For organizations with under 100 files, 2–4 weeks is typical when using an automated tool. For larger environments (hundreds to thousands of files), budget 4–8 weeks for the full audit, conversion, and validation cycle. The inventory phase is usually faster than expected; the surprise is always the files nobody remembered existed.
Practical fixes for legacy Excel and Access problems. No spam.