The short answer

If a Divi 4 to Divi 5 migration looks wrong, start on a staging copy and compare it with the original. Clear Divi's generated CSS cache and other caches first. Then investigate the affected page's custom CSS, legacy modules, templates and responsive settings. A completed migration does not replace testing forms and other important website functions.

First, separate a migration problem from a display problem

Divi 5 uses a different underlying content structure from Divi 4. The Migrator converts supported content, while some unsupported third-party modules can keep running through a backward compatibility layer. That means a successful migration report is a useful milestone, but it cannot tell you that every page looks and behaves as intended.

Before editing an affected page, compare three things: the original Divi 4 page, the migrated page on staging and the same migrated page in a private browser window. Record the exact URL, screen width, symptom and whether the problem occurs in the Visual Builder, on the public page or both. A difference that appears only to one browser may be a cache issue; a difference that appears everywhere needs a closer look.

Keep a full pre-migration backup of the database, uploads, theme and plugins. Divi's own content rollback is useful, but it is not a substitute for a recoverable site backup. Work on staging whenever possible, particularly if the site handles enquiries, orders or bookings.

  • Record the original appearance of the homepage, service pages, contact page and shared templates.
  • Confirm the exact Divi and WordPress versions and any recent plugin changes.
  • Note which pages show a problem and whether logged-out visitors see it.
  • Preserve a restore point before trying fixes.

1. Layouts look broken: clear generated CSS and other caches

Misaligned sections, old fonts, missing styles and differences between the builder and live page can be caused by cached files. Divi 5 generates CSS for performance; after a migration or update, a stale copy can make a correctly saved layout appear broken. Start with cache removal before changing padding or rebuilding a section.

In the WordPress dashboard, open Divi → Theme Options and use the Clear CSS Cache control. Then clear the cache in any optimization plugin, your hosting cache and any CDN used by the site. Finally, open the affected page in a private browser window. Check whether the result changed after each step.

If clearing caches fixes the page, do not add CSS overrides for a problem that is already gone. If it does not, save the symptom and proceed to the specific layout or plugin checks below.

  • Clear Divi 5's CSS cache.
  • Purge page-cache and CSS/JS optimization caches where present.
  • Clear hosting and CDN caches where present.
  • Retest as a logged-out visitor in a private window.

2. Custom CSS no longer works, or applies to the wrong element

Custom CSS written for Divi 4 may depend on selectors, markup or element relationships that have changed. The visible symptom might be a heading with the wrong spacing, a button shifted out of place or a column overflowing on mobile. It is tempting to add another override immediately, but doing so without finding the original rule makes future fixes harder.

Find where the relevant CSS lives. Common locations include Divi → Theme Options → Custom CSS, page-level and module-level Custom CSS, Code Modules and the child theme's stylesheet. On a staging copy, preserve the existing code, temporarily isolate the suspected rules and clear the generated CSS cache after the test. If the symptom disappears, restore the code in small groups until you identify the precise selector or declaration causing it.

Check browser developer tools for the rule that actually wins in the cascade, and inspect its effect at desktop, tablet and mobile widths. Change the smallest responsible rule and verify the shared design elsewhere before publishing. A broad rule aimed at every Divi module can fix one page while changing many others.

  • Identify the affected element and its existing custom CSS.
  • Check whether the selector still matches Divi 5's rendered markup.
  • Test a small, reversible CSS change on staging.
  • Clear generated CSS and review other pages using the same style.

3. Legacy modules and backward compatibility warnings

A legacy warning does not automatically mean the module has failed. Divi 5 can display some unconverted third-party Divi 4 modules using its backward compatibility system. However, an affected page may also load the older Divi 4 framework, so it may not gain the same performance improvements as a page using only native Divi 5 modules.

Review the Divi Migrator's readiness report and identify which plugin or module leaves each page in legacy mode. Then check the plugin vendor's current Divi 5 compatibility information. A native update may exist, or the module may need replacement with an equivalent supported feature. Record the affected pages and test behavior before accepting the migration.

Do not deactivate a business-critical plugin merely to remove a compatibility notice. Removing a plugin can also remove the shortcode or feature that produced visible content. Some third-party products explicitly opt out of Divi 5, in which case the safe next step may be to delay migration or agree a scoped rebuild.

  • Identify the plugin and the exact pages using its legacy modules.
  • Check the plugin vendor's supported Divi 5 version.
  • Test front-end rendering and editing on staging.
  • Decide whether to update, replace, retain temporarily or postpone the migration.

4. Header, footer or Theme Builder templates look different

Some of the highest-impact differences appear in repeated areas: the site header, footer, archive templates, custom post type layouts or global sections. A page can look correct in isolation while a shared template applies to the wrong pages or loses a design detail. Because templates repeat, an error can affect the whole website.

In Divi's Theme Builder, review which template is assigned to each page type and whether its header, body or footer is enabled. Check the default website template as well as any specific assignments. If the navigation is wrong, verify the WordPress menu assignment and the menu module's settings before rebuilding the header.

Compare a normal page, a post, a category/archive page and any custom post type or product template the business actually uses. After a template change, purge the CSS cache and test the public page, not just its editor preview.

  • Check the default and custom Theme Builder template assignments.
  • Verify header and footer visibility on representative page types.
  • Test navigation links, dropdowns, sticky behavior and mobile menu opening.
  • Review global sections and reusable elements on more than one page.

5. Mobile spacing, hidden sections and sideways scrolling

A desktop screenshot cannot establish that a Divi 5 migration is complete. Sections may disappear at narrow widths because of responsive visibility settings, display conditions or custom code. Other elements can remain visible but extend past the viewport, creating sideways scrolling or buttons that are difficult to tap.

Find the screen width where the problem starts. Inspect the section, row, column and module's device-specific values, including width, spacing, alignment and visibility. Then check custom media queries and any CSS that hides or positions the element. Avoid adding negative margins or a blanket overflow rule before identifying what is causing the problem.

Retest the affected section on a real phone if available, at a tablet width and on desktop. Open the mobile menu, use the contact form, and check buttons and overlays. A page is not fixed if the affected section looks correct at one width but becomes unusable at another.

  • Look for content hidden by responsive settings or display conditions.
  • Check for text clipping, horizontal overflow and overlapping controls.
  • Test the mobile menu and every primary call-to-action.
  • Review the affected layout at multiple screen widths.

6. Forms, shops and integrations need functional testing

A layout can look identical after migration while an important interaction is no longer working. For a brochure website that may be an enquiry form; for another business it could be a booking calendar, membership login, product variation selector or checkout. These checks deserve priority over cosmetic polish.

Submit a clearly labeled test enquiry through the actual public form and confirm that the intended mailbox receives the notification. A form success message alone does not prove email delivery. Check any visitor confirmation, redirect, conditional field or file upload that the business relies on.

For WooCommerce or booking systems, use an agreed safe testing method on staging. Verify the relevant product, cart or booking steps without making a real charge or sending accidental customer messages. If the staging site contains copied customer data, handle it carefully and disable or sandbox outbound notifications and payment actions during tests.

  • Submit a test contact form and confirm delivery to the receiving inbox.
  • Check buttons, links, search and navigation.
  • Test booking, membership and e-commerce journeys where applicable.
  • Verify multilingual pages or integrations the business depends on.

7. Some migrated pages remain slow

Divi 5 has a revised architecture, but upgrading does not guarantee a particular loading time or PageSpeed score. A page containing an unsupported legacy module can load the older rendering framework as well. Hosting, media, caching and unrelated plugins still affect performance.

Compare the same important pages before and after the migration under reasonably similar conditions. Note whether slow pages have legacy warnings and whether the delay affects all pages or only one layout. Start with the dependency or asset actually responsible rather than assuming the migration itself is the entire explanation.

If performance is a project goal, define what will be measured and which changes are in scope. Replacing several legacy modules or optimizing an image-heavy site can be separate development work beyond a standard migration.

Should you fix the issues, wait or roll back to Divi 4?

For minor spacing or CSS problems on an otherwise compatible website, a targeted fix may be reasonable. If an essential plugin cannot run on Divi 5, the readiness scan reports extensive legacy content, or the site is in the middle of a critical business period, postponing the migration can be the safer decision.

As of November 2026, Elegant Themes states that Divi 4 will remain supported for at least 12 months after Divi 5's February 26, 2026 public release. That is a planning window, not a reason to ignore the transition indefinitely. Verify the latest support policy when scheduling your own upgrade.

Divi documents a rollback path, but do not assume you can freely switch back after weeks of edits to the Divi 5 version. Restoring older content or a database backup can overwrite newer changes, orders and enquiries. Preserve that newer data and agree a recovery plan before any rollback.

If a high-risk site is still on Divi 4, a readiness assessment and a planned migration may be more valuable than rushing to upgrade immediately.

Post-migration QA checklist before going live

Use a representative page list rather than checking only the homepage. Include each distinct template and important customer journey. Keep screenshots or short notes of anything that needs correction, and repeat the affected test after each fix.

  • Full backup retained and staging migration completed.
  • Divi readiness and legacy-module warnings reviewed.
  • Homepage, service pages, posts and relevant archives compared with Divi 4.
  • Headers, footers, Theme Builder layouts and reusable sections checked.
  • Desktop, tablet and mobile layouts checked for clipping and overflow.
  • Menus, buttons, anchors, search and links tested.
  • Custom CSS and child-theme behavior verified.
  • Contact forms submitted and notifications confirmed in the actual mailbox.
  • Booking, login, shop or other integrations tested safely where present.
  • Important URLs, page content and headings retained as intended.
  • Divi CSS, plugin, hosting and CDN caches purged where applicable.
  • Go-live plan, content freeze and rollback responsibilities agreed.
  • Final public-site checks repeated after deployment.

When professional Divi 5 migration help makes sense

If the site uses mostly native Divi modules and the readiness report is clean, the built-in migrator may handle much of the conversion. A careful website owner with backups, staging and time to test may be able to complete that work independently.

The case for professional help is stronger when the site relies on custom CSS, child themes, many global templates, third-party modules or business-critical integrations—or when a migration has already left pages looking or behaving differently. The value is in assessing the exceptions, making agreed corrections and verifying the live result.

SiteKnot offers scoped Divi 4 to Divi 5 migrations for existing WordPress websites, starting at $299 for eligible simple sites. The final scope is confirmed before paid work begins, and a one-time migration does not require a monthly subscription.

To request help, send the website URL and say whether you are still on Divi 4 or have already migrated and noticed problems. Do not send passwords with the initial enquiry.

Explore Divi 4 to Divi 5 migration.

Official references

Use these references alongside the checks and questions in this guide. Interfaces and provider requirements can change.