Moving from Sitekick AI CMS to Studio

claude mcp add --transport http sitekick-docs https://docs.sitekick.ai/mcp

codex mcp add sitekick-docs --url https://docs.sitekick.ai/mcp

{
  "mcpServers": {
    "sitekick-docs": {
      "url": "https://docs.sitekick.ai/mcp",
      "type": "http"
    }
  }
}

Moving from Sitekick AI CMS to Studio

There is no forced migration. Sitekick AI CMS keeps working, and your CMS sites keep running exactly as they are. Moving to Studio is a choice you make when — and only when — it fits.

What moving means

Moving to Studio is really starting a Studio site: you write a brief (describe the business — your CMS site is an excellent reference), Studio drafts the new site, and you review it. You keep your CMS site live the whole time, then point your domain at the Studio site when the new one is ready.

Nothing is deleted in the process. If the Studio site is not ready on the day you planned, the CMS site simply keeps serving your visitors.

What carries over

• Your domain — the same domain can serve the Studio site instead.
• Your knowledge — the copy and structure of your CMS site are the best raw material for a Studio brief.
• Your account — you use the same Sitekick account to sign in.

A sensible order of operations

1. Keep your CMS site running.
2. Start a Studio brief in parallel, using your CMS site as reference material.
3. Review and revise the Studio draft until it is genuinely better — not just newer.
4. Connect your domain to the Studio site.
5. Retire the CMS site when you are confident in the replacement.

When not to move

If your CMS site is deeply customized, you depend on specific CMS workflows, or hands-on editing is the part you enjoy — stay. Studio is built for people who want the work done for them; CMS is built for people who want to do it.

See Choosing between Sitekick AI CMS and Studio for the fuller comparison.