Divi 5 backward compatibility mode: what it costs and how to get out

Most agencies notice backward compatibility mode the same way: a red notice in the admin bar after a Divi 4 to Divi 5 migration, and a speed test that barely moved. The site works. It just isn’t really on Divi 5 yet.

Here is what the mode does, what it costs your clients, and the order we use to get pages out of it.

01What is backward compatibility mode?

It is a safety net. When Divi 5 finds content it can’t convert natively, such as a third-party Divi 4 module or an old layout, it loads the Divi 4 framework so that content keeps rendering and stays editable.

• It switches on automatically when Divi 5 finds legacy modules, layouts or plugins.
• A notice in the admin bar tells logged-in users that legacy content is running.
• Legacy modules can still be edited in the Visual Builder, though settings changes can trigger slower reloads.
• Visitors see a working page. Nothing looks broken.

02What does it cost?

Mostly speed, and the speed is the reason clients pay for the upgrade.

03How do you find the pages that use it?

Use the Divi 5 Migrator, not guesswork. It lists incompatible pages, posts, Theme Builder templates, library items, modules and plugins.

• Run the Migrator scan on a staging copy and export or screenshot the results.
• Group the flags by module, not by page. One plugin often accounts for most of them.
• Check Theme Builder headers and footers first. A legacy module there affects every page.
• Note which pages get the most traffic. Fix those before the long tail.

04How do you get out of it?

Work through each flagged module with one of three fixes.

• Update: the plugin developer has released a Divi 5 version. Update on staging and rescan.
• Swap: a native Divi 5 module does the same job. Rebuild that section with it and match the styling with presets.
• Replace: nothing native fits. Rebuild the feature as a small custom module or with a lighter plugin.

05When is it fine to stay in it for now?

Compatibility mode is not an emergency. It is fine as a short-term state when a key plugin has a Divi 5 version on the way, or when the page gets little traffic. Keep a list, recheck it monthly, and clear the busy pages first. If you are still deciding which sites to move at all, start with our Divi 5 decision guide.

06A fix order that saves time

Not every flag is worth the same. Work through them in this order and the biggest speed gains arrive first.

07What a typical cleanup looks like

Take a brochure site with around 25 pages and two add-on plugins. The Migrator flags a testimonial slider used on six pages and an icon list used in the footer. Here is how that usually goes.

• Rebuild the footer icon list with native Divi 5 modules. Every page drops one legacy module.
• Rebuild the testimonial slider once as a native section, save it to the library, then swap it into the six pages.
• Rescan. Most pages are now native.
• Run a before and after speed test on the five busiest pages for the client report.
• Deactivate both add-on plugins only after the rescan comes back clean.

On a site like this, the work is mostly rebuilding two sections well, not touching 25 pages.

08Stop it from coming back

• Don’t install new Divi 4 add-ons. Check the Divi Marketplace for the Divi 5 compatibility tag first.
• Save native sections to the Divi Library, so the team reuses them instead of old layouts.
• Rescan after big plugin updates, because an add-on update can add or remove support.
• Add a monthly compatibility check to the site’s care plan.

09FAQ