Plan a website content migration with AI
Map old addresses, prepare a cutover checklist and agree when to roll back. Give the team a way to test what visitors will actually encounter after the move.
Plan a website content migration with AI when changing the CMS, domain or address structure could strand older pages and downloads. The content-migration skill starts with an inventory of the existing site. It then connects each source address to a destination or an explicit decision about retirement.
Imagine a guide that no longer appears in navigation but is still linked from hundreds of confirmation emails. A homepage check after launch will miss it. The migration plan can put its old address in the redirect map and add it to the first round of checks.
What it does
- Build an inventory from authorised CMS exports, sitemaps and relevant traffic records.
- Separate content to keep, consolidate, redirect or retire.
- Prepare backups, an editing freeze and a named cutover owner.
- Check redirected addresses, public assets and important integrations.
- Set a rollback threshold and monitor unresolved errors after launch.
Install and use
- Install the skill in a compatible agent. For planning, provide authorised site exports and addresses. Live cutover needs CMS, hosting and applicable DNS access; header checks use curl.
- Ask, “Build the map and a staging checklist for our help centre move. Flag pages with no agreed replacement.”
- Test representative journeys on staging, agree the switch and rollback decisions, and schedule checks after the change.
FAQ
Source
Made by RampStack Co. Original skill: content-migration, published on GitHub under the MIT licence.
View on GitHub