Migrating From WordPress
Version 1.2.0
What actually changes moving off WordPress, and what doesn't need to.
What maps over cleanly
Posts, pages, and their basic fields — title, date, tags — translate directly to Carapace's content model: one entry per post, a JSON metadata file plus an HTML body. If your posts are already reasonably clean HTML (not deeply nested shortcodes or page-builder markup), most of the actual writing carries over with light editing to fit the allowlist.
What doesn't, and why
Plugins are the real gap, and it's worth being direct about it: there's no plugin ecosystem, and there isn't going to be one. Carapace's safety model depends on a small, enumerated set of what content can express — a plugin system that lets arbitrary code run against your content would work against the same guarantee that makes agent-authored publishing safe in the first place. If your site leans on WordPress plugins for core functionality (forms, e-commerce, membership), that functionality doesn't have a direct equivalent here.
The admin dashboard doesn't carry over either, by design — there isn't one. Editing happens through a conversation with an AI agent instead.
If you need highly transactional data — e-commerce, complex user accounts, anything relational beyond content — WordPress with the right plugins is still a better fit than reshaping that into a content system that deliberately doesn't do databases.
The actual migration path
Export your posts, convert them to clean HTML (most WordPress export tools get you most of the way), and bring them in through the same MCP tools you'd use to write new content — there's no separate bulk-import mechanism today, so a real migration means feeding posts in as content, not running a converter script against the repository directly. For a small-to-medium blog, this is a real but bounded amount of one-time work, not an ongoing maintenance cost afterward.