If you run a Divi site, you’ve heard the advice by now: let Divi convert it, check a few pages, and you’re on Divi 5. Here’s the honest version. Divi’s built-in converter really does convert. On a real Divi 4 page we tested, every module turned into a native Divi 5 block. But it doesn’t catch everything. A module from a plugin that has no Divi 5 version stays in an old Divi 4 box inside your Divi 5 site. And the converter says “success” either way, so it never tells you what it left behind.
I’m Dyllon. I run PC Designs here in Texas, and I’ve rebuilt enough Divi sites to know that a half-finished migration isn’t the same as moving. So I built a way to do it for real. Here’s the difference, in plain English.
What Divi’s built-in converter does
Divi 5 is a real step forward, and the converter that comes with it is better than its reputation. It turns Divi’s own modules into native Divi 5 blocks. In our test on a real Divi 4 page, that was every module, with nothing wrapped. It falls short at the edges. Here is what we found it leaves behind or gets wrong:
- Modules from plugins that have no Divi 5 version stay in an old Divi 4 box. If a Divi module carries a setting from a plugin Divi doesn’t know, the whole module stays old. For a Section, that means the whole section.
- Split tests are not converted. Shortcodes in widget areas are not converted. Content that doesn’t start with a shortcode is wrapped as it is.
- About 15 modules lose or change a few settings along the way. Two examples: the link URL and target on a Heading, and the grayscale setting on a Fullwidth Map.
- It reports “success” every time and doesn’t count what it left behind. If you convert in the Visual Builder, it doesn’t save a Divi 4 backup copy either.
So a converted site can still hold a few old-format pieces and a few missing settings. You won’t see them unless you look. If you wrote custom CSS for the old .et_pb_ class names, check that too.
What a checked Divi 4 to Divi 5 migration looks like
A checked migration rebuilds your site page by page as native Divi 5, then proves it. That includes the plugin modules Divi’s converter has to leave in the old format. That’s what PressConduit does. Here’s the short version:
- Divi’s converter: turns Divi’s own modules into native Divi 5 blocks. Keeps plugin modules with no Divi 5 version in the old format, skips split tests, can drop a few settings, and reports success either way.
- A checked migration: backup first, leftover old-format blocks counted, lost settings checked, phone, tablet and desktop compared, plugin modules rebuilt natively, and your sign-off before anything goes live.
And to be clear, this is a migration, not a redesign. It matches your original down to the colors, fonts, and spacing. You’re moving the same site to a better foundation, not starting over.
How the migration works
- Connect your own AI. You bring your own Claude. Your AI does the work, and PressConduit just gives it safe access to your site, so your data stays yours.
- Point it at your site. Tell it what to convert: one page, a single section, or the whole site.
- Get real Divi 5. It rebuilds each page in native Divi 5 that looks just like the original. You review it, then publish.
I migrated a 42-page site in an afternoon
This isn’t theory. I recently converted a 42-page site to native Divi 5 in a single afternoon, page for page, looking exactly like the original. A rebuild like that normally runs a client $3,000 to $8,000 and takes weeks. This one took a few hours, and every URL and SEO setting came through untouched.
Will it look the same, and what about my SEO?
Yes on both. Pages are converted in place, so your URLs, slugs, and SEO settings stay exactly as they are. No redirects to manage, no rankings put at risk. The design is transcribed faithfully, and you check every page before it goes live. And because you end up on one clean framework instead of two, your site is in a much better position to stay fast, which Google and your visitors both care about.
It’s more than a migrator
Migration is just the first thing it does. Once your AI is connected to your site, it can build new pages in Divi 5, run your WooCommerce store, and make everyday edits across your site by chat, all with you reviewing before anything goes live. Not ready to move to Divi 5 yet? It works on your Divi 4 site today, too, so you can put it to work now and migrate whenever you’re ready.
Frequently asked questions
How is this different from Divi’s built-in converter?
Divi’s converter does convert, and it does a good job on Divi’s own modules. It keeps some things in the old Divi 4 format: modules from plugins with no Divi 5 version, split tests, and modules with a setting it doesn’t know. It can also drop a few settings, and it says “success” either way. PressConduit backs up first, counts what was left behind, checks for lost settings, compares phone, tablet and desktop, and rebuilds plugin modules with native Divi 5 modules. Then you sign off.
Will the migration change how my site looks?
No. It’s a faithful migration, not a redesign. Your colors, fonts, spacing, and layout are matched to the original, and you review every page before publishing.
Do I need my own AI?
Yes. You connect your own Claude, so the AI cost is yours and your data stays with you. PressConduit just connects your AI to your site safely.
What happens to my URLs and SEO?
They stay the same. Pages are converted in place, so every URL, slug, and SEO setting is left alone, with no redirects and no lost rankings.
Find out what your conversion left behind
If you’re sitting on a Divi 4 site dreading the move, this is the easy way through. Migrate one site free and see your real, native Divi 5 page right next to the original. Take a look at PressConduit and migrate your first site free, or reach out and I’ll help you plan the move.
