eZ Publish to Ibexa Migration for Content-Heavy Websites

Your eZ Publish site isn't dead — but it needs a future.

eZ Publish served you well. But now you're stuck: PHP versions you can't upgrade, hosting providers asking uncomfortable questions, security patches that stopped coming years ago.

You need to move. The question is: where and with whom?

We migrate eZ Publish sites to Ibexa OSS

Ibexa OSS is the direct successor to eZ Publish. Same content model foundations, active development, modern PHP, long-term viability.

For most eZ Publish installations, it's the lowest-risk migration path — your content structure translates naturally, and you don't have to rebuild everything from scratch.

But "lowest-risk" doesn't mean "simple." Especially if your site has:

  • Custom content types and fields built over years
  • Editorial workflows your team depends on
  • Complex permissions and user roles
  • Deep integrations with other systems
  • Years of content that has to migrate cleanly

That's where we come in.

What we do

Full migration projects

We handle the complete transition: database migration, content transformation, template rebuild, editorial workflow preservation, URL redirects, and go-live support.

Custom development on Ibexa OSS

Ibexa OSS doesn't include everything. If you need approval workflows, advanced permissions, custom editor features, or other functionality — we build it.

Ongoing maintenance

After migration, we stay with you. Updates, improvements, support when things break. We prefer long-term relationships over one-off projects.

Why us

We've done this before

We recently completed a complex migration for a European SME — a content-heavy B2B portal with custom editorial workflows, approval processes, and specialized editor plugins. Not a simple lift-and-shift: real custom development on top of Ibexa OSS. Read the case study

Deep platform expertise

We've worked with eZ Publish since 2007. Certified since 2013. We know the legacy codebase, the migration pitfalls, and the Ibexa platform deeply.

eZ Publish Certificate 2013 eZ Publish Certificate 2013
We fill the gaps

Ibexa OSS is missing features that eZ Publish had (or that you built custom). We've implemented approval workflows, version comparison tools, custom CKEditor5 plugins, role-based field permissions — things that would otherwise require Ibexa's expensive commercial editions.

Small team, direct communication

You work directly with senior engineers who understand your system. No account managers, no handoffs, no translation layers.

How we work

1
Assessment

We review your current eZ Publish installation: version, customizations, content structure, integrations. We identify what migrates cleanly and what needs custom work.

2
Migration plan

You get a clear scope: what we'll migrate, what we'll rebuild, what we'll improve, and what it will cost. No surprises.

3
Migration + development

We execute the migration in phases. Your editorial team can often continue working during the process.

4
Go-live + support

We handle the cutover, DNS, redirects, and post-launch monitoring. Then we stay available for ongoing maintenance.

Is this right for you?

This service is a good fit if:

  • You have a serious eZ Publish installation (not a brochure site)
  • Your site is business-critical and needs to keep running
  • You have custom functionality that needs to survive the migration
  • You want a partner who stays with you after go-live
  • You communicate well in English

This probably isn't right if:

  • You're looking for the cheapest possible option
  • You want to move to WordPress or a completely different platform
  • You need a large agency with 24/7 support teams

Let's talk

If you're facing an eZ Publish migration decision, we're happy to discuss your situation — even if you're not ready to start.

Request eZ Publish Migration Assessment

Still researching? Read our guide: eZ Publish End of Life: What Are Your Options?