After Office 2016/2019: Microsoft 365 or a Perpetual Licence?

TL;DR: For out-of-support Office 2016/2019 there are two exits: a Microsoft 365 subscription (always current, cloud services included) or perpetual Office 2024 (one payment, fixed version). For most offices the honest answer is a mix of both — and the mix is decided by user profiles, not by a single company-wide preference.
October 2025 retired more than Windows 10: Office 2016 and Office 2019 stopped receiving security updates on the same calendar day. Word still opens and Excel still calculates — but an unpatched application that processes documents arriving by email leaves ajar exactly the door attackers love most; office documents are the classic carrier of malware. This article settles the "which Office do we buy" question across the two models.
Two Models, Two Philosophies
Microsoft 365 is a per-user subscription: the Office applications stay permanently current, and the package includes corporate email (Exchange Online), Teams and OneDrive/SharePoint cloud services. A perpetual licence (the Office 2024 family) is a one-time purchase: the version is fixed, no cloud services are included, and security updates run to a set date — after which today's 2016/2019 situation repeats. The real choice is this: does the business want to manage its software as a service, or as an asset?
The Decision Table
| Dimension | Microsoft 365 | Perpetual (Office 2024) |
|---|---|---|
| Payment character | Ongoing per-user subscription | One-off fee per device |
| Currency | Continuous features + security | Security only; features frozen |
| Support horizon | As long as the subscription runs | Bound to the version calendar — same decision returns at the end |
| Corporate email | Included (plan-dependent) | Not included — solved separately |
| Collaboration (Teams, co-authoring) | Native | Limited |
| Multiple devices per user | Install rights on several devices | Licence tied to the device |
| Internet dependency | Needed for setup and validation; work can continue offline | Low |
Comparing Costs Honestly
The classic accounting mistake is comparing the perpetual licence's one-off price against a single year of subscription. A sound comparison runs over a 4–5 year window with package contents equalised: on the Microsoft 365 side, email hosting, cloud storage and Teams are inside the fee; on the perpetual side those items are bought separately or ignored. For a business already hosting its email on Microsoft 365, the perpetual licence's "cheapness" is usually optical; for an estate that uses no cloud services and processes documents locally, perpetual can be genuinely economical.
Most Offices' Real Answer: the Mixed Model
User profiles are not uniform, so a single licence type is usually either a gap or a waste. The arrangement we build most often in the field:
- Heavy office users (accounting, sales, management): Microsoft 365 — email, multiple devices and collaboration already make the subscription unavoidable.
- Light-use stations (warehouse terminal, production kiosk, shared shift PC): perpetual licence — pushing a subscription onto a machine that opens and prints documents and has no mailbox is waste.
- View-only seats: free web versions or shared solutions may suffice; not every chair needs the full suite.
The precondition of the mixed model is knowing who actually uses what — the same usage-inventory discipline that governs SaaS subscription management in general.
What Not to Skip in the Transition
- Add-ins and macros: accounting integrations, e-declaration add-ins and years of accumulated Excel macros must be tested on a pilot before the waves; surprises do not belong to production day.
- Legacy file formats: very old archive documents can behave differently on opening; sample-test the critical archive.
- The mixed-version period: while migration proceeds in waves, different versions will touch the same documents; watch shared template compatibility through this window.
- Recording the old licences: which licence remains on which device goes into the inventory — the cost of answering "we don't know" on audit day is well documented.
Yamanlar Bilişim's Contribution to the Licence Decision
Our role in this decision is tailoring, not selling: we profile your users, measure your current email and cloud usage, and put the two models' costs side by side over a 4–5 year window for your specific case. Transition day — add-in tests, data moves, installations — is scheduled outside working hours, and the licence inventory stays current under the maintenance agreement.
FAQ
Frequently Asked Questions
What happens if we keep using Office 2016/2019?
The applications keep working but receive no security patches; exposure to document-based attacks grows over time, and incompatibilities with newer file features and cloud services accumulate. A short planning period is reasonable; indefinite continuation is a risky choice.
If we move to Microsoft 365, do we lose our old documents and templates?
No; documents stay in place and open in the new applications. The area that needs attention is not documents but automation: macros, add-ins and integrations must be verified in the pilot.
Can we not work with Microsoft 365 when the internet is down?
The desktop applications work offline; documents open and edit locally. The internet is needed for setup, licence validation and cloud sync. Cloud services like email naturally require connectivity — which is a line-redundancy question, not a licensing one.
We bought perpetual licences; is the same decision really coming back in a few years?
Yes — that is the nature of perpetual licensing: when the version calendar runs out, today's decision returns. Choosing it knowingly is fine; the problem is treating the end date as "never" instead of writing it into the calendar.
Doesn't the mixed model complicate licence management?
Not if the inventory is kept: which user is on subscription, which device on perpetual — one table. Complexity comes from recordlessness, not from licence diversity; the price of enjoying both models' advantages is a list that stays maintained.
Author
Serdar YAMAN
Yamanlar Bilişim Expert
Writes content on IT infrastructure, cybersecurity, and digital transformation at Yamanlar Bilişim. Get in touch for any questions.
Professional Support
Get help on this topic
Let's design the Software and License Management solution you need together. Our experts get back to you within 1 business day.
support@yamanlarbilisim.com · Response time: 1 business day
Keep Reading
Related Articles

Licence Optimisation for Price-Rise Season: Finding and Closing Unused Subscriptions
January is the software world's price-letter season — and most businesses only realise how much subscription they pay when those letters stack up. A five-step cleanup that finds the empty seats, duplicate tools and over-sized plans, and wins the budget back.

Microsoft Licensing Types: Which Plan Is Right for an SME?
The differences between Microsoft 365 Business Basic, Standard, Premium and Enterprise E1/E3/E5 are confusing. This guide explains which plan fits which scenario at SME scale across usage, security, and cost.

Preparing for a Software Audit: 12 Things to Do Before a BSA Inspection
A software audit is a process SMEs frequently encounter but are often caught unprepared by. This guide explains the 12 concrete steps to complete before audit requests from BSA, Microsoft, and Adobe.