Divi 5 launched in February, and if you’re running a WordPress site built on Divi, you’re probably wondering whether it’s time to make the jump. I’ve been migrating client sites from Divi 4 to Divi 5 over the past several weeks, and I want to share what I’ve learned — the good, the tricky, and the things I wish I’d known before the first one.

The short version: yes, the upgrade is worth it. But don’t just push the button on your production site and hope for the best. Here’s why, and how to do it right.

Every Site Has Something That Needs Fixing

This is the first thing I want you to hear: every single site I’ve migrated has had at least one issue that needed attention. That’s not a knock on Divi 5 — it’s the reality of moving any complex site to a new framework version.

The biggest culprit? Incompatible plugins. And I’m not just talking about Divi-specific modules from third-party developers. Standard WordPress plugins can cause problems too. Some of them you can live with if they’re only on a page or two, but others might require finding a replacement altogether.

This is exactly why testing matters so much. You need to find these issues before your live site is affected.

Automated Testing Catches What Manual Testing Misses

Can you test manually? Absolutely. Open every page, click every link, check every form. It works. But automated testing is more thorough because it checks things a human might overlook — broken links buried three clicks deep, subtle layout shifts, assets that failed to load.

My automated testing process runs against the staging site after Divi 5 is installed. It produces a report that covers page status, broken links, and specific recommendations for what needs to be fixed before the site is ready to go live. I share that report with the client so they can see exactly what’s going on and make informed decisions about timing.

The Performance Gains Are Real

This is the part that gets me excited. Divi 5 isn’t just a visual refresh — it’s a genuine performance upgrade, both on the front end for your visitors and in the builder itself for developers.

On one client site, GTmetrix scores went from an F to a C after the migration alone, and after adding WP Rocket we pushed it into the A range. PageSpeed Insights jumped from a 22 to an 85. Those aren’t small improvements — they directly affect how fast your site loads for visitors and how Google evaluates your pages.

And for those of us who build with Divi, the builder experience is night and day. If you’ve used Divi 4 for any length of time, you know the pain: click “Edit with Divi,” go get a cup of coffee, come back, and hope it loaded without flashing and reloading. Divi 5 loads the builder fast. You click, you’re in, you’re working. It’s the difference between dreading builder work and actually enjoying it.

My Migration Process: A Seven-Step Checklist

I follow a structured checklist for every migration. If everything goes smoothly, it’s really about five steps, but the full process accounts for the fixes that are almost always needed. Here’s the high-level flow:

Start with a complete backup of the production site. Then set up a staging environment and install Divi 5 there — never on the live site first. Run automated testing on the staging site to identify issues. Fix whatever the report surfaces, then share the results with the client. Once everything looks good, schedule a time to migrate the production site, ideally during off-hours to minimize any disruption.

I have this checklist available on my website, and I’ve also built a self-assessment tool that helps you decide whether a DIY migration makes sense for your situation. It factors in your site type, the potential cost of downtime, and whether a flat-rate professional migration might be the safer bet.

Why Consider Migrating Now

Divi 5 just launched, and I understand the instinct to wait. But the performance improvements alone make a strong case for moving sooner rather than later. Your visitors get a faster site, Google sees better performance metrics, and you (or your developer) get a dramatically better building experience.

The key is doing it safely: use a staging site, have backups in place, and don’t rush the process. Whether you do it yourself or bring in a professional, those fundamentals don’t change.

Ready to Make the Move?

If you’re considering the migration, my biggest piece of advice is simple: don’t do it on your production site without testing first. Set up staging, run your tests, fix what needs fixing, and then schedule the cutover. It’s the difference between a smooth transition and an emergency at 2 AM.

I’ve been building with Divi for years, and after waiting three years for Divi 5, I’m glad I stuck with it. The improvements are real and they’re worth the migration effort.