JSS EOL in June 2026 for SitecoreAI: what you need to know

In June 2026, Sitecore JavaScript Services (JSS) 22.x reaches end of life (end of maintenance). JSS 23.x for self-hosted teams wil be released around March/April 2026 but will not support SitecoreAI. For SitecoreAI teams running front ends on JSS, this isn’t a minor technical footnote, it is a hard stop for future investment in that framework.

End of life means no new features, no security patches, and no long-term roadmap. At the same time, Sitecore’s energy is firmly behind XM Cloud, SitecoreAI and the Sitecore Content SDK as the supported model for modern, cloud-native front ends.

If your organisation is still relying on JSS, the next 6-9 months are the window in which to design and execute a considered migration plan, not a last-minute scramble.

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 will not be patched, increasing exposure over time.
• No bug fixes – issues you discover in production will not receive 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, this is more than a technical inconvenience, it becomes a governance and compliance question.

Why the Content SDK is the path forward

Sitecore has been clear that the Content SDK is the strategic front-end integration pattern for XM Cloud (CMS) and the SitecoreAI stack. It is where new investment, features and optimisation effort are focused.

Moving to the Content SDK unlocks immediate benefits:

• Alignment with SitecoreAI – you are building on the supported, forward-looking model.
• Modern Next.js support – including App Router support in Content SDK v1.2 (currently beta) and a cleaner developer experience.
• Design Studio integration – better alignment with design systems and composable front-end workflows.
• Improved developer ergonomics – clearer contracts between content and front end, and cleaner patterns.

In other words, a move away from JSS is not just about avoiding risk. It is about unlocking the next generation of Sitecore front-end capability.

The real challenge: migrating from JSS to the Content SDK

Most teams understand that JSS needs to be retired. The harder question is how to migrate a live implementation without disruption.

Typical challenges include:

• Unpicking incremental front-end changes and patterns in JSS.
• Mapping components, routes and rendering logic to the Content SDK model.
• Managing multiple front-end applications within a single XM Cloud project.
• Coordinating changes across development, operations and content teams.
• Estimating effort, risk and cost with enough confidence to commit to a plan.

This is where specialist experience – and the right tooling – matters.

Think Fresh Digital’s experience with Content SDK migrations

Think Fresh Digital is a specialist Sitecore partner focused on SitecoreAI and modern headless architectures. We have already delivered enterprise migrations from JSS to the Content SDK, taking solutions from assessment through to production.

Our work in this space is underpinned by three things:

• Deep platform expertise – our leadership includes an 8-time Sitecore MVP and senior delivery specialists with long-track records in complex Sitecore programmes.
• Hands-on Content SDK delivery – we are not learning on your project; we are applying patterns proven in real migrations.
• AI-powered analysis tooling – we have built a proprietary CLI tool that analyses JSS solutions and generates a detailed migration plan.

Our CLI tool can analyse a JSS codebase in minutes and produce a structured view of components, routes and dependencies, together with a file-by-file breakdown of the changes required. It also generates prompts that can be used to automate parts of the migration process.

That combination of experience and tooling allows us to reduce manual analysis effort, improve scoping accuracy and accelerate delivery.

Fixed-cost migrations for JSS to Content SDK

Because we have invested in this problem space, we are able to offer fixed-cost migrations for JSS to Content SDK, covering assessment, planning, execution and hyper-care support.

For many organisations, this fixed-cost model provides the predictability needed to secure internal approval while still benefiting from specialist engineering and AI-accelerated planning.

Why act now, not in 2026

On paper, June 2026 can feel distant. In reality:

• 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.

Waiting until 2026 compresses your options. Starting now gives you time to:

• Run a calm, thorough assessment of your JSS implementation.
• Agree an architecture and migration pattern aligned with Content SDK and SitecoreAI.
• Schedule delivery in a way that respects other programme priorities.

The goal is not to rush, but to remove surprises.

Where to go next

If you are running JSS in production, now is the right moment to explore your options.

Explore the Content SDK migration offer to see how we approach assessments, planning and delivery.