Phase 0 — Source Setup

Phase 0 is what the agent does automatically before Discovery can run. It audits your workspace and source instance, surfaces any issues, and fixes them with your approval. Nothing is changed until you confirm.

The manual environment steps — SPE Remoting config, role and user creation, credentials, IIS configuration — are covered in Environment Setup and must be complete before Phase 0 runs.

Duration: ~5 min (Headless) | ~5–30 min (MVC, depending on remediation needed) | Orchestrator: Setup Orchestrator

Applies to: All XP → SitecoreAI migrations

What Phase 0 checks

Phase 0 runs up to three checks depending on your source site type:

1. Workspace identity

Every migration needs a known type (xpheadless2sai or xpmvc2sai), plus source/target connectors and site/app names. Phase 0 collects these once through a single consolidated question and writes them to workspace memory. Every downstream phase reads from this — nothing needs to be re-entered later.

2. SPE version check (#1322)

Older versions of Sitecore PowerShell Extensions have a known file-download bug (issue #1322) that silently breaks file transfers later in the pipeline. Phase 0 confirms your SPE installation is on a safe version before anything else runs.

If a patch is needed, the agent shows you the proposed patch and waits for your approval before applying it.

3. Headless Services install (MVC only)

🔵

MVC source sites only

This check does not apply to Headless (JSS) migrations — Headless Services is already in place.

SitecoreAI cannot read your MVC renderings without Headless Services installed on the source XP instance. The Layout Service it provides is what turns Razor views into the JSON the migrated Next.js app consumes — without it, Discovery cannot inventory your components and Code Migration has nothing to work from.

If Headless Services isn’t installed, the agent presents a recommended package and a short install plan. You approve before anything is installed. On production environments, the agent does not auto-install — it hands you an install request you can give your services team.

Before you start

• Environment Setup fully complete — SPE Remoting configured on both XP and SitecoreAI, credentials ready
• Workspace Setup complete — all four connectors configured and verified
• A project created inside your workspace

How to run Phase 0

1. Open your project in Kajoo Agentic and start a new chat session
2. Type "Start setup" to invoke the Setup Orchestrator
3. The agent asks one consolidated question for workspace identity — migration type, source repo, target app name
4. Confirm before anything is written to workspace memory
5. The agent runs the SPE version check and (MVC only) the Headless Services check
6. Review and approve any remediation the agent proposes
7. Phase 0 produces a green-light readout — proceed to Phase 1

📘

Legacy workspaces

If your workspace was set up before Phase 0 existed, the Discovery Orchestrator auto-acknowledges the prior setup. You can move on to Phase 1 without re-running Phase 0.

What you’ll decide

What Phase 0 produces

A green-light readout for every prerequisite check — Workspace identity, SPE version, and (MVC only) Headless Services. This readout is stored in workspace memory and read by every downstream phase to confirm prerequisites are met before starting.

Check it anytime with migration-workflow-status.

Failure modes

What’s next