How PostDeploy migrates Divi page builder content
Copy a Divi-built page's content into a new post, or move it with a tool that only knows how to transfer plain post content, and at a glance it looks fine — the layout, the text, the structure are all there. Then you load the page and the images are broken. Not corrupted, not missing from the media library — still pointing at the old site, because of where Divi actually stores the reference.
Divi doesn't reference images the way you'd expect
Most page builders — Elementor among them — store an image reference as an attachment ID: a number that means "whichever file has this ID in the media library." Move the page to another site, resolve the ID to the new site's copy of that file, and the image displays correctly. It's indirection, and indirection is what makes a reference portable.
Divi 4 doesn't do that. A classic Divi image, or a section/row/slide's background image, stores the full source-site URL baked directly into the shortcode attribute: [et_pb_image src="https://old-site.com/wp-content/uploads/2026/08/photo.jpg" ...]. Divi 5's block-based format stores the same plain URL string, just inside the block's JSON attributes instead of a shortcode attribute. Either way, there's no attachment ID to resolve — just a URL that happens to point at a server that isn't this one anymore.
What actually has to happen
Since there's no ID to resolve, the fix has to work the other way: find every URL anywhere in the page's content that points at the source site's uploads directory, bring over the underlying file, and rewrite the exact string once the destination has its own copy at its own URL. That has to work for a plain image, a background image, and every responsive variant Divi tracks separately — tablet and phone background images are their own distinct attributes, not derived from the desktop one.
It also has to be shape-based, not a fixed list of attribute names. Divi has a lot of modules, and enumerating "every attribute that might hold an image URL" by name is the kind of list that's permanently one module behind. Matching the URL's own shape — anything under this site's uploads path, ending in a file extension — finds the reference regardless of which attribute it's sitting in.
The one module that's the opposite case
Divi 4's classic Gallery module breaks the pattern above: it references its images by attachment ID, not URL — a plain comma-separated list, gallery_ids="412,413,414". That's the Elementor-style problem, not the usual Divi one, and it needs the matching fix: resolve each ID against the attachment's real destination copy once that file has actually been migrated, then rewrite the list. A URL-rewriter does nothing for this module, and an ID-rewriter does nothing for everything else — treating Divi as having one single reference format, instead of checking each module on its own terms, is exactly the kind of assumption that quietly drops images without any error telling you why.
What PostDeploy does about all of this
Pro's Divi integration scans a Divi-built page's content for every source-site uploads URL — plain image references and every background-image variant, tablet and phone included — brings the underlying files over, and rewrites each one to the destination's own URL once it's there. The Gallery module's attachment-ID list is handled separately and correctly: each ID is resolved against its own migrated copy, using the same reference-mapping PostDeploy already relies on for Elementor's ID-based references, so a gallery doesn't silently lose images or point at the wrong ones on the destination.
The URL-based rewriting covers both Divi 4's classic shortcode format and Divi 5's block format — a page built in either one gets its image and background references resolved the same way. The Gallery module fix above is Divi 4's classic module specifically; Divi 5's gallery block format hasn't been handled yet.
Try it
PostDeploy Free moves Posts, Pages, and custom post types as plain content. PostDeploy Pro adds the Divi, Elementor, ACF, and WPML reference resolution described here — see the Divi integration page for the Divi 4 vs Divi 5 details.