SitecoreAI: what it is, what it includes, and who it affects

SitecoreAI is Sitecore's digital experience platform: XM Cloud rebranded and expanded with more components and AI agents.
It is not a new product, you do not have to purchase it separately, and there is nothing to install.
We’ll walk you through what happened and what it means for your project.
The change has already taken place
The name change was for a practical reason. The offering was no longer just a CMSwith optional extras, but a suite that Sitecore sells and deploys together.
Sitecore describes the move as shifting from composable to composed.
- Composablemeans buying each piece separately and integrating them yourself.
- Composedmeans the platform arrives as a unified package that you configure.
That nuance explains almost everything that follows, including the budget.
So, XM Cloud hasn't disappeared. The change took place on November 10, 2025: XM Cloud tenants were automatically transitioned to SitecoreAI, at no extra cost and without the need for a migration project.
What SitecoreAI includes
SitecoreAI covers the entire lifecycle of your content: creating it, organizing it, publishing it, ensuring visitors can find it, and deciding what each person sees.
Previously, these were separate products you had to license and connect. Now, they come together.
- CMS. The cloud-based content manager, which until now you knew as XM Cloud. This is where you create templates, build pages, and publish. It is the core that everything else connects to and the place where your content team works every day.
- CDP. Customer Data Platform: unifies the data a single visitor leaves across different channels into one profile. Web browsing, forms, email campaigns. Without this unification, each channel sees a different person.
- Personalize.Use those profiles to decide what each visitor sees. The same page block, but different content depending on the segment. An installer and a purchasing manager visit the same URL and read different messages.
- Sitecore Search.The site's internal search engine, with its own name. It indexes your content and returns results ordered by rules controlled by marketing. In long industrial catalogs, finding the right reference is a major part of the buying process.
- DAM. Digital Asset Management: the single repository for images, videos, blueprints, and data sheets. A single source for the entire organization, without twenty versions of the same render in shared folders. The embedded DAM is Content Hub DAM.
- Content Hub.The process layer on top of that repository: who requests the content, who approves it, and when it expires. DAM and Content Hub are the same product on two levels. One stores the assets, the other governs the lifecycle.
And what about Sitecore Stream, the AI layer that Sitecore launched before all of this? Within SitecoreAI, it doesn't exist as a separate product because AI permeates the entire platform.
Stream is still alive, but for XP and XM.
.jpg)
Sitecore Studio: where agents live
Studio is the platform's extensibility layer, consisting of four spaces:
- Agentic Studio.Where you design, execute, and govern agents and workflows.
- App Studio.Where your team or partner builds custom extensions and apps.
- Marketplace.Third-party apps and agents, with no-code installation.
- Sitecore Connect.The low-code integration layer for external systems, using connectors and recipes.
Inside Agentic Studio, you have 16 ready-to-use agents.
These include the Researcher, Competitor Analyzer, Translation Assistant, and AEO/SEO Researcher, which works to ensure your content appears in search engines and AI answers. The number grows with every release.
Prebuilt agents do not require a Builder license or consume credits. They run right out of the box.
What comes standard and what is purchased separately
A single platformdoesn't mean everything is on the same line item, and it's worth mentioning before it comes up in negotiations.
Your SitecoreAI contract includes entry-level access to each capability, with caps on: environments, storage, CDN bandwidth, interaction volume, DAM users, and Agentic Studio Builder seats.Increasing any of those caps requires an additional purchase.
The most common case is DAM. What comes standard is not the full depth of Content Hub, and the integration of Content Hub within SitecoreAI is being rolled out in phases. If your project depends on heavy DAM workflows, check what level is included in your proposal.
There is one invoice. Not all line items are the same.
How to check it yourself in ten minutes
- Log in to your tenant.If you see the SitecoreAI interface, your migration has already taken place.
- Check the date of the documentation, not the name.You will find official pages that say XM Cloud and others that say SitecoreAI for the same functionality. It is an ongoing brand transition.
- Review your contract without alarm.If you say XM Cloud, that's fine. XM Cloud is still alive as a component of the SitecoreAI family.
- Ask your account manager which agents you have active in addition to the out-of-the-box ones.Translation Assistant, Researcher, and AEO/SEO researcher come out-of-the-box.

How it's paid
There is no public rate card. Everything is custom-quoted, and this is what you can count on:
- One metric per capacity. The core is measured by visits and the DAM by users.
- Personalize and CDP, which used to be two licenses, now share a single metric: Experience Interactions. This counts any experience that is personalized or modified by AI, from search results to variants and recommendations.
- AI is included. No cost per token, no credits, and no stated usage limits.
What changes depending on where you're coming from
The answer depends on your starting point, and there are only three.
1. You're coming from XM Cloud
You don't need to do anything. You're already on SitecoreAI. The name changed, the interface changed, and the location of everything changed. Your website keeps working the same way, and your team will spend an afternoon getting reoriented.
2. You're coming from on-premise XM or XP
This is where you have a real project on your hands.
On-premise means Sitecore is installed on servers that you manage. There is no switch to flip. You have to rebuild the architecture, the content model, and the custom integrations you set up.
Think of a manufacturer using XP with fifteen years of legacy templates and a catalog connected to their ERP. That project isn't "updated." It is planned, prioritized by section, and launched in phases. And you have a window of time to do it right.
Support and transition
Mainstream support for XP and XM 10.4 runs until the end of 2027, and extended support until the end of 2030.
Sitecore also announced a phased transition of XP and XM to modern .NET: modern .NET rendering hosts, gradual replacement of the CM using the strangler pattern, future cross-platform versions including Linux, and a support cycle aligned with .NET LTS releases.
3. You are coming from another CMS
Now we are talking about a CMS migration.
With one advantage:you aren't carrying over any Sitecore technical debt.And with a cost that is often overlooked: your team is starting from scratch with the tool and will need training.
Sitecore offersSitecoreAI Pathwayfor migrating content from previous platforms. We break down what is and isn't covered inhow to migrate to SitecoreAI.
What is a rebrand versus a replatforming
It is worth separating them, because budgets and expectations stem from that distinction.
In the first phase, for existing tenants, the underlying architecture did not change. The interface and the location of each function did. That is a rebrand, plus a layer of agents and components that now come bundled instead of being contracted separately.
True replatforming is something you did earlier if you moved from on-premise to XM Cloud. Or it is something you have ahead of you if you are still on-premise. That is where the architecture, deployment model, and the technical team's way of working actually change.
The difference is best seen with an example
If your content team uses a manual with screenshots of XM Cloud, that manual is no longer useful. Your front-end code, however, is. One takes an afternoon to update. The other would cost an entire project.
This distinction also helps you interpret what you are being told. When a vendor presents SitecoreAI as a new platform, ask what part of their proposal is configuration and what part is development.
What remains team work
Composed does not mean solved. The platform brings the pieces together. The decisions are still yours.
- Integrations with your CRM.Salesforce and Dynamics 365 integrate via Sitecore Connect. That reduces custom development, though it does not always eliminate it. It is not a native integration, and it is worth stating that before finalizing deadlines.
- The CDP data model.The CDP unifies what you give it. Without a clear criterion for identifying the same person across two channels, there is no single profile. There are two incomplete profiles.
- Personalization rules.Someone decides which segment sees which message, and with what content behind it. That is marketing's job. Personalize executes the rule; it does not invent it.
- Content governance.Content Hub organizes a process that already exists. If the process does not exist, you are just organizing chaos, and with more steps than before.
- Training.The interface has changed and the agents are new to almost everyone. Set aside time for your team to learn the tool. It’s the budget item that gets cut the most and the one that costs you the most later on.
We saw it with Thielmann. Before touching the website, we organized a workshop with managers from various departments to define their buyer personas. Then, we mapped out the customer journey for each one. No platform can do that part for you.
Let's talk about your case
At Novicell we are a Sitecore partner in Spain and we work with the platform on industrial B2B projects.
Our team implements SitecoreAI and migrates projects from other Sitecore versions or different CMS platforms. Tell us where you're starting from, and we'll tell you what you really need.
