Hi @Heba Wagih ,
the upgrade path is complicated because the upgrade of SCSM is like @XinGuo-MSFT described in the answer:
- SCSM 2012 -> SCSM R2 with Update Rollup 9 -> SCSM 2016 -> SCSM 2019 -> SCSM2022
Parallel you need to upgrade the OS and the SQL Server version as well based on the requirements of each SCSM version:
- SCSM 2016: SQL Server 2014/2014SP1 or SP2/2016 - Windows Server 2012R2/2016
- SCSM2019: SQL Server 2014/2014SP1 or SP2/2016 /2017/2019 - Windows Server 2016/2019
- SCSM2022: SQL Server 2017/2019 - Windows Server 2019/2022
This means you have to upgrade a lot of components multiple times (SCSM, SQL Server and OS). Every update of a component carries the risk of an error or problem.
- 4 upgrades of SCSM (SCSM 2012 -> 20212R2 UR9 -> 2016 -> 2019 -> 2022)
- 2 upgrades of SQL Server (SQL 2012R2 -> 2016 -> 2019)
- 2 upgrades of Windows Server 2012 R2 (Windows Server 2012R2 -> 2016 -> 2019)
Also you have to check if all customizations, mostly 3rd party solutions in SCSM 2012 or your own customizations, are possible to migrate. SCSM 2012/2012R2 is using .Net 3.5 and SCSM 2016 and above require .Net 4.5.1. This adds some more efforts during the migration and increase the risk for errors/issues.
I would consider a new start with SCSM 2022, latest OS and SQL Server versions.
----------
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Andreas Baumgarten