
In June 2026, Sitecore JavaScript Services (JSS) 22.x reached end of life (end of maintenance) for SitecoreAI, formerly XM Cloud. JSS 23, released in September 2026, supports self-hosted Sitecore XM and XP 10.5 and removes SitecoreAI support from every JSS package. For SitecoreAI teams still running front ends on JSS, the framework has no future investment behind it.
End of life means no further updates of any kind, security patches included, and no support. Sitecore names the Sitecore Content SDK as the official and supported SDK for SitecoreAI, and recommends it for all new projects.
If your organisation still relies on JSS, every month on an unsupported framework adds exposure. The move to the Content SDK is well understood, and a planned migration takes weeks.
What end of life for JSS 22.x actually means
In practice, it has direct implications for risk, cost and capability:
- No security updates – vulnerabilities are not patched, so exposure grows over time.
- No bug fixes – issues you discover in production receive no official fixes from the product team.
- No future support – support options narrow, and it becomes harder to justify JSS in risk and architecture forums.
- Rising operational risk – as the rest of your stack moves forward, an end-of-life front-end framework becomes a weak point.
For regulated industries, public sector and complex B2B platforms, an unsupported front end is a governance and compliance question.
Why the Content SDK is the path forward
Sitecore describes the Content SDK as the version of JSS built exclusively for SitecoreAI. New SitecoreAI front-end capability, such as Design Studio support, ships in the Content SDK.
Moving to the Content SDK brings immediate benefits:
- Alignment with SitecoreAI – you are building on the supported, forward-looking model.
- Modern Next.js support – the App Router arrived as a beta in Content SDK v1.2.0 and has had full, production-ready support since v1.3.1.
- Design Studio support – every component in your application is visible in SitecoreAI’s Design Studio, where it can be previewed with different content.
- Simpler applications – cleaner naming and code across the SDK, and smaller, less complex starter apps.
What to check before you migrate
Most teams understand that JSS needs to be retired. The harder question is how to migrate a live implementation without disruption. Before you commit to a plan, review:
- Your JSS setup, architecture, hosting and dependencies.
- The incremental front-end changes and custom patterns built up in JSS over time.
- How components, routes and rendering logic map to the Content SDK model.
- How many front-end applications sit within your SitecoreAI project.
- Which Content SDK version to target: 2.x is the active line, and 1.x is in maintenance.
- Whether to adopt the App Router as part of the move, on Content SDK v1.3.1 or later.
- Who needs to be involved across development, operations and content teams.
Those answers give you an estimate of effort, risk and cost with enough confidence to commit to a plan.
How long a migration takes
In our delivery experience, a JSS to Content SDK migration typically takes two to four weeks, depending on complexity. The checks above are what set that complexity.
Planning a migration after the deadline
The deadline has passed, and the pressures that make a rushed migration risky still apply:
- Your team still has a roadmap of new features, campaigns and releases to support.
- Many organisations operate on annual or multi-year budgeting cycles.
- Enterprise change windows, particularly in regulated sectors, are limited.
A planned migration gives you time to:
- Run a calm, thorough assessment of your JSS implementation.
- Agree an architecture and migration pattern aligned with the Content SDK and SitecoreAI.
- Schedule delivery in a way that respects other programme priorities.
The goal is to remove surprises.


