Support for Office 2016 and Office 2019 ended on October 14, 2025. That date is behind you. So this isn’t a countdown post, and you’re not planning ahead for anything. Every copy of Word, Excel, and Outlook on that fleet has been running without a security fix since then, and it will keep doing that indefinitely, because Microsoft’s guidance for these versions lists two upgrade destinations and no paid extension program to buy your way out. Nothing broke. Nothing will announce itself. The apps open exactly as fast as they did in 2024.
We’re gmware, a software development firm headquartered in Austin, TX with engineering centers in Bangalore and Mohali, India. Desktop fleet moves land in our IT support and cloud migration work, so we’ve done the inventory-and-argue phase of this more than once. This post is deliberately narrow. Not the general case for Microsoft 365, but the specific decision facing someone on a perpetual license today: what actually stopped, what the three options really cost in supported years, and which machines should honestly stay put.
Where Office 2019 stands
What stopped on October 14, 2025
Three things, all of them invisible on the day. Microsoft no longer provides technical support for issues, bug fixes for issues that are discovered, or security fixes for vulnerabilities that are discovered. Its consumer-facing notice is blunter about what that means for you: you could expose yourself to serious and potentially harmful security risks and the performance and quality of the apps may degrade over time.
Read the middle item again, because people skip it. Bug fixes stopped too, not just security patches. A rendering glitch in a merged Excel range, an Outlook profile that corrupts on a particular Exchange configuration, a print bug in a specific driver combination: those are now permanent features of your environment. There is no escalation path and no hotfix coming. Support calls are gone as well, so the answer to “we opened a ticket” is that you can’t.
The security half compounds differently. A malicious document only needs someone to open an attachment they were expecting, which is why Microsoft’s own end-of-support notice warns of “serious and potentially harmful security risks” once the patches stop. Microsoft 365 Apps keeps getting hardened against that every month. Your Office 2019 install got its last hardening in October 2025 and now drifts further behind with each release the supported product ships.
The lifecycle math nobody checked before buying
This is where people get caught, and it’s why we’d push back on reflexively buying another perpetual license. Office 2019 did not get the lifespan Office 2016 got. Not close.
| Version | Released | Mainstream support ended | Support ended (or ends) |
|---|---|---|---|
| Office 2016 | Sep 22, 2015 | Oct 13, 2020 | Oct 14, 2025 |
| Office 2019 | Sep 24, 2018 | Oct 10, 2023 | Oct 14, 2025 |
| Office LTSC 2021 | Sep 16, 2021 | Oct 13, 2026 | Oct 13, 2026 |
| Office LTSC 2024 | Sep 18, 2024 | Oct 9, 2029 | Oct 9, 2029 |
Dates from Microsoft’s lifecycle records for Office 2016, Office 2019, Office LTSC 2021, and Office LTSC 2024.
Office 2016 shipped in September 2015 and was supported for a little over ten years. Office 2019 shipped three years later and was supported for seven, because Microsoft gave it a two-year extended phase instead of the five Office 2016 got. Both suites died on the same October day. If you bought Office 2019 to avoid a subscription, you paid a similar-shaped license fee for roughly 70% of the runway.
Supported years each version actually bought
Look at the bottom two bars before you price another one-time purchase. Neither LTSC release has an extended phase listed at all. Office LTSC 2021 runs out on October 13, 2026, which makes it a non-starter today. Office LTSC 2024 runs to October 9, 2029, and every month you spend deciding is a month off that number, because a perpetual license doesn’t reset the clock when you happen to buy it. That’s the honest frame for the “buy it once” instinct: you’re not buying forever, you’re buying whatever’s left of five years.
Three options, and what each one really is
There are only three moves. One of them is doing nothing, which counts.
| Option | Supported through | Fits | The catch |
|---|---|---|---|
| Microsoft 365 Apps | as long as you subscribe | most fleets, especially anything touching Exchange Online or Teams | recurring per-user bill; features shift monthly, so you inherit change management |
| Office LTSC 2024 | Oct 9, 2029 | the narrow set Microsoft scopes it for (below) | one device per license, volume agreement only, no new features, clock already running |
| Stay on Office 2019 | already ended | nothing, honestly | no patches, no bug fixes, no support, permanently, with no priced bridge available |
The two supported destinations come straight from Microsoft’s own planning guidance: Microsoft 365 Apps, the subscription version across desktop, web, and mobile, or Office LTSC 2024, sold as a one-time purchase through a volume license agreement, one device per license. The licensing difference matters more than the price difference for most teams. Microsoft 365 Apps licenses a person, so the same user covers a Windows laptop, a Mac, and a phone. LTSC licenses a box.
Row three deserves a straight answer rather than a scolding. Sometimes staying is a defensible call for a defined window: a machine already scheduled for replacement, a plant PC being retired in the same capital cycle. What makes it indefensible is doing it by default, across the whole fleet, because nobody scheduled the conversation. If you want the dollars side of the subscription move rather than the lifecycle side, we costed that separately in our Microsoft 365 migration breakdown. Not sure which bucket your fleet is in? Reach out with a rough device count.
Who should actually stay on a perpetual license
We’d rather point at Microsoft’s own scoping than invent our own, because theirs is unusually specific. Office LTSC 2024 is designed for specific scenarios. These include regulated devices that can’t accept feature updates, process control devices on manufacturing floors, and specialty systems that can’t connect to the internet.
That’s a real list, and if you’re reading it thinking “that’s us,” you’re probably right. A validated workstation in a GxP environment where any feature change triggers requalification paperwork. A line-side PC on a manufacturing floor with no route to the internet and a change-control process measured in quarters. A test-bench machine whose Excel template feeds a signed report. On those, monthly feature updates are the risk, not the benefit, and LTSC is the correct buy.
Here’s an opinion we’ll defend, though. Most organizations reaching for LTSC aren’t in that list. They’re reaching for it because a one-time purchase feels safer than a subscription line item, which is a finance preference wearing an IT costume. If your users are already on Exchange Online, already in Teams, already syncing to OneDrive, the LTSC path adds a device-licensing constraint and a 2029 expiry to a fleet that’s cloud-attached anyway. Pick LTSC for the machines that match Microsoft’s description. Don’t pick it for the whole estate because the invoice shape is more comfortable.
The upgrade that doesn’t need a reimage
Good news for anyone dreading a fleet-wide rebuild: Microsoft documents an in-place path from Office 2019 to Microsoft 365 Apps that doesn’t require deploying a separate installation package. You enable the Group Policy setting Upgrade Office 2019 to Microsoft 365 Apps for enterprise under Computer Configuration\Administrative Templates\Microsoft Office 2016 (Machine)\Updates, which sets the VLtoSubscription registry value, and you specify the update channel alongside it. The existing install converts itself.
Two operational notes from Microsoft’s own text, both of which catch people. The upgrade process could take several days to complete as it depends on Office’s update checks, so don’t schedule a Friday cutover and expect a Monday report. And users could be prompted with a “Your Privacy Matters” dialog they have to accept for the upgrade to finish. That’s the kind of thing that leaves a chunk of your rollout half-done until someone walks the floor.
For estates that need more control, the Office Deployment Tool route works with a RemoveMSI element that strips old MSI-based Office during install, and the Microsoft Support and Recovery Assistant can automate uninstalling older Office versions ahead of time. Either way, old versions come off before the new one goes on.
What breaks, and what rides along
Microsoft names three compatibility categories worth testing before you deploy: business-critical Visual Basic for Applications (VBA) macros, non-Microsoft add-ins, and complex documents and spreadsheets. In our experience the ranking is right but the pain is concentrated in the first one. The Excel workbook that runs quarterly close, written in 2013 by someone who left in 2017, is the single most common thing that stalls an Office migration. There’s tooling: the Microsoft 365 Apps Upgrade Readiness Toolkit assesses compatibility, and the App Assure program will help fix what breaks.
When a macro is genuinely beyond patching, the upgrade quietly turns into a small rewrite project, and that’s a different budget conversation than a license swap. We wrote up the rebuild-versus-refactor decision in our legacy modernization cost guide, and it applies to a 4,000-line VBA workbook more often than anyone wants it to.
Don’t forget the ride-alongs either. Desktop Project and Visio share the same end of support dates as the Office suites for those versions, so Visio 2016 ended on October 14, 2025 too, and the current volume-licensed replacements are Project 2024 and Visio LTSC 2024. If your Office 2019 machines also carry an unsupported Windows Server on the back end, the sequencing matters, and our Windows Server 2016 migration plan covers that side of the estate.
If you genuinely can’t move this quarter
Sometimes the answer is “not yet,” and pretending otherwise doesn’t help. Four things worth doing in the meantime, none of which restore a patch supply:
- Count the machines first. Which devices, which build, which apps, which users. You can’t risk-rank what you haven’t counted, and any migration quote you get without that number is fiction.
- Move the regulated and internet-facing users to the front of the queue. Anyone touching client data, payment data, or health data on an unpatched Office install goes in wave one. The rest can wait a quarter.
- Harden around the app rather than in it. Attachment filtering at the mail gateway, macro execution blocked by policy for anything unsigned, endpoint detection that actually reports. This narrows the blast radius. It doesn’t close the hole.
- Put a date on the calendar with a name beside it. Unsupported software drifts because it belongs to nobody.
If you’re carrying an unsupported fleet because there’s no one in-house to own the move, that’s a staffing answer more than a licensing one, and we broke down what that costs in the managed IT services pricing piece.
How gmware handles an Office estate move
We start with the inventory, and we won’t quote before it exists. Device count, Office build per machine, macro and add-in dependencies, which users touch regulated data, and which machines legitimately match Microsoft’s LTSC description. That last column is the one that changes the recommendation, and it’s the column most quotes skip. An Austin-side lead owns the plan and the wave sequencing; engineers in Bangalore and Mohali build the deployment configs, grind the macro and add-in compatibility passes, and run the pilot ring, with enough US-hours overlap that your cutover mornings happen while your team is awake.
We also run production systems ourselves through Shield Suite, our retail-intelligence platform covering more than 60,000 beverage-alcohol storefronts, so “test the rollback before you need it” is a habit rather than a slide.
And we’ll tell you when not to hire us. If you’re a 12-person shop with no custom macros and no compliance scope, this is a licensing purchase plus an afternoon, and you should do it yourself rather than pay anyone to project-manage it. The engagement earns its keep at fifty-plus seats, or wherever VBA and add-ins have grown into the workflow far enough that the compatibility pass is the actual work.
Tell us what you’re running: device count, Office versions, whether macros or add-ins are in the critical path, and any compliance scope. Reach out and we’ll come back within 48 hours with a wave plan, a cost range, and a straight opinion on which machines should move and which should stay.