Migrating to Divi 5 is a lot like moving house. Except the house is a database, the boxes are shortcodes, and one wrong move means your hero section ends up in the kitchen.
Here is the short version. Back up your site. Do the migration on staging first. Update WordPress, Divi, and every plugin before you start. Check plugin compatibility in the Divi 5 Migrator. Click migrate. Test everything. This whole Divi 5 migration guide is the long version of that sentence.
Most sites migrate in under an hour. Most broken sites skipped one of those steps. (Yes, I know which step people skip. It changes every time. That is the problem.)
TL;DR: Back up first, migrate on staging, audit third-party plugins with the Divi 5 Migrator's compatibility check, then migrate live. Rollback exists via the Restore Divi 4 Content button, but it erases anything you built in Divi 5 afterward. Slow is smooth. Smooth is fast.
Most migration horror stories start with one skipped step
Every few weeks someone posts in the Divi community that their migration "broke everything." I read these threads the way some people read car crash reports. Professionally.
Almost none of those disasters come from the Migrator itself. The Migrator is actually conservative. It checks your site, shows you blue checkmarks for compatible modules and orange warnings for anything unsupported, and waits for you to confirm.
The disasters come from the setup. No backup. No staging. A third-party Divi extension that hasn't been updated since 2022. The Migrator can protect you from a lot of things. It cannot protect you from a plugin its author abandoned before Divi 5 existed.
That is the whole thesis of this guide. The migration is easy. The preparation is the job.
Do the boring work before you touch the Migrator
Three things happen before anything Divi-related. No exceptions. I have been building Divi sites for years, and I still do all three every single time. Mostly because the one time I considered skipping them, I remembered why I don't.
1. Back up everything. Full database and files. Use your host's backup tool, UpdraftPlus, or whatever you trust. Test that the backup actually restores. A backup you have never restored is a rumor, not a backup.
2. Update WordPress first. Divi 5 expects a current WordPress install. An outdated core is a classic source of weird, unreproducible errors.
3. Update Divi and every plugin to the latest versions. Migration problems love to hide inside outdated plugins. Update everything on staging first, then on live, and check for fallout before you migrate anything.
Also write down your list of Divi-specific extensions. Third-party modules, layout packs, add-ons. You will need that list in the compatibility check, and memory is a terrible place to store it.
Staging is not for cowards
You could migrate directly on your live site. Technically. The same way you could change a tire on a moving car.
Use a staging environment instead. Two easy options:
| Option | Cost | Best for |
|---|---|---|
| Your host's staging feature | Included with most decent hosts | Production sites where downtime costs money |
| WP Staging plugin (free version) | $0 | Any site, especially cheap shared hosting |
Clone your live site to staging. Run the entire migration there. Break staging, not your business.
(I have strong opinions about staging. My therapist is aware of them.)
One detail people miss: when you test on staging, test the boring pages too. The checkout. The forms. The archive pages. The page you built in 2021 and never looked at again. That one is always where the problem lives.
Install Divi 5 and let the Migrator check your homework
On staging, install Divi 5. Two ways:
- From the Divi dashboard inside WordPress, if your membership is connected.
- Or Appearance > Themes > Add New > Upload Theme, using the Divi 5 ZIP from your Elegant Themes account.
Once Divi 5 is active, go to Divi > Divi 5 Migrator. This screen is the closest thing the migration has to a safety inspection.
- Blue checkmarks mean a module or extension is fully compatible.
- Orange warnings mean something is unsupported or only partially supported.
Read every orange warning. Not skim. Read. Each one is telling you exactly what will misbehave after the migration. If an abandoned plugin is flagged, decide now: replace it, live without it, or wait.
If your site is mostly native Divi modules and well-maintained plugins, this screen will be a wall of blue. That is the green light. (Metaphorically. The checkmarks are blue. I am aware of the mixed metaphor.)
Clicking "Migrate This Site to Divi 5" is the easy part
Everything up to here was preparation. The migration itself is one button: Migrate This Site to Divi 5.
The Migrator converts your Divi 4 layouts into the Divi 5 structure. Depending on the size of the site, this takes minutes. Grab a coffee. Do not close the tab, do not refresh, do not suddenly remember an urgent email.
When it finishes, start testing. In this order:
- Homepage and your top 5 pages by traffic.
- Every page that makes or collects money — checkout, forms, bookings.
- Headers, footers, and anything built in the Theme Builder.
- Mobile and tablet views. Migration occasionally shifts responsive settings.
- Contact forms. Submit one. Then submit another.
If everything passes, repeat the whole process on your live site. Same order. Backup, updates, install, check, migrate, test.
If something fails, you have two options. Fix it on staging until it passes, or roll back. Both are covered below.
Building something new in Divi 5 while you decide? The Loop Builder is the feature worth learning first. Our Divi 5 Loop Builder guide walks through real dynamic content examples.
Backward compatibility mode is a safety net, not a destination
Here is the part most migration guides skip, and it matters.
Divi 5 includes a backward compatibility mode. Modules that are not yet supported in the new builder keep working through shortcodes, so your pages do not go blank. Content survives. The site stays up.
That sounds perfect, so let me ruin it slightly. Backward compatibility mode is a waiting room. Your content sits there, rendering, but you cannot edit it properly in the Divi 5 visual builder until the module gets support. On a big site with several unsupported extensions, you can end up running two versions of your layout logic at once. That gets confusing about week two.
So treat it as a bridge. Check the changelog of flagged plugins regularly. When support lands, update and re-test. Your goal is a site fully native to Divi 5, not one on long-term life support.
If something breaks, you can roll back. Mostly.
This is the safety net Elegant Themes built in, and it is genuinely good.
Inside the Divi 5 options there is a Restore Divi 4 Content button. One click restores your pre-migration layouts. Then you reinstall the Divi 4 ZIP from your account, and your site is back where it started.
One catch, and it is a big one. Any edits you made in Divi 5 after migrating are gone. Rollback restores the Divi 4 snapshot. It does not merge. So if you migrated, spent three days redesigning your homepage in the new builder, then rolled back — those three days are now a learning experience.
That is why the rollback plan matters most in the first week. Migrate, test hard, decide fast. If it is broken, roll back while the cost is still small.
And keep that pre-migration backup from step one. The built-in restore is excellent. Your own backup is the second opinion.
Updates work differently after the migration
Small but important. Divi 4 and Divi 5 are on different update tracks.
After you migrate, make sure your site is receiving Divi 5 updates. In Divi > Dashboard, look for the update settings and confirm the Enable Divi 5 Updates option is active where offered. If you stay on the Divi 4 track while thinking you are on Divi 5, you will miss fixes for the new builder.
While you are there, note your version number. If something behaves oddly later, "which version am I on" is the first question any support thread will ask. (It is also the first question I ask myself, usually while already knowing I am on the wrong one.)
This is also a good moment to look at performance. Divi 5 is faster than Divi 4 out of the box, but only if you are not carrying old optimization hacks that now fight it. Our Divi 5 speed optimization tips cover what to clean up.
My take: the Migrator is good enough that waiting is costing you
Nine out of ten migration failures I see trace back to one thing: third-party plugin debt. Not the Migrator. The Migrator has gotten boring, in the best possible sense. Predictable. Careful. It shows you the problems before you commit to them.
So here is the opinion. If your site runs mostly native Divi modules and maintained plugins, there is no strategic reason to wait. The longer a site sits on Divi 4, the more Divi-4-only habits and workarounds get baked into it, and the heavier the eventual migration becomes. A site migrated this month is an easier migration than the same site migrated next year.
The numbers back this up from my own work. Clean sites — native modules, current plugins, full backup — migrate in under an hour of hands-on time. Sites carrying five-year-old add-ons take three hours or more, and almost all of that is untangling extensions, not the migration itself. The Migrator is not the bottleneck. Your plugin list is.
If you have not looked at what changed between the two versions yet, read our Divi 5 vs Divi 4 comparison before you migrate. Knowing what the new builder does differently makes the post-migration testing a lot less confusing.
Do not migrate yet if your site looks like this
Time to talk you out of it, conditionally. Skip the migration for now if:
- A revenue-critical plugin shows orange warnings and has no Divi 5 support announced. Fix the dependency first. A store that cannot check out is a very fast way to lose more than a migration delay costs.
- You have no staging environment and no way to create one. Migrating blind is not bravery. It is a scheduled outage.
- Your site runs on a PHP version older than Divi 5 expects. Update PHP first, test, then migrate. One major change at a time.
- You are mid-launch on a client project. Finish on Divi 4. Ship. Migrate when the pressure is off. A migration during launch week is how you discover bugs in front of the client.
None of these are permanent. They are all "not today" answers, not "never" answers.
The mistakes that break migrations
A short list, because the list is short.
- No backup, or an untested backup. The classic. It never gets old because it never gets learned.
- Migrating live first. Staging exists. Use it.
- Ignoring orange warnings. Every warning is a spoiler for something that breaks later.
- Testing only the homepage. The broken thing is never the homepage.
- Waiting weeks to decide. Rollback erases Divi 5 edits. Decide fast, while rolling back is still cheap.
Straight Answers
Will migrating to Divi 5 delete my content?
No. The Migrator converts your layouts without destroying content, and backward compatibility mode keeps unsupported modules rendering via shortcodes. Take a backup first anyway, because "should be fine" is not a backup strategy.
How long does the Divi 4 to Divi 5 migration take?
The migration click takes minutes. Budget 1 to 3 hours for the full process: backup, staging, plugin audit, testing. Extension-heavy sites sit at the long end.
What happens if a plugin is not compatible with Divi 5?
The Migrator flags it with an orange warning before you commit. You can still migrate through backward compatibility mode, but plan to update or replace the extension.
Can I roll back to Divi 4 after migrating?
Yes. Click Restore Divi 4 Content, then reinstall the Divi 4 ZIP. Anything you built in Divi 5 after migrating is lost, so roll back early if you are going to.
Does the migration cost anything extra?
No. Divi 5 is included in your Elegant Themes membership — $89 per year, or $249 for the lifetime license. No upgrade fee.
Should I migrate all my client sites at once?
No. Staging first, then one low-stakes site, then the rest. Batch migration is how horror stories get written.
The Last Word
Migrating to Divi 5 is not the nerve-wracking job the forums make it sound like. Backup, staging, compatibility check, migrate, test. Five steps. The Migrator does the heavy lifting, backward compatibility mode catches the stragglers, and the restore button is there if the migration and your site turn out to be incompatible.
If you would rather someone else carry that responsibility, we do Divi migrations for a living. Send your site over and we will audit the plugin list before touching anything. Or if you want to do it yourself and just need the theme, Divi is here — $89 a year, or $249 once and never again.
Either way: back up first. We will assume you did. But we will also ask.