Migration Paths for Security Platforms

Migration paths

Security systems get built once and then left alone for a decade. The VMS is three major versions behind, the access control head-end is on a server operating system that stopped getting patches, and the database underneath both of them went out of support in a year nobody wrote down. Then a support date lands in the middle of a budget cycle and the whole estate has to move at once.

This is the reference I use when planning those moves. Supported routes, real lifecycle dates, the order things have to happen in, and a checklist per platform. Sourced from vendor documentation and dated, because the answer changes.

What is expired or expiring

Everything below is either already out of support or has a date on the calendar. If any of it is running a security system, it is the first thing to plan around.

Platform	Version	Status	Support ends
Genetec	5.10	Out of support	—
Genetec	5.9	Out of support	December 2025
Software House	C-CURE 9000 v2.8x and older	Support ending	—
Microsoft	Server 2016	Support ending	12 January 2027
Microsoft	Server 2012 R2	Out of support	10 October 2023
Microsoft	Windows 11 23H2	Out of support	11 November 2025
Microsoft	Windows 10 (all editions)	Out of support	14 October 2025
Microsoft	SQL Server 2017	Support ending	12 October 2027
Microsoft	SQL Server 2016	Out of support	14 July 2026

Video management

Genetec Security Center migration paths

Supported upgrade routes to Security Center 5.14, which versions need a two-step hop through 5.11, and the sequencing that keeps Archivers, federated systems, and SDK integrations working across the move.

Access control

C-CURE 9000 migration planning

Upgrading C-CURE 9000 is three migrations stacked: the application, the Windows and SQL platform underneath, and the Mercury panel firmware in the field. What to sequence, what the version matrix will not tell you, and where the door hardware bites.

Server operating system

Windows Server migration paths for security systems

Windows Server 2016 loses support on 12 January 2027, and it is under more VMS and access control head-ends than most integrators realise. Supported upgrade routes, what an in-place upgrade costs you, and the order to move a security estate in.

Workstation operating system

Windows workstation migration for security operators

Windows 10 went out of support in October 2025 and at least one major VMS still lists it as a supported client platform. What that means for operator workstations, the Windows 11 servicing cadence nobody budgets for, and how to move a SOC without losing a shift.

Database platform

SQL Server migration under a security platform

SQL Server 2016 went out of support in July 2026 while current VMS releases still list it as supported. Upgrade routes to 2019 and 2022, the Express edition ceiling nobody plans for, and how to move a security database without losing the archive index.