Disclosure: WP Builder Guide is independent. Some links on this page are affiliate links, which may earn us a commission at no additional cost to you.
Treat a Divi 4 → Divi 5 move as a production migration, not a routine visual update. Elegant Themes recommends staging first and a complete backup before upgrading.
Before migration
- Clone the production site to staging.
- Create a complete backup of files and database.
- Inventory third-party Divi modules and integrations.
- Update WordPress, Divi, and extensions only through a controlled process.
- Record critical forms, ecommerce flows, templates, and scripts that must be retested.
Compatibility mode matters
Elegant Themes says legacy Divi 4 content and third-party legacy modules can continue in backward compatibility mode. That mode loads the Divi 4 framework, so it does not receive the full Divi 5 performance and stability improvements.
After migration
- Check global headers, footers, and Theme Builder assignments.
- Test representative pages across breakpoints.
- Test forms, checkout, search, popups, and tracking scripts.
- Review console/server errors and caching behavior.
- Only move production after the staging site passes your checklist.
Bottom line: If a critical third-party module is not ready for Divi 5, compatibility mode may buy time—but verify its limitations before moving production.
Considering Divi?
See Divi 5Check the current plans, inclusions, and checkout price directly with Elegant Themes.