User DocsChangelogWebsite
User Docs
  1. Kajoo Agentic Delivery
  2. Recipes
  3. XP → SitecoreAI Migration

Phase 3 — Content Migration

Serializes the full Sitecore XP content tree and pushes it to SitecoreAI CMS (XMC) namespace by namespace — with template remapping and full resume support.

Phase 3 migrates your Sitecore content — templates, items, renderings, layout, and configuration — from your source XP instance to SitecoreAI CMS (XMC). The agent serializes the full content tree from XP and deserializes it into XMC, namespace by namespace.

Duration: Hours — depends on content volume | Orchestrator: Content Migration Orchestrator

Requires: content-discovery-report + code-discovery-report from Phase 1, plus both source and target content connectors configured

⚠️

Hard gate — Phase 3 will not proceed unless both source XP and target SitecoreAI CMS (XMC) connectors are fully configured. Check with migration-get-info before starting.

How Content Migration works

Content migration runs in three internal steps:

1. Setup — The agent loads discovery artifacts, configures the Sitecore CLI serialization module using serialization-config.json, and validates both connectors.

2. Pull — The agent serializes content from your source XP instance — templates, items, renderings, pages, and configuration — namespace by namespace. Each namespace is pulled and staged before any push begins.

3. Push — The serialized content is deserialized into SitecoreAI CMS (XMC), namespace by namespace. After each namespace, you review the result and choose how to proceed.

Large content handling. Timeout is calculated automatically from metadata.itemCount in the discovery report. For datasets over 25,000 items, the agent chunks the operation automatically — no manual intervention needed.

Parallel execution. Phase 3 operates entirely on the Sitecore CMS layer, independent of Phase 2 (which operates on the code layer). Both can run simultaneously in separate chat sessions within the same project.

Before you start

  • Phase 1 — Discovery is complete
  • content-discovery-report and code-discovery-report artifacts exist
  • Source XP connector configured and verified
  • Target SitecoreAI CMS (XMC) connector configured and verified

How to run Content Migration

  1. Open your project in Kajoo Agentic and start a new chat session
  2. Type "Start content migration" to invoke the Content Migration Orchestrator
  3. The agent validates connectors and loads discovery artifacts
  4. Review and resolve any XP-only template issues before the pull begins
  5. The agent pulls content from XP namespace by namespace
  6. The agent pushes each namespace to SitecoreAI CMS (XMC) — review and approve after each one
  7. Handle any template dependency issues as they arise (see below)
  8. Continue until all namespaces are pushed

What you'll decide

DecisionWhen
XP-only template issuesBefore the pull — approve, reject, or defer per issue
Duplicate item remediationDuring pull, if duplicate item IDs are detected
After each namespace pushContinue / Redo / Add Exclusions / Skip / Stop
Template remap proposalsWhen XP templates reference features absent in XMC (e.g. Analytics, Marketing)
Exclusion strategy on push failureExclude and continue / manual fix / broaden exclusion path

Template dependency issues

The most common issue in Phase 3: XP templates that reference Analytics or Marketing features which don't exist in SitecoreAI CMS (XMC).

When this happens, the agent:

  1. Identifies the problematic template
  2. Searches for a compatible remap in XMC
  3. Proposes a remap or exclusion strategy
  4. Waits for your approval before proceeding

This is expected behaviour, not an error. Most XP sites have at least a few templates in this category.

Resuming Content Migration

Progress is tracked in the content-migration-state artifact, which records setup, pull, and push completion per namespace.

To resume: open a new chat session in your project and type "Resume content migration". The agent picks up from the next pending namespace.

What Content Migration produces

ArtifactWhat it contains
content-migration-stateSetup/pull/push phase tracking, namespace push order and completion, metrics per namespace
content-migration-exclusions-logAll exclusions applied — reasons, types, and item paths

Troubleshooting

IssueFix
"Source/target connector not configured"Use migration-set-connectors to configure, migration-get-info to verify
"Duplicate items detected" during pullThe Health Check agent proposes remediation — approve or exclude per item
"Template dependency error" during pushNormal — agent proposes remap or exclusion, you approve
"Timeout exceeded" on large contentAgent calculates timeout from itemCount and chunks automatically for >25k items. If it still fails, use migration-set-connectors to check config
Push fails on a namespaceChoose Redo, Add Exclusions, or Skip — the agent will not proceed without your decision

What's next

Once content migration is complete, SXA Conversion can begin. Phase 4 requires both content migration and Phase 1 discovery artifacts to be present.

Code migration still running?Wait for Phase 2 to complete — both are required before Phase 5
Ready to proceed?Continue to Phase 4 — SXA Conversion

Updated 42 minutes ago