ECS 4.x is a structural update. The features are still familiar, but the way they are organized is cleaner: modules, activation states, and more explicit responsibilities.
1. Check requirements first
- WordPress 6.2 minimum, with 6.5+ recommended.
- Elementor 3.18 minimum.
- PHP 8.0 minimum, with PHP 8.2+ recommended.
Elementor Pro is required for workflows that depend on Pro widgets, such as Loop Grid. ACF Pro is required only when Dynamic Repeater reads from an ACF Repeater source.
2. Back up and stage
Before updating production, create a full backup and test on staging. This matters most on sites with custom loop templates, global color systems, or heavy Elementor template usage.
3. Update and activate intentionally
After updating, open ECS → Modules. Enable the modules the site actually uses:
- layout modules such as Container Layout and Loop Custom Layout,
- workflow modules such as Style Templates and JSON PowerEdit,
- design-system modules such as Color Schemes, Font Schemes, Alternative Site Logos, and Custom Look & Feel,
- data modules such as Dynamic Repeater.
4. Re-test templates
- Open pages that use Loop Grid and Loop Custom Layout.
- Check containers using Slider, Grid, or Custom Layout mode.
- Verify dark mode if Dark Mode Colours is active.
- Review repeater widgets populated by Dynamic Repeater.
- Preview Custom Look & Feel conditions across relevant pages.
5. Regenerate Elementor CSS
After a major update, use Elementor → Tools → Regenerate CSS. This clears stale generated files and avoids chasing visual issues caused by old CSS output.
6. Sign off with the content team
A migration is not done when the developer view looks correct. The Elementor editor should still feel predictable for the people maintaining the site. Ask them to edit a representative page, update a widget, and preview the result.
Final checklist
- Front end verified on desktop, tablet, and mobile.
- Editor workflow verified.
- Active modules documented.
- Backups retained until the site is stable.
- Support notes updated for the new module names and locations.
The upgrade is easiest when it is treated as a controlled module review, not just a plugin update.