Case study · Legacy CMS modernization

Legacy rescue: moving an ExpressionEngine 1.6 site to modern hosting

A 2000s-era EE 1.6 site had to leave a host that no longer offered PHP 5.6. We moved its content into a current ExpressionEngine install.

Client
A long-running website built on ExpressionEngine 1.6 (name withheld)
Technologies
ExpressionEngine 1.6Current ExpressionEngineContent import

Project overview

The site had run on ExpressionEngine 1.6 for many years. Its new host no longer offered PHP 5.6, which EE 1.6 depends on.

The challenge

Keeping the site running on an unsupported PHP version was no longer possible, and stepping through every ExpressionEngine version would have been slow and risky.

Technical challenges

  • ExpressionEngine 1.6 needs PHP 5.6, which the new host does not offer.
  • Content had to survive the move intact.

Our approach

  • Set up a current ExpressionEngine install instead of chasing an unsupported stack.
  • Imported the old entries into the new install.