Version Upgrades

Every major version of ExpressionEngine and Craft CMS eventually reaches end of life, and sites running on older versions become progressively more exposed. Security patches stop being released, third-party plugins stop being maintained for the old version, and the gap between what the site is running and what the platform requires grows wider. The longer an upgrade is deferred, the more work it typically involves when it finally has to be done.

Expression 37 has carried out version upgrades across every major release of both platforms, from EE 2 through to the current version and from Craft 2 through to Craft 5. The process is methodical: assess first, scope the work clearly, then carry out the upgrade with thorough testing before anything goes live.

What the Upgrade Process Involves

• A full site audit to assess the current version, all installed plugins and add-ons, and any custom code or templates
• A clear written scope of work before anything begins, outlining what is involved and what it will cost
• Plugin and add-on compatibility assessment, including identification of any that need replacing or rewriting
• Upgrade carried out on a staging environment so the live site is never at risk during the process
• Template and custom code updates required for the new version
• Thorough testing of all site functionality before the upgraded version goes live
• Post-launch monitoring to catch anything that only surfaces under real traffic

Common questions:

Our site has been on the same version for years. Is that a problem?

It is a risk, not necessarily an immediate crisis, but one that grows over time. Older versions stop receiving security patches, and the longer the gap between the current version and where the site is, the more work is typically involved in bridging it. The best time to address it is before something forces the issue.

Will an upgrade affect how our site looks or works for visitors?

Done properly, no. The upgrade process is carried out on a staging environment that mirrors the live site. Everything is tested before the upgraded version replaces the live one. Where a plugin is no longer compatible and has to be replaced, that replacement is tested to ensure equivalent functionality is in place.

We have bespoke add-ons and custom code. Does that make the upgrade more complicated?

Yes, but it is manageable with the right approach. Before the upgrade begins, every piece of custom code is reviewed for compatibility. Where a rewrite is needed, that is included in the scope. Nothing is left untested. Sites with significant custom code simply require more careful scoping and more thorough testing, both of which are built into the process.

How long does an upgrade take?

A straightforward site with few third-party add-ons and standard templates can often be upgraded in a few days. A complex site with multiple bespoke add-ons, heavily customised templates, and integrations with external systems will take longer. Scope is always assessed before work begins, so you have a clear picture of the timeframe before committing.

Can you upgrade a site you did not originally build?

Yes. This is common. We take the time to understand the existing codebase before making changes, which is the only sensible way to approach an upgrade on a site built by someone else. The audit phase exists precisely to surface any surprises before the upgrade work begins rather than during it.

Get in Touch

To discuss an upgrade for your ExpressionEngine or Craft CMS site, call Karl directly on 01924 501 813 or 07771 656 606, or use the contact form.