If your website is running on ExpressionEngine 4 or 5, it may look fine on the surface. But underneath, you are carrying costs that most business owners do not see until something goes wrong. This is not about upgrading for the sake of it. It is about understanding what your current situation actually means.
PHP compatibility is already a live issue
ExpressionEngine 4 and 5 were designed to work with PHP 7.x. PHP 7 reached end of life in November 2022. Most hosting providers have since moved to PHP 8.x, and many have dropped support for PHP 7 entirely. If your hosting is still running PHP 7 to keep your site working, you are running unsupported server software with known security vulnerabilities. If your host has upgraded to PHP 8 and your site has not been updated, you may already be experiencing errors or functionality quietly breaking.
You are not receiving security patches
Packet Tide do not issue security patches for versions 4 and 5. If a vulnerability is discovered in those versions, there is no fix coming. This is not a theoretical concern. CMS platforms are regularly targeted by automated scanning tools looking for known vulnerabilities. A site running an outdated, unpatched CMS is a significantly easier target than one running a current version.
Addons are no longer being maintained for old versions
The ExpressionEngine addon ecosystem is built around third-party developers. Most of those developers have moved on to supporting EE 6 and EE 7 only. If you need to update or replace a critical addon, such as a form handler, a custom field type, or a third-party integration, you will find that options for EE 4 and 5 are either unavailable or no longer receiving updates themselves.
The cost of waiting is compound
Every month you stay on an old version, the gap between your installation and the current release grows. A migration from EE 5 to EE 7 today is a manageable project. A migration from EE 5 to EE 7 in two years, after your PHP situation has deteriorated further and more addons have fallen out of support, is considerably more involved. The longer the delay, the more the cost of eventual remediation grows.
What to do about it
Start with a clear picture of where you stand. What version of EE are you running? What PHP version is your server on? Which addons are you using and when were they last updated? If you cannot answer those questions yourself, a proper audit will answer them quickly. From there, you can make an informed decision about timing and approach rather than waiting for something to break.