ExpressionEngine to Wagtail Migration
A considered path off ExpressionEngine, without losing years of content.
ExpressionEngine served many organisations well for a long time, but ongoing support has become harder to find. We've migrated a number of long-running EE sites to Wagtail — mapping legacy channels and templates onto a modern content model, and moving the content itself without losing URLs, SEO value or editorial history.
How the migration works
-
Content & URL auditing
Understanding exactly what exists before deciding what to keep.
-
Channel-to-model mapping
Translating EE channels and fields into a clean Wagtail content model.
-
Automated content migration
Scripted migration of entries, not manual copy-and-paste.
-
Redirect mapping & SEO preservation
Protecting the search visibility you've already earned.
-
Editor retraining
A smooth handover for the people who'll use the site day to day.
How we'd work together
-
Audit & content mapping
Reviewing existing channels, templates and URLs.
-
Data migration & scripting
Extracting and transforming content into the new model.
-
Rebuild & design
Building the new front end around the migrated content.
-
Redirects & QA
Checking every migrated page and mapping old URLs to new ones.
-
Launch
A carefully sequenced go-live to minimise disruption.
-
Handover
Documentation and training for your editorial team.
Featured work
Frequently asked questions
Not if it's done properly. Careful URL mapping and redirects are a core part of every migration we run, specifically to protect the SEO value you've built up over the years.
Usually the great majority of it. We write migration scripts tailored to your specific EE channels, so structured content moves across automatically — freeing up time to focus on anything that genuinely needs a human eye.
Yes. Some organisations prefer to migrate section by section rather than all at once — we can plan a phased approach if that suits your team better.
Let's work together
Nick Lee











