Move a CMS site to code and Markdown
Use Cursor agents to export CMS content, convert it to Markdown, and refactor the site in parallel.
- What they did
- Lee Robinson used Cursor to plan a move of cursor.com away from its CMS. The agent outlined a workflow that reused the CMS API key to export content, check it, turn it into Markdown files in the repo, and place images and videos in object storage. After about 10 agent runs got most of the job done, they sent the agent at pages that still differed from production and used browser screenshots to compare each one.
- How it went
- The migration finished in three days and cost $260.32 in tokens, instead of the 1-2 weeks Lee expected. It included 344 agent requests and 67 commits, with roughly +43K and -322K lines changed. Builds ended up twice as fast, but the last 20% of the pages took most of the time.
- Tips
- Plan for the hard part to be the pages that do not match production yet. Working page by page with screenshot checks helped close that gap.
Try it yourself with Cursor
I want to move [site or repo] from [CMS name] to plain code plus Markdown. First, map out a safe migration plan and show it to me before changing anything. Use the CMS API or export tools to pull the content, verify the export, convert posts and pages into Markdown files in the repository, and update the app so it reads from those files. Use subagents where that helps, but stop and ask before any irreversible step, including deleting CMS code, removing integrations, sending anything, or publishing changes. After each major step, report what changed, what still differs from the live site, and anything you could not migrate. Then compare pages against [production URL] using screenshots and fix mismatches one by one.
Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.
1 more report of this
Get 3 agent uses like this every morning
With the day's top AI news. Free, and one click to unsubscribe.
Related agent uses
Assign PRs and bug fixes across Cursor sub-agents
A Cursor coordinator tracked incoming pull requests and live bugs, sent sub-agents after each issue, and kept the user updated along the way.
Copy an existing module’s structure into a new one
A commenter used Cursor to scaffold a second module, but it missed the pattern because it did not load the source module’s files.
Hand small repo fixes to Cursor agents
A developer used Cursor agents to chip away at a daily batch of repo maintenance, bug fixes, and minor features.
Let Cursor draft a project app in a 24-hour loop
A developer let Cursor work for a full day on a project tracker, and it finished with a usable but unfinished result.
Use Cursor to make a custom invitation site
Fabio Zapata had Cursor assemble a local invitation site with motion, images, and page links, using prompts instead of hand-coding at first.
Flag coding conflicts before agents edit
They set up a local layer that makes coding agents announce planned changes so overlapping architecture work gets caught early.