Quick Answer
Before replacing a Divi menu plugin, inventory every label, destination, hierarchy and display condition in the existing navigation. Identify whether the items live in a WordPress menu, individual builder modules or plugin-managed records. Reconcile that inventory with the replacement on a protected copy before disabling or removing the old extension.
A new header can look complete while omitting a utility link or sending a child item to a demonstration page. A destination record gives the team something concrete to compare during a menu change.
Identify where the current items are stored
Record the installed Divi and extension versions, the active header or other template, and the editor used to maintain its items. Inspect the actual source rather than assuming every menu plugin reads the same WordPress records.
The official Divi 5 Menu Module guide documents selecting a WordPress menu in the Content settings. A third-party extension or individually built navigation can have a different source. Verify the specific implementation and supplier instructions.
Include separate desktop and mobile structures if the site maintains both. Also inspect secondary navigation, footer menus and any utility links affected by the planned replacement.
Create a destination and condition inventory
| Record field | What to preserve |
|---|---|
| Label and hierarchy | The visible wording, parent item, order and level. |
| Destination | The actual URL or action, including any meaningful fragment or approved parameter. |
| Source record | The WordPress menu, builder module or extension setting an editor must change. |
| Display condition | The applicable template, screen arrangement or account state, where relevant. |
| Interaction role | Whether the item navigates, reveals children or uses separate controls for those jobs. |
| Replacement match | The corresponding new item, tested destination and any intentional approved change. |
For an illustrative services menu, keep the Services overview destination and each child service destination distinguishable. Record a show/hide control separately from a link so the replacement does not accidentally remove the overview route.
Reconcile the replacement with the inventory
Work on a separate review copy with a preserved current header and required records. Build the intended replacement from the approved inventory. Mark each item as matched, intentionally changed or unresolved.
Follow the rendered links, including later or conditionally displayed items. Check the final destination and the page meaning, not merely whether a link opens. Inspect the mobile version separately when it uses different records.
The custom Divi navigation guide covers dropdown controls, states and keyboard behavior. Use those interaction checks alongside the record reconciliation; neither replaces the other.
Plan removal after preserving the actual data
WordPress’s plugin management documentation distinguishes deactivation and deletion. Check the particular extension’s storage and uninstall behavior before assuming its records will remain usable after removal.
Keep a recoverable copy and any supported export required for the approved change. Record where future editors will maintain the new navigation. The plugin evaluation guide covers broader adoption questions, while a WordPress design scope can define the header replacement and acceptance work.
Key Takeaways
- Identify the actual navigation data source.
- Preserve labels, hierarchy, destinations and conditions.
- Reconcile every replacement item and rendered link.
- Verify storage and removal behavior before retiring the old extension.
Frequently Asked Questions
Will a new menu plugin automatically use all existing items?
Verify its supported source and actual configuration. The current navigation may use WordPress records, individually built items or extension-managed data.
Does a matching screenshot prove the replacement is complete?
No. Compare the inventory, follow destinations and inspect applicable mobile and conditional versions.
Should I delete the old plugin before checking its data?
Preserve required records and a recovery route first. Confirm the specific extension’s removal behavior on a protected copy.

