Sitecore XP → SitecoreAI Migration

This recipe migrates a Sitecore XP Headless site to SitecoreAI CMS (XMC) SXA Headless — code, content, and presentation — using a team of 21 specialized agents across five orchestrated phases.

It is designed as a minimal-change, de-risked migration. The goal is to preserve as much of your original codebase as possible while making only the structural changes required to run on SitecoreAI CMS (XMC). You don't rewrite your site — you migrate it.

What this recipe covers

Scope	Details
Source	Sitecore XP — Headless JSS (React), any version
Target	SitecoreAI CMS (XMC) — SXA Headless, Content SDK 2.0, Next.js
Code	React/JSS components — migrated one at a time, verified in a live sandbox
Content	Full content tree — templates, items, renderings, layout — serialized and pushed to XMC
Presentation	SXA conversion — headless tenant, rendering registration, partial designs, page designs
Resolvers	C# Rendering Contents Resolvers — converted to TypeScript GraphQL adapters
Not included	MVC source sites, full redesign, custom module rebuilds

Migration philosophy

Minimal change. Approximately 95% of your original component code is preserved. Only what is structurally incompatible with XMC is modified.

Visual and progressive. You see every change rendered in a sandbox dev server before approving it. Nothing happens in the dark.

Incremental and always working. Components are migrated one at a time. After each one, the app still builds and renders. One change never silently breaks something elsewhere.

Safe to stop, safe to resume. Every phase saves progress to artifacts in your workspace. Close the chat, come back the next day, start a new session — the agents pick up exactly where you left off.

You are the reviewer. Agents propose and execute — you approve, reject, redo, or skip. At any point you can ask questions, give instructions, or redirect. The agents work with you, not around you.

What gets provisioned

When you create a workspace from this recipe, Kajoo automatically provisions:


21 specialized agents	Discovery, code migration, content migration, SXA conversion, resolver adapters — each with its own role, skills, and tool set
5 MCP connections	Source XP instance, target XMC instance, source code repo, target code repo, Kajoo internal tools
32 skills	DXP-specific knowledge packages covering XP architecture, XMC SXA patterns, Content SDK 2.0, GraphQL adapters, and more
1 sandbox	A cloud workspace with its own git repo, dev server, and file system — nothing touches your production systems until you're ready

The five phases

The migration runs in five phases. You initiate each one from the Kajoo chat when you're ready.

Phase 1: Discovery          (~5–15 min)
          ↓
    ┌─────┴─────┐
    ↓           ↓
Phase 2:     Phase 3:       (hours — iterative)
Code         Content
Migration    Migration
    │           ↓
    │        Phase 4:       (~30–60 min)
    │        SXA Conversion
    │           │
    └─────┬─────┘
          ↓
       Phase 5:             (hours — iterative)
    Resolver Adapters
          ↓
        Done

Phase	What happens	Duration
Phase 1 — Discovery	Analyzes your XP codebase and content architecture. Produces the artifact foundation every downstream phase depends on.	~5–15 min
Phase 2 — Code Migration	Migrates React/JSS components to XMC Content SDK 2.0, one at a time. Verified live in the sandbox after each component.	Hours (iterative)
Phase 3 — Content Migration	Serializes the full XP content tree — templates, items, renderings — and pushes it to SitecoreAI CMS (XMC). Runs in parallel with Phase 2.	Hours (iterative)
Phase 4 — SXA Conversion	Converts the migrated site structure to SXA Headless — headless tenant, rendering registration, partial designs, page designs.	~30–60 min
Phase 5 — Resolver Adapters	Replaces C# Rendering Contents Resolvers with TypeScript GraphQL adapters, one resolver at a time.	Hours (iterative)

Typical timeline: A 30-component site takes 3–5 sessions spread over several days. Discovery is fast. Code and Content migration are the longest phases and can run in parallel. SXA Conversion is largely automated. Resolver Adapters depend on how many custom resolvers your site uses.

Before you start

What you need

Requirement	Details
Sitecore XP instance	A live or QA XP environment with SPE Remoting enabled and GraphQL configured
SitecoreAI CMS (XMC) instance	A provisioned XMC environment with a starter repository created
Source code repository	Your XP Headless codebase on GitHub or Azure DevOps
Target code repository	A destination repo for the migrated XMC codebase (can be the same repo on a new branch)
Kajoo Agentic workspace	Created from this recipe with all four connectors configured

What to expect

You will be asked to review and approve changes at every meaningful step
Some phases (Code Migration, Resolver Adapters) are iterative — you work through components or resolvers one at a time
Sessions can be paused and resumed at any point — nothing is lost between sessions
The sandbox is isolated — your production XP instance is read-only throughout

How to get started

Complete Environment Setup to prepare your Sitecore XP and SitecoreAI CMS (XMC) environments
Complete Workspace Configuration to connect your environments to Kajoo
Start Phase 1 — Discovery from your workspace chat

What's next


First time?	Start with Environment Setup
Workspace already configured?	Jump to Phase 1 — Discovery