Claude
Claude Cowork
Cursor
ChatGPT
Codex
Hermes AgentMigrate away from Divi
Divi stores its pages as shortcodes in post_content. That single fact decides what a migration can carry across and what it cannot, so it is where this page starts.
What Divi stores
Divi 4 keeps the whole layout as nested shortcodes inside post_content, so the page is one long string rather than a structured tree. Divi 5 moves to a JSON model, which is why a Divi 5 upgrade and a Divi exit are different jobs and should not be attempted in the same pass.
The part that actually costs time
Shortcode nesting carries no schema, so depth has to be inferred by parsing rather than read. Global modules are references, not content, and a naive conversion inlines them and silently breaks the link between every page that used them.
Carries across
- Text, headings and body copy
- Images and their alt text
- Link targets
- Section and row order
Needs a decision, or a rebuild
- Global modules, which become inlined copies unless mapped first
- Theme Builder templates, which live outside post_content
- Custom module CSS keyed to Divi class names
Where you can go from Divi
Coming the other way, into Divi
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.
