April 2026: everyone is migrating off JSS, and the deadline came from a blog

  • JD + AI
  • Sitecore
April 2026: everyone is migrating off JSS, and the deadline came from a blog

If you are running JSS 22.x on XM Cloud, the most consequential thing published in April did not come from Sitecore. It came from a pseudonymous WordPress blog, and it says the clock runs out in June.

That is the shape of the month. SUGCON Europe took over London for two days, SitecoreAI was the only thing anyone wanted to talk about, and the operational detail of how you actually get there was written up by individuals on free blogging platforms. The single Sitecore-authored post that reached our harvest was about AI strategy in travel and hospitality.

The deadline that arrived from a blog

Migrating to Content SDK 1.5.1 — scorewow, Score Wow! The claim the whole post rests on: "Sitecore has officially confirmed that JSS 22.x reaches end of life in June 2026". We could not match that to a Sitecore-published lifecycle page, so treat it as this author's claim and confirm it with your account team before you build a budget on it. The author writes under a handle and states no employer, which means we cannot tell you what commercial interest, if any, sits behind the advice. The technical content is a migration from JSS 22.7 to Content SDK 1.5.1 done over a weekend, and the useful part is the framing of what 1.0 to 1.5.x actually changed before you start.

Automate Your JSS → Content SDK Migration with GitHub Copilot Agent Mode — scorewow, Score Wow! The same migration, handed to an agent. Worth reading for the boundary it draws rather than the automation: the mechanical package and import rewrites go to the tool, the middleware plugins and the personalization wiring stay with a person. If you are estimating this work, that boundary is your estimate.

Your CI/CD Pipeline After the Migration: What Changes and What to Verify — scorewow, Score Wow! The part teams forget until the first deploy fails. Environment variables, build configuration and a verification checklist for Content SDK 1.5.x. Read it during planning, not during the incident.

Three of the fourteen posts we cite this month come from that one blog. That is 21%, under the threshold at which we would call a roundup someone's newsletter, but it is worth saying out loud: the best-documented account of the migration that will define Sitecore budgets this year was written by one person we cannot identify.

Customization moved out of the server and into the browser

App Studio: Rethinking How We Customize DXPs in the SaaS Era — Jose, Sitecore Tips "Customization never ends", which every Sitecore team already knows. What changed is where it lands. On SaaS you no longer patch a pipeline or drop a DLL, you build an app. This is the piece to read before you promise a client a customization on the old assumptions.

Building a Page Health Dashboard – Part 1: SDK Subscription & Architecture and Part 2: Scoring Functions & UI — Devanshi, Tech Insights By Devanshi The same argument with running code. A live SEO dashboard inside the Pages editor, built on the Marketplace SDK subscription model: part one is the architecture and how the app subscribes to page context, part two is the scoring and the UI. This is the closest thing published in April to a reference implementation of the new extension model, and it is on a personal WordPress blog rather than in Sitecore's developer docs.

Sitecore Serialization Viewer: Simplifying Serialization Management — jagadeeshmaroju, Jagadeesh's blog A VS Code extension that puts a visual layer over Sitecore CLI serialization. Small, and it targets the exact moment where a developer pulls the wrong subtree and finds out at review.

Search now has two models, and you have to pick

SitecoreAI Search Experiences: A First Look — no byline on the page; the site describes itself as "A Sitecore blog by Marcel Gruber" Search Experiences is a new search model in SitecoreAI, meant to pair with Content SDK 2.x, and it is not the same product as full Sitecore Search. The historical note is the part that earns its place: Sitecore Search came out of the 2021 Reflektion acquisition, built for commerce, and that lineage explains a lot of the behaviour teams find surprising. If your architecture assumed one search product, that assumption expired in April.

Sitecore Search End-to-End: Integrating the Search SDK into Your JSS Next.js Headless Solution — David Goosem Nearly four thousand words of end-to-end integration, written from a build rather than from the documentation. If you are on the existing Search product, this is the implementation guide the docs do not give you.

SUGCON, and what Sitecore published instead

SUGCON Europe 2026 - Key Takeaways — no byline on the page, though it runs on Vinay Jadav's own domain and the page title names him The event ran 16 and 17 April at Park Plaza Victoria in London. The takeaways worth acting on: the Marketplace Code Jam built a working SitecoreAI Marketplace app against the Blok MCP server and the Sitecore Docs MCP server, and the migration tooling sessions kept circling the same JSS problem. The keynote was Sitecore's own market positioning, so read that section as such.

AI-driven experience strategy in travel and hospitality — no author credited; Sitecore's official Insights blog This is Sitecore writing about the product Sitecore sells, so it is marketing rather than analysis and we are treating it that way. It is also, notably, the only vendor-published item in our April Sitecore harvest. In a month where several thousand words of migration guidance were needed, that is a choice.

Why SitecoreAI - Getting into the shoes of the customer how to select right CMS — Daivagna Nanavati Written from pre-sales demos, which makes it the closest thing to an honest account of the questions prospects actually ask. Nanavati does not state an employer on the post, and the framing is clearly from the selling side of the table, so read it as sales-floor field notes rather than a neutral comparison.

The unglamorous half

Sitecore CDP Audience Export — Chandan XP 10.1 to CDP, with a downstream system that must keep receiving the "exact same JSON format". Every migration has one of these constraints and it is usually the thing that decides the shape of the whole integration. Useful precisely because it is not about AI.

Sitecore containers without Docker Desktop — Martin Miles Docker Desktop needs a paid subscription above 250 employees or $10M revenue, which is most of our clients, and Miles walks through running standalone Docker Engine as a Windows service instead. He is explicit about which steps are Sitecore-supported and which are community-derived, which is the detail that makes it usable. Our harvest recorded the title of this one as "Experience Sitecore !", the site name rather than the article name, so the title above is taken from the article URL.

What we're watching

The uncomfortable fact of April is that the single date driving Sitecore roadmaps this year reached us through a blog we cannot attribute to a person. Whether or not the June figure holds, that is a documentation failure, and it is the vendor's. A platform whose migration deadline is best explained by an anonymous author has outsourced its most important communication to volunteers.

The second thing is quieter and probably bigger. App Studio and the Marketplace SDK move customization from code you deploy to apps you register, and April was the month the community started publishing real implementations of it. If you have a team whose Sitecore expertise is pipelines and processors, their skills have a shelf life now, and it is shorter than the JSS one.

Sources

sitecore · xm-cloud · sitecore-headless · how-to · ai · architecture · seo · sitecore-search