A week of copy-paste, or something that reads
A WordPress export is not a Webflow import. The posts came out as HTML soup — inline styles, shortcodes, image tags pointing at a media library that was about to stop existing — while Webflow wanted clean rich text, a slug, an excerpt and references to CMS items that had to exist first. Done by hand it is the same three decisions repeated a few hundred times, which is exactly the work worth handing over.
What the agent was actually for
Not the moving. Scripts have moved data between two APIs for thirty years. The agent earned its place on the judgement calls a script cannot make: which of a post's five tags are real categories and which are noise, what the excerpt should say when the original had none, whether a block of markup is a pull quote or a heading somebody bolded instead.
Where it needed a leash
Early 2025 meant no tool loops worth the name, so it ran as a pipeline — read, propose, validate, publish — with a schema at the end that refused anything malformed. That last gate mattered more than the model did. Allowed to publish directly it would now and then invent a category that had never existed, and a rejected write is a retry while a bad write is a cleanup.
What carried over
The shape outlived the migration: let the model do the reading and the judgement, let ordinary code do the writing, and put something between them that is allowed to say no.