Methodology: Dates come from Microsoft's own lifecycle pages and Microsoft Learn documentation. Vendor facts come from each vendor's own pages. All were checked on 12 Oct 2026. No vendor reviewed or paid for this article. We did not run hands-on tests.
System Center Service Manager end of life comes down to one date: System Center 2016 Service Manager (SCSM 2016) reaches end of support on 11 Jan 2027, per Microsoft's "Ending support in 2027" page. SCSM 2022 moves from mainstream to extended support on 13 Apr 2027. SCSM 2019 is already in extended support, and System Center 2025 Service Manager is supported into 2030 and 2035. This guide is for ITSM platform owners, often running the Cireson portal, choosing between an in-place upgrade and a move to a SaaS platform.
Key takeaways
- System Center 2016 Service Manager reaches end of support on 11 Jan 2027, 91 days from this article's date (Microsoft, Ending support in 2027 page, as of 12 Oct 2026).
- SCSM 2022 leaves mainstream support on 13 Apr 2027. SCSM 2025 has mainstream support to 8 Jan 2030 and extended support to 9 Jan 2035 (Microsoft lifecycle pages, as of 12 Oct 2026).
- Microsoft documents only in-place upgrades, one version at a time, and 2025 can be reached only from 2022, so a 2016 system needs three upgrades (Microsoft Learn, as of 12 Oct 2026).
- Microsoft has published no Service Manager dates beyond its lifecycle table, and no statement about a release after 2025.
System Center Service Manager end of life: the key dates
Microsoft publishes these dates for every Service Manager release still in use. All four follow its Fixed Lifecycle Policy.
| Release | Lifecycle start | Mainstream support ends | Extended support ends (end of support) | Status on 12 Oct 2026 |
|---|---|---|---|---|
| System Center 2016 Service Manager | 28 Oct 2016 | 11 Jan 2022 | 11 Jan 2027 | Extended support, 91 days left |
| System Center 2019 Service Manager | 14 Mar 2019 | 9 Apr 2024 | 9 Apr 2029 | Extended support |
| System Center 2022 Service Manager | 1 Apr 2022 | 13 Apr 2027 | 13 Apr 2032 | Mainstream, 183 days left |
| System Center 2025 Service Manager | 1 Nov 2024 | 8 Jan 2030 | 9 Jan 2035 | Mainstream |
Source: Microsoft lifecycle pages for each release and the Ending support in 2027 page, as of 12 Oct 2026. Microsoft's product pages print each end time as 6:59:59 AM, for example on 12 Jan 2027 for SCSM 2016. The table uses the Pacific calendar date, which matches the 11 Jan 2027 and 13 Apr 2027 dates on the Ending support in 2027 page.
Service Manager is not the only System Center 2016 component on that date: Microsoft lists Data Protection Manager, Operations Manager, Orchestrator and Virtual Machine Manager 2016 on 11 Jan 2027 too. If your servers run Windows Server 2016, that OS reaches end of extended support on 12 Jan 2027, and SQL Server 2016 extended support ended on 14 Jul 2026 (Microsoft lifecycle pages, as of 12 Oct 2026). Check the whole stack.
What changes at System Center Service Manager end of support
Microsoft's Fixed Lifecycle Policy has three phases (lifecycle policy page, as of 12 Oct 2026).
| Phase | Security updates | Non-security updates and design changes | Support |
|---|---|---|---|
| Mainstream support | Available | Available on request | Incident support, including no-charge support where your license includes it |
| Extended support | Available at no extra cost | Not available | Paid support; limited complimentary support may be available |
| After end of support | Only through the Extended Security Update (ESU) program | Not available | Self-help; paid support requires the ESU program |
SCSM 2016 and 2019 are already in extended support, so you receive security updates but no fixes or features. Their last update rollups are Update Rollup 10 (October 2020) and Update Rollup 4 (June 2022) (Microsoft Learn, as of 12 Oct 2026).
The cliff for 2016 is 11 Jan 2027. Microsoft's ESU FAQ (updated 24 Aug 2026) lists Windows Server 2012 and 2012 R2 and Windows 10, and does not mention System Center. We found no ESU offer for Service Manager, so ask your Microsoft account team before assuming one exists. For SCSM 2022, 13 Apr 2027 changes less: you keep security updates and lose non-security fixes.
Your options after SCSM 2016 end of support
Upgrade within System Center. Microsoft documents that 2019 can be reached only from 2016 (or 1801 and 1807), 2022 only from 2019, and 2025 only from 2022. Side-by-side and rolling upgrades are not supported for the 2025 step. The 2025 release needs Windows Server 2019 or later and SQL Server 2019 with CU8 or later, or SQL Server 2022. Microsoft also warns that a wrong order of System Center component upgrades can leave components with no recovery option (Microsoft Learn, as of 12 Oct 2026).
Move to a SaaS ITSM platform. This article covers three destinations: Freshservice, Jira Service Management (JSM) and ServiceNow. As SaaS platforms they remove the Windows and SQL servers from your ITSM footprint. Management packs are SCSM-specific XML, so the workflows they hold are rebuilt.
| Option | Choose this if | Watch for |
|---|---|---|
| Upgrade 2016 to 2019 only | You need supported status after 11 Jan 2027 and cannot finish a platform move first. 2019 is supported to 9 Apr 2029. | Buys time, not features. Mainstream support is already over. |
| Upgrade to 2022, then 2025 | You are committed to System Center and want mainstream support to 8 Jan 2030. | Three in-place hops from 2016. OS and SQL prerequisites. Other System Center 2016 components share the date. |
| Move to Freshservice, JSM or ServiceNow | You want to stop hosting ITSM servers, or are retiring other System Center 2016 components. | Workflows, notifications and SLOs are rebuilt. Relationships and history need a mapping plan. |
| Stay unsupported | You have a dated retirement plan and a written risk acceptance. | No security updates after 11 Jan 2027. |
SCSM alternatives: what the three destinations publish
| Platform | Published pricing (as of 12 Oct 2026) | Where change and problem management sit |
|---|---|---|
| Freshservice | Starter $19, Growth $49, Pro $99 per agent per month billed annually; Enterprise custom | Pro (Freshworks pricing page) |
| Jira Service Management (Service Collection) | Free for 3 agents; Standard $20 and Premium $51.42 per agent per month; Enterprise by quote | Premium (Atlassian pricing page) |
| ServiceNow ITSM | No public prices; custom quote | Advanced package; CMDB is in Foundation (ServiceNow pricing page) |
If you run the Cireson portal, ask Cireson in writing what it supports after 11 Jan 2027. Its portal prerequisites page (undated) lists Service Manager 2016, 2019, 2022 and 2025 as fully supported, but Microsoft's dates govern SCSM itself.
What moves out of SCSM and what does not
Records and relationships can move. Behavior has to be rebuilt. Microsoft describes the SCSM database as holding configuration items, work items and the product's own configuration (Microsoft Learn, as of 12 Oct 2026).
| Moves as records | Rebuilt on the new platform | At risk if not planned |
|---|---|---|
| Incidents, service requests, change requests, problems and release records | Workflows, forms, views and classes held in management packs | Links between work items, and between work items and CIs (affected and related items) |
| Activities on change and service requests (manual, review, dependent) | Notification templates and subscriptions (email is the only supported channel) | Private action log entries, which must map to internal notes |
| Configuration items and service maps | Service level objectives, calendars and metrics for incidents and service requests | Attachments, because we found no Microsoft-documented bulk export |
| Knowledge articles (title, keywords, description, internal and external content) | Request templates, the service catalog and the self-service portal, including Cireson customizations | Review activity votes and in-flight approvals |
| Action log entries, resolution comments and closure comments | Connectors that import CIs from Active Directory, Configuration Manager and Operations Manager | History older than your grooming settings and data warehouse retention |
How data leaves SCSM: what Microsoft documents
Microsoft documents four routes. None is a ready-made export to another ITSM platform.
- PowerShell. Get-SCSMClassInstance and Get-SCSMRelationshipInstance retrieve records. Export-SCSMManagementPack exports definitions as XML, not records.
- Data warehouse. DWStagingAndConfig holds copies of management packs, configuration items and work items. Fact table data is kept for three years by default.
- Reports and cubes. Any user can export report data, and predefined OLAP cubes open in Microsoft Excel.
- The SCSM database. Microsoft calls it the CMDB but does not document it as an export interface.
Check retention this month. Grooming deletes work items from the main database once they meet console thresholds, and a Microsoft Learn archive post (dated 2012) says the data remains in the data warehouse. If your warehouse keeps the three-year default for fact data, older history may exist in neither place. Microsoft names the Get-SCDWRetentionPeriod cmdlet to check it.
Each destination has its own landing rules. ServiceNow stores CI relationships in cmdb_rel_ci as a parent CI, a child CI and a relationship type (ServiceNow documentation, updated 10 Sep 2026). Freshservice asset relationships have normal and inverse directions (Freshservice help center, modified 10 Mar 2026). JSM Assets connects objects through references such as Dependency and Link (Atlassian documentation, undated). Atlassian's CSV import guide recommends about 1,500 work items per file and warns that comments mapped from a CSV become public in JSM spaces. Freshworks documents a Bulk API for migration partners, with rate limits marked "to be confirmed post load testing" (modified 24 Nov 2025). MigrateX moves service history between ITSM platforms, so we have a view on this; the points above hold whoever does the work.
A backwards plan from 11 Jan 2027
There is no neutral public benchmark for how long an SCSM migration takes, and Microsoft publishes none. So this plan fixes the order of work and the decision gates, and leaves durations to your own test results.
| When | What must be true |
|---|---|
| By 31 Oct 2026 (Q4) | Inventory done: SCSM version and update rollup, Windows and SQL versions, management packs, connectors, Cireson apps, warehouse retention, record counts. Gate 1: upgrade, move, or move with a bridge. |
| November 2026 (Q4) | Upgrade path: lab test of each hop and the component upgrade order. Move path: field mapping signed off, destination configured, first test migration run and reconciled against SCSM counts. |
| December 2026 (Q4) | Second test migration or upgrade rehearsal, user acceptance testing, rebuilt workflows and SLOs tested. Check your change calendar for year-end freezes. Gate 2: go or no-go. |
| 1 to 11 Jan 2027 (Q1) | Cutover with delta sync, or the final in-place upgrade. Reconcile counts, then hypercare, with SCSM kept read-only and backed up until sign-off. |
The bridge decision. If a platform move cannot cut over before 11 Jan 2027, you have two choices. Upgrade 2016 to 2019 in place, which gives extended support to 9 Apr 2029, and migrate on a calmer schedule. Or run SCSM 2016 unsupported for a dated, approved period. The first costs an upgrade you may throw away. The second costs security exposure.
SCSM end of life checklist
- Record your SCSM version and update rollup, and list other System Center 2016 components, which share the 11 Jan 2027 date.
- Record Windows Server and SQL Server versions and their lifecycle dates.
- List management packs and connectors, and mark each as in use, unused or unknown.
- Note your data warehouse retention and work item grooming settings.
- Count work items by type, activities, CIs, relationships, knowledge articles and attachments.
- Ask Cireson and your Microsoft account team what support exists after 11 Jan 2027.
- Hold Gate 1 by 31 Oct 2026: upgrade, move, or move with a bridge.
- Back up the databases, the encryption key and unsealed management packs before any change.
- Write the SCSM retirement date and name who signs off the risk if it runs past 11 Jan 2027.
FAQ
Methodology
We read Microsoft's lifecycle pages for each Service Manager release, its Ending support in 2027, lifecycle policy and ESU pages, and Microsoft Learn documentation on upgrades, the data model, the data warehouse and cmdlets, all on 12 Oct 2026. Destination facts come from each vendor's own pages. We did not speculate about Microsoft's plans beyond what it has published. Disclosure: MigrateX, the publisher of this article, runs ITSM data migrations, including between platforms named here. No vendor reviewed or paid for this article.