When your practice server, or the Windows Server or SQL Server version on it, reaches end of life, nothing breaks that day. Microsoft stops releasing security fixes for it, and your clinical software vendor will usually stop supporting new versions on it. That leaves patient data on a system that gets weaker every month. You have three ways forward: replace the server, upgrade what runs on it, or move the clinical software to the vendor’s cloud. Start planning at least three months before the date.
Consider a hypothetical practice manager at a five-doctor GP clinic. The IT provider’s report says the server runs Windows Server 2016 and that extended support ends in January 2027. The server is six years old and still works fine. Her question is whether that matters, and if so, what it will cost and how much disruption it will cause.
What does end of life actually mean?
- No more security updates. New vulnerabilities found after the date are not fixed for that version.
- Vendor support narrows. Clinical software vendors list the operating system and SQL Server versions they support. Older versions drop off, and new releases of the software may not install.
- Insurance and accreditation questions. Cyber insurance questionnaires often ask whether you run unsupported software. An honest “yes” can affect your premium or cover.
- Hardware age is a separate clock. A server can be on a supported operating system and still be past its warranty. Both matter.
Which dates matter for a practice server?
| Product | End of extended support |
|---|---|
| Windows Server 2012 and 2012 R2 | 10 October 2023 (already ended) |
| SQL Server 2016 | 14 July 2026 (already ended) |
| Windows Server 2016 | 12 January 2027 |
| SQL Server 2017 | 12 October 2027 |
| Windows Server 2019 | 9 January 2029 |
| SQL Server 2019 | 8 January 2030 |
Dates are from Microsoft’s product lifecycle pages. Check the page for your exact version. Many practices run Best Practice, MedicalDirector or other clinical software on SQL Server, so check both the Windows Server and SQL Server versions.
How do you find out what your server runs?
Ask your IT provider for four facts in writing: the Windows Server version, the SQL Server version and edition (if your clinical software uses one), the server’s purchase date and warranty end, and the clinical software version. Then check your vendor’s current system requirements against them. With those four facts, the decision is usually clear.
What are the options?
| Option | When it fits | What to check |
|---|---|---|
| Replace the server | Hardware is old or out of warranty, and you want to stay on premises | Vendor’s supported specification, licensing for Windows Server and SQL Server, backup, and a tested migration plan |
| Upgrade the software on the existing server | Hardware is recent, under warranty and meets the vendor’s requirements | Vendor approval for the upgrade path, a full backup and restore test first, and downtime |
| Move to the vendor’s cloud product | The cloud version covers your workflows and integrations | Feature gaps, data migration, internet reliability, subscription cost and what happens to the old server and its data |
If you need more time, check whether Microsoft sells paid Extended Security Updates for your version, and whether your software vendor supports running on them. Treat that as a bridge with an end date, not a plan.
What should the replacement plan include?
- Vendor confirmation of the target Windows Server and SQL Server versions, and who moves the clinical database.
- A restore test of the current backup before anything moves.
- A cutover date outside clinic hours, with a rollback plan if checks fail.
- A clean-up step: securely wiping or destroying the old server’s disks, because they hold patient data.
- Updated documentation: what was installed, where backups go and who to call.
Our clinic server migration checklist covers the cutover in detail, and our guide to who supports Best Practice, Genie and MedicalDirector explains what the vendor owns.
Frequently asked questions
Does an end-of-life server stop working?
No. It keeps running on the day support ends. What stops is security updates from Microsoft and, often, support from your clinical software vendor. The risk grows from that day, and so does the chance your insurer or vendor asks about it.
When does Windows Server 2016 reach end of support?
Microsoft lists 12 January 2027 as the end of extended support for Windows Server 2016. Windows Server 2019 follows on 9 January 2029. Check Microsoft’s lifecycle pages for your exact edition, because dates are occasionally adjusted.
Can we just keep using the old server for another year?
You can, but you would be running patient data on an operating system that no longer gets security fixes, and your software vendor may stop supporting the setup. If you need time, agree a dated plan, limit what the server is exposed to, and check whether Microsoft offers paid Extended Security Updates for your version.
Should we move our clinical software to the cloud instead?
It depends on whether your vendor’s cloud product does everything your practice needs today. Several vendors now offer cloud versions. Compare features, integrations, data migration and the ongoing subscription against a five-year cost for a new server.
How long does a server replacement take?
Plan for weeks, not days. Hardware lead times, vendor scheduling for the database move, testing and a weekend or after-hours cutover all take time. Start at least three months before the support end date.
Next step for a practice with an ageing server
Our hypothetical practice manager asks her IT provider for the four facts, then her vendor for its supported versions and cloud option. Within a fortnight she has two written options with five-year costs, and books the work for well before January. Any practice can follow the same order.
Product dates come from Microsoft’s published lifecycle information and can change. Vendor requirements change too, so confirm them with your vendor. Nothing here adds a service inclusion, recovery time or response commitment; those belong in your written agreement. This is general information, not legal advice.
Is your practice server reaching end of life?
Call 1300 521 162 to talk through your server, software versions and options with the Netluma IT team. See healthcare IT support.
Related Services
Server Management Data Backup Managed IT
Remote helpdesk Monday to Friday, 6:30am to 6pm, excluding national public holidays. Gold Coast team.




