Skip to content

Moving Applications off Windows Server 2016

Microsoft ends extended support for Windows Server 2016 on 12 January 2027. It is the same day that support for .NET Framework 4.6.2 ends, so a business application built in the late 2010s can lose security updates for its server and its runtime at once.

The server is usually the easy part. What takes the time is everything installed on it over the years: IIS sites, Windows services, scheduled tasks, a SQL Server instance, certificates and service accounts nobody has written down. We list all of it first, then move each application to a supported Windows Server, to Linux where the code allows, or to a cloud account in your own name.

Support dates

Where each Windows Server version stands

Dates from Microsoft's lifecycle pages, checked on 15 November 2026. Extended support is the last phase with free security updates.

Windows Server 2012 and 2012 R2

Extended support ended on 10 October 2023. Microsoft gives 13 October 2026 as the last day of their Extended Security Updates, so they now receive nothing.

Windows Server 2016

Extended support ends on 12 January 2027. Microsoft's lifecycle page lists three Extended Security Update years after that, the last ending in January 2030.

Windows Server 2019

Mainstream support ended on 9 January 2024; extended support ends on 9 January 2029. Moving here from 2016 buys two years.

Windows Server 2022

Mainstream support ended on 13 October 2026; extended support runs until 14 October 2031.

Windows Server 2025

Mainstream support until 13 November 2029, extended support until 14 November 2034. The usual target for a move made now.

Scope

What we list before anything moves

A server that has run for eight years carries more than its main application. Each of these is found, written down and given an owner.

  • IIS sites, application pools, bindings and the certificates they use
  • Windows services and scheduled tasks, with the accounts they run as
  • The .NET Framework version each application targets and the version installed
  • SQL Server instances, their versions, jobs and linked servers
  • File shares, mapped drives and folders other systems read or write
  • Firewall rules, open ports and every system that connects in or out
  • Backups, with one restore actually tested before the move
  • A written way back for each server: the old one is kept until the new one has run cleanly
Order of work

How a move runs

  1. Inventory

    We read each server with whoever runs it today and produce the list above, server by server. You receive it in writing, with what blocks each route and what clearing it involves.

  2. Choose a route per server

    An in-place upgrade, a new server built beside the old one, a cloud account you own, or Linux where the application allows. Different servers often get different answers.

  3. Rehearse

    The move is run first on a copy, and the application is checked there by the people who use it. Anything that differs from today is fixed before the real move.

  4. Move

    At a time agreed with you. The old server stays as it was, switched off from traffic but ready, until the new one has run cleanly for an agreed period.

  5. Retire

    The old server is backed up one last time and then switched off, and the inventory is updated to describe what now runs where.

Judgement

When an in-place upgrade is not the answer

An in-place upgrade suits

  • The server does one job and that job is well understood
  • The software on it is supported on the newer Windows Server
  • A full backup exists and a restore has been tested

A new server beside the old one suits better

  • Years of changes were made by hand and nobody can list them
  • The applications need a newer .NET Framework or SQL Server as well, which is cleaner on a fresh server
  • You want the option of moving to Linux or to a cloud account in the same project
  • The hardware or the virtualisation host underneath is itself out of support
Questions

Common questions

Can we just buy Extended Security Updates?

For a time, yes. Microsoft describes Extended Security Updates as a last-resort option: they contain security updates rated critical and important, and no new features or other fixes. They suit a server that is already being replaced. Prices and terms come from Microsoft or your licensing partner, not from us.

Can Windows Server 2016 be upgraded straight to 2025?

Microsoft states that, starting with Windows Server 2025, a non-clustered in-place upgrade can cross up to four versions at a time, so 2016 to 2025 is a supported path. Whether it is the right path depends on what has been installed on the server over the years.

Our application runs on .NET Framework. Does that change anything?

It adds a second deadline on the same day: .NET Framework 4.6.2 support also ends on 12 January 2027. On Windows Server 2016 the newest version Microsoft lists is .NET Framework 4.8; version 4.8.1 is listed for Windows Server 2022 and 2025. Moving the server is a good moment to move the runtime too.

Do you manage our servers afterwards?

Our work is the applications and their data. We work with whoever runs your servers today, or set them up in cloud accounts in your name, and hand over documentation either way.

Is there a calendar of these dates?

Yes. Our end-of-support dates page lists Windows Server, SQL Server, .NET and PHP dates with their sources, and offers a calendar you can subscribe to.

For enterprise buyers

What your procurement team will ask, answered before the call

  • Your paper or oursNDA, data-processing agreement, master agreement and statement of work.
  • Named peopleThe statement of work names the delivery lead and the escalation contact above them.
  • Your code, your accountsWork is committed to your repository and assigned to you on final payment.
  • Local sales teamsSales teams in the UAE and Singapore; engineering in Rajkot and Ahmedabad, India.
Next step

Tell us what runs on your Windows Server 2016 machines

How many servers, what each one does as far as you know, whether SQL Server is on the same machine, and who looks after them today. A rough answer is enough to start; the inventory fills in the rest. We reply within one business day.

Discuss a Windows Server move

Goes straight to our team on WhatsApp and email. We reply within one business day.