Windows Server to Linux migration · for small & mid-sized business

Windows Server to Linux — no core licences, no CALs.

Every Windows Server needs at least 16 core licences plus a CAL for each user, bought again at every upgrade. File, web and many application servers have no technical reason to stay. We move them to Debian or Ubuntu on a fixed price and date — and leave alone what genuinely needs Windows.

  • Fixed price & date
  • Cutover off-hours
  • Rollback at every wave
  • No lock-in

Why now

You pay per core and per user. Linux charges neither.

16core licences minimum per server (8 per CPU), whatever the server actually has
$1,176Microsoft's price for a 16-core Windows Server 2025 Standard licence — before user CALs
Jan 2027end of extended support for Windows Server 2016; after that, security updates only via paid ESU
0 €licence for Debian and Ubuntu Server; support only if you want it

Sources: Microsoft Windows Server 2025 pricing, Microsoft Lifecycle (Windows Server 2016), Debian and Ubuntu licensing.

Savings calculator

What would you keep?

Enter what you run today. The calculator applies the vendor's real licensing rules — core minimums included — and compares three years.

Today · per year—
After the move—
You keep over 3 years—before a one-off, fixed-price migration
Turn this into a migration plan →

Exchange rate used: 1 € = US$ (ECB reference rate, Sep 2026). Everything is calculated in your browser — nothing you enter is sent anywhere.

How we move it

Same services for your users. Fewer licences for you.

File servers → Samba

Shares, NTFS permissions and AD groups carried over; users keep the same drive letters and paths.

Linux in your Active Directory

Linux servers join your existing domain; logins, groups and Kerberos keep working.

Web servers → nginx or Apache

Sites, certificates and reverse-proxy rules moved. .NET applications only where they run on modern .NET on Linux.

Infrastructure roles

Print, DHCP and similar roles move to their Linux equivalents where that simplifies things — or stay on a domain controller.

Monitored and patched from day one

Every moved server is monitored, backed up and patched from the first day — by your team, by us or by StayPatched.

A way back

The Windows server stays powered off, not deleted, until you sign off.

Straight talk

What doesn't move one-to-one

How a migration runs

Five steps. The old platform stays intact until you sign off.

  1. 1

    Assess

    Inventory, written plan, fixed quote and date — before any work starts.

  2. 2

    Pilot

    Non-critical systems move first; performance and restores proven on your workloads.

  3. 3

    Plan the cutover

    A runbook per wave, agreed windows, a written way back for every step.

  4. 4

    Cut over

    Wave by wave, outside your business hours. Anything wrong rolls back.

  5. 5

    Hand over

    Documentation, runbooks, full admin access — or StayPatched keeps it patched.

Questions

What people ask before this move.

Will our users notice?

For file shares, usually not: the same paths and the same permissions. Each server switches in its own off-hours window.

Can Linux servers work with our Active Directory?

Yes. They join the existing domain; logins, groups and file permissions keep working.

What about our .NET applications?

Modern .NET (.NET 5 and later) runs on Linux; the older .NET Framework doesn't. The assessment checks every application.

Do we still need CALs?

Not for services that moved to Linux. Whatever still runs on Windows Server — including Windows Active Directory — still needs CALs.

How long does it take?

It depends on the number of servers and applications. The completion date is fixed in the quote after the assessment.

Get a migration plan

Tell us what you run. Get a fixed plan back.

A short call, then a written assessment: what moves as-is, what needs care, what should stay — with a fixed price and a fixed date. No obligation.

  • A reply from an engineer, not a sales sequence
  • Your details are used only to reply
  • If migrating isn't worth it for you, we'll say so

Your details are used only to reply to you. See the privacy notice.