Migration: 2012 to 2025
Migrate Websites from Windows Server 2012 to Windows Server 2025
Windows Server 2012 and 2012 R2 have had no free security updates since 10 October 2023. The websites on them usually run on IIS 8, PHP 5.x and MySQL 5.5 or 5.6: the hardest combination to move, because all three are several major versions behind. Here is how to move them to a new Windows Server 2025 without breaking them, and what ServerMaid does for you on the way.
Website migration £49 £24.50 one-off per old server; included in every Agency licence. New server from £99 £49.50 for twelve months. 30-day money-back promise.
Upgrade in place, or move?
Why a clean 2025 server beats an in-place upgrade from 2012
Windows Server 2025 can be upgraded in place from 2012 R2 (not from the original 2012), but for a web server that is rarely the right call. An in-place upgrade keeps every old setting, permission and hand-made change, runs for hours with the websites offline, and has no easy way back if a site breaks afterwards. Many VPS providers do not offer it at all.
A migration builds a fresh 2025 server properly, moves only the websites and their data, and leaves the old server running until you switch DNS. If anything is wrong, the old server is still there.
What a Windows Server 2012 website usually looks like
- IIS 8 or 8.5 with handler mappings, rewrite rules and permissions set by hand over the years.
- PHP 5.4 to 5.6, sometimes 7.0, often installed through the old Web Platform Installer, which Microsoft retired in 2022.
- MySQL 5.5 or 5.6, with latin1 or old utf8 tables and database users that exist only on that server.
- Code written for PHP 5:
mysql_connect()and the othermysql_*functions,each(),create_function(), which PHP 7 and 8 removed.
Copy that onto a 2025 server with PHP 8 and MySQL 8.4 and three things break at once: the database import, the database connection and the code. ServerMaid deals with the first two and tells you exactly where the third will bite, before you move.
Rebuilt, not cloned
Your websites move. Your old server's baggage does not.
An old 2012 server carries a decade of workarounds. Cloning it onto 2025 would carry them too. ServerMaid takes only what belongs to each website and rebuilds it on the new server's hardened baseline.
Left behind on purpose
- Old permissions and accounts that no longer exist
- The old web.config and its missing handlers
- Old database accounts and grants
- Logs, temp files and abandoned backups
- The hand-made settings nobody wrote down
Rebuilt on the new baseline
- The site's files, database and host names
- Fresh least-privilege permissions for the site's own identity
- A web.config written for the new server
- A new database account limited to its own database
- Free SSL, proven backups and monitoring from day one
How it works
Windows Server 2012 to 2025 in four steps
1. Build the 2025 server
Rent a Windows Server 2025 VPS and let ServerMaid build it: hardened IIS, a supported PHP 8 line, MySQL 8.4 LTS, backups and a locked-down Remote Desktop.
2. Run Migrate on the 2012 server
ServerMaid Migrate is a single file that runs on Windows Server 2012 and 2012 R2. It only reads: it lists the IIS websites, copies their files and dumps their databases into one package.
3. Read the PHP 8 report
Before you import, Migrate lists every PHP 5 feature the sites use that PHP 8 removed, with the file and line, so a developer can quote the fix once instead of discovering it page by page.
4. Import and switch DNS
Each site is rebuilt on 2025 with its own folder, pool, permissions and database, its MySQL 5.5 dump fixed for MySQL 8.4 on the way. Check it, then point DNS at the new server; free SSL follows.
What gets fixed between MySQL 5.5 and MySQL 8.4
- Old table options. The pre-5.5
TYPE=MyISAMspelling becomesENGINE=, which MySQL 8 requires. - Zero dates. Defaults such as
'0000-00-00 00:00:00', which MySQL 8's strict mode rejects, are made importable. - Character sets. latin1 and old utf8 tables are brought to utf8mb4 so accents and emoji survive.
- Accounts and definers. Old users and grants stay behind; each site gets a new account with rights on its own database only, and DEFINER clauses that name missing users are put right.
Your data is not changed, only the parts of the dump that MySQL 8.4 would refuse. See moving off Windows Server 2012 or 2016 for the full list of what ServerMaid fixes and what it deliberately leaves alone.
Moving from Windows Server 2008?
Migrate needs Windows Server 2012 or newer. Sites on 2008 can still move: zip the website with a database export and upload it as one zip; ServerMaid imports the database and fixes the connection settings with your OK.
Questions about Windows Server 2012 to 2025 migration
Is Windows Server 2012 still supported?
No. Windows Server 2012 and 2012 R2 reached the end of extended support on 10 October 2023. Security updates since then need Microsoft's paid Extended Security Updates, which end in October 2026.
Can I upgrade Windows Server 2012 straight to 2025?
From 2012 R2, Microsoft supports an in-place upgrade to 2025; from the original 2012 it does not. For a web server a clean 2025 build plus a migration is safer: the old server keeps running and none of its old settings come across.
Will my PHP 5.6 site run on the new server?
Only if its code avoids the features PHP 7 and 8 removed. Migrate's PHP 8 report lists every one it finds, with file and line, before you import. An empty report usually means a straightforward move.
Does Migrate change the 2012 server?
No. It only reads: files are copied and databases dumped. The old server keeps serving until you switch DNS.
What does the migration cost?
£49 £24.50 one-off per old server for the migration, plus a ServerMaid licence for the new 2025 server (Server setup £99 £49.50 and Websites and SSL £79 £39.50 for twelve months). Agency licences include migration. See pricing.
Off Windows Server 2012, onto a server that gets updates
The old server untouched, the sites rebuilt properly on 2025, and a plain list of anything that needs a developer.