Claude
Claude Cowork
Cursor
ChatGPT
Codex
Hermes AgentMigrate away from Brizy
Brizy stores its pages as Brizy JSON. That single fact decides what a migration can carry across and what it cannot, so it is where this page starts.
What Brizy stores
Brizy stores its own JSON structure describing a component tree. It is self-contained and versioned, which means a conversion can rely on the shape rather than sniffing it.
The part that actually costs time
Brizy leans on its own styling primitives, and many of them have no direct equivalent elsewhere. The structure converts cleanly; the visual result is where the work goes.
Carries across
- Component structure
- Text and media
- Link targets
Needs a decision, or a rebuild
- Brizy-specific styling primitives
- Global blocks
- Animation and interaction settings
Where you can go from Brizy
How the migration actually runs
The agent works on a duplicate of the page, not the live one. The original keeps serving while the converted copy waits for review, and every write captures a before-state so a bad conversion is one call to undo. Nothing publishes without a human approving it.
