If you have an ExpressionEngine site that is running on an old version, or has been left without proper support, at some point you will face this question: is it better to upgrade the existing site to a current version of EE, or to rebuild it from scratch on a new platform or a fresh EE installation?
The frustrating reality is that the answer you get often depends on who you ask. Generalist agencies tend to recommend rebuilds because that is work they are comfortable quoting for. ExpressionEngine specialists tend to find upgrade paths that others miss. Neither perspective is inherently wrong, but neither is fully impartial either.
Signals that point towards an upgrade
- The site works well for the business. If the content structure, the editorial workflow, and the features all broadly do what you need them to do, the problem is technical debt rather than a platform mismatch. Upgrading addresses the technical debt without disrupting the parts that work.
- The site has years of content and complex data. Migrating a large content database to a new platform is considerably more complex and risky than upgrading within EE. Data loss during migration is a real risk that is often understated in rebuild proposals.
- The main issues are PHP compatibility and security patches. These are upgrade problems, not rebuild problems. A well-executed EE upgrade to the current version resolves both.
- Custom functionality that works. If the site has bespoke add-ons or custom templates that do exactly what the business needs, a rebuild means rebuilding all of that too. That is often where the real cost lies.
Signals that point towards a rebuild
- The site structure no longer fits how the business operates. If the content model was designed for a business that looks quite different from the one that exists today, patching it may create more problems than starting clean.
- The codebase is genuinely beyond rescue. Some EE installations have been modified so heavily, and so badly, over the years that they are genuinely difficult to work with. This is less common than agencies suggest, but it does happen.
- The add-on dependencies are completely unresolvable. Most add-on compatibility issues can be addressed during an upgrade, but occasionally a site depends so heavily on abandoned, unsupported add-ons with no modern equivalent that a rebuild is the more practical option.
- The business is also planning a redesign. If you are going to redesign the site anyway, and the content structure needs rethinking, a rebuild makes more sense than upgrading first and redesigning on top of that.
The questions to ask any developer before deciding
Before committing to either path, it is worth asking any developer you are considering these questions directly:
- Have you seen a site in a similar state to ours that you successfully upgraded? What did that involve?
- What specifically in our codebase makes you recommend a rebuild over an upgrade?
- What is the realistic all-in cost of a rebuild, including content migration and any custom functionality that needs rebuilding?
- What would the upgrade cost, and what would be left outstanding afterwards?
A specialist who knows ExpressionEngine well should be able to answer these questions clearly and specifically. Vague answers about complexity or risk, without concrete explanation of what that means for your specific site, are a warning sign.
Getting an honest assessment
Karl will give a straightforward view of whether upgrade or rebuild is the right option for your specific situation, including a realistic cost comparison of both paths. He has no financial incentive to recommend one over the other. If a rebuild is genuinely the better answer, he will say so. If the site can be upgraded cleanly for a fraction of a rebuild cost, he will say that too.
If you have an ExpressionEngine site and are trying to work out which path is right for your business, get in touch and Karl will take a look.