AI Services Market › Use cases › Software & DevOps
Software & DevOpsDone with Cursor 2026-10-22
Migrate a website from a CMS to raw code and Markdown
Lee Robinson used Cursor agents to move cursor.com off its CMS in three days for $260 in tokens, with subagents handling a broad refactor.
- What They Did
- Lee planned the migration with Opus 4.5 in Cursor. The agent suggested using the existing CMS API key to write scripts that export content, validate it, convert it to Markdown files in the repo, and upload images and videos to object storage. About 10 runs got it 80% of the way. He then ran an agent on each mismatched page, using browser screenshots to compare against production. Subagents handled the wider refactor in parallel.
- How It Went
- It took three days and $260.32 in tokens, against his estimate of 1-2 weeks. That covered 344 agent requests and 67 commits (+43K/-322K lines). Builds got 2x faster. The last 20% took most of the time.
- Worth Knowing
- Expect the final 20% (pages that don't match production) to take most of the effort. Per-page agent runs with screenshot comparison were how he closed that gap.
Try it yourself with Cursor
I want to move my website at [repo or folder] off [CMS name] and into plain code with Markdown files for content. First export the existing content from [CMS or export location], then use subagents to convert pages and posts into Markdown and update the templates and routes to read from those files. Finished means the site builds locally, the pages match the originals, and you give me a list of anything you could not migrate. Show me the plan before you delete any CMS code or integrations.
Do this with a skill.
These AI Services Market playbooks do this exact job.