Phase 4 — SXA Conversion

Phase 4 converts your migrated site structure from XP-style to SitecoreAI CMS (XMC) Headless SXA. This is a multi-step structural transformation that takes the content and templates pushed in Phase 3 and reorganises them into a properly architected SXA Headless site.

Duration: ~30–60 minutes | Orchestrator: SXA Conversion Orchestrator

Requires: Phase 3 — Content Migration complete, plus discovery artifacts from Phase 1

What SXA Conversion does

SXA Conversion runs a sequence of structural transformations, each handled by a specialized sub-agent:

Create headless tenant — Provisions a new headless SXA tenant in SitecoreAI CMS (XMC)
Register renderings — Registers all migrated components as SXA rendering modules under the tenant
Site adoption — Moves the migrated site under the headless tenant and updates all path references
Headless template conversion — Converts XP-style data templates to headless SXA template structure
Shared data safety check — Verifies shared data items are correctly scoped after adoption
Partial Designs — Creates Partial Designs from the source XP layout patterns (header, footer, shared regions)
Page Designs — Creates Page Designs from the source page template structure
Presentation migration — Migrates presentation data — final alignment between the SXA structure and the migrated components

All sub-agents are idempotent — they check their own state and skip work already done. Safe to re-run if the phase is interrupted at any point.

Before you start

Phase 3 — Content Migration is complete
content-migration-state artifact confirms all namespaces pushed
Discovery artifacts from Phase 1 are present

How to run SXA Conversion

Open your project in Kajoo Agentic and start a new chat session
Type "Start SXA conversion" to invoke the SXA Conversion Orchestrator
The agent loads discovery and content migration artifacts
Review and approve decisions as each sub-agent completes its step (see below)
The orchestrator proceeds through all eight steps in sequence
Review the final conversion state and choose to proceed to Phase 5 or stop

What you'll decide

Decision	When
Confirm site adoption	Before path references are updated — review the proposed tenant and site structure
Review site conversion results	After adoption and shared-data safety check
Approve Partial Design plan	Before Partial Designs are created — review the proposed header/footer/region mapping
Approve Page Design plan	Before Page Designs are created — review the proposed page template mapping
Review presentation migration dry-run	Before presentation data is moved — the agent shows the full plan before executing
Proceed or stop after completion	Once all steps are done, choose to move to Phase 5 or stop here

What SXA Conversion produces

Artifact	What it contains
`sxa-conversion-state`	Per-site tracking: tenant, rendering registration, adoption, conversion, and presentation status
`sxa-tenant-state`	Tenant-level state, tracked separately from per-site conversion

Troubleshooting

Issue	Fix
Phase starts but stalls on adoption	Confirm the site name in `migration-get-info` matches the actual Sitecore site name
Rendering registration incomplete	Re-run — sub-agents are idempotent and will skip already-completed registrations
Partial/Page Designs look wrong	Reject the plan and provide guidance — the agent will re-propose
Phase interrupted	Safe to re-run from the start — all sub-agents skip completed work

What's next

Once SXA Conversion is complete, and Phase 2 — Code Migration is also complete, Phase 5 can begin.


Code migration still in progress?	Wait for Phase 2 to complete — Phase 5 requires all components migrated (pending=0)
Both phases complete?	Continue to Phase 5 — Resolver Adapters