Zend Framework and Laminas migration

Zend Framework applications are mature and often business-critical. The framework's future is the problem.

Zend Framework was a serious enterprise PHP framework, and plenty of important systems still run on it. Zend Framework became the Laminas Project, and Laminas MVC, the direct successor, has now been moved to security-only status. Zend Framework 1 is long past end of life.

If your application is built on Zend or Laminas, you need a plan. I'll help you make one, and carry it out without disrupting the business.

Book a free conversation Legacy System Assessment, from £2,500

Where things stand

Checked October 2026 against the Laminas project's own announcements. Confirm at getlaminas.org.

Framework	Status	What it means
Zend Framework 1	Long past end of life	No security fixes. Written for PHP 5-era servers. The Laminas migration tool doesn't convert it
Zend Framework 2 and 3	Succeeded by Laminas	No longer the maintained line. The Laminas migration tooling can convert these to Laminas
Laminas MVC	Security-only. The project has announced security patches until 31 December 2028, with no new features or bug fixes	It won't be updated to support PHP 8.5. A supported framework path, but a finite one
Mezzio	Maintained (the Laminas project's middleware framework)	The project's recommended direction for new work. A different architecture, so moving from MVC is a migration

The upshot: moving from Zend Framework to Laminas MVC buys you time and supported components, but Laminas MVC itself has an end date. That makes the question "migrate to what?", and the answer depends on your application.

Your options

Option	What it involves	Best when	Watch out for
Zend 2/3 to Laminas MVC	Mostly mechanical: rename namespaces and packages with the migration tooling, then fix what breaks	You need a supported base soon, and the application is stable	It's a staging post. You'll face the same question again before the end of 2028
Zend 1 to a modern framework	Port in stages, because there's no direct migration path	The application is important and still needed	A real project. Needs tests and careful planning
Laminas MVC to Mezzio	Move from MVC to middleware architecture, in stages	You want to stay in the Laminas ecosystem	A different architecture, not a version bump
Move to another framework (for example Laravel or Symfony), in stages	Replace piece by piece	The business wants a larger ecosystem, or the team already uses it	More work. Needs planning. Laravel upgrades
Replace the system	Move to a packaged product	Needs are no longer special	Migration and fit

Rewrite vs refactor vs upgrade

How I approach it

1. Assess

I map the Zend or Laminas version, PHP version, modules, Composer packages, database layer and integrations, and how heavily the application relies on framework-specific features. AI-assisted analysis speeds this up, and I check what it finds against the running system. How I use AI

2. Build a safety net

Enterprise Zend applications often have large, complex business logic and thin tests. I write tests that capture how it behaves today, so a migration that changes behaviour is caught before it reaches users.

3. Pick the target

You get the options with costs and risks for your application, including what each means for 2028 and beyond.

4. Migrate in stages

The mechanical parts (namespaces, packages) are done first. Behaviour changes, PHP upgrades and deeper restructuring follow, each step tested and reversible.

5. Test, roll out, hand over

Testing on a copy, a rollout with a rollback plan, and documentation. PHP upgrades

What typically causes trouble

Namespace and package renames that have to be consistent across code, configuration and third-party modules
Abandoned modules that never moved from Zend to Laminas
Old PHP, because many Zend applications were built for PHP 5.x and 7.x
Heavy use of framework internals, such as view helpers, form components and service-manager configuration
Zend Framework 1 specifics: front controllers, action helpers, Zend_Db and layouts, with no automated route forward
Large, undocumented business logic inside controllers and models
Server and extension assumptions

All of these are predictable once mapped.

What it costs

Fixed price, after assessment.

Free conversation
Legacy System Assessment, from £2,500, with options costed
Fixed-price quote for the route you choose

What affects cost: how far behind you are, application size, module count, test coverage and integrations. Direct day rate is £950; urgent work from £1,300 per day. Pricing

For agencies

A client on Zend Framework that your team would rather not touch? I can take it white-label, or direct with you as referrer. Agency terms

Frequently asked questions

Is Zend Framework still supported?

No. Zend Framework was succeeded by the Laminas Project. Version 1 is long past end of life, and versions 2 and 3 are no longer the maintained line.

Is Laminas still supported?

Laminas MVC is in security-only mode, with security patches announced until 31 December 2028. It won't gain new features or support for PHP 8.5.

Can the move to Laminas be automated?

Partly. A migration tool handles much of the mechanical renaming for Zend Framework 2 and 3 projects, but behaviour, PHP version and third-party packages still need human work and testing. It doesn't convert Zend Framework 1.

Should I move to Laminas or somewhere else?

It depends. Laminas MVC is a supported staging post, not a long-term destination. I'll tell you which fits your system.

We're on Zend Framework 1. What now?

It's a larger project, but often a worthwhile one if the application is valuable. A staged port or gradual replacement is usually safer than a rewrite.

Do you need to see our live data?

Usually not. Most of the work is on code and configuration. How I handle access

Tell me what you've inherited.

Tell me your Zend or Laminas version, your PHP version and what's worrying you. I'll tell you honestly what the options are.

Book a free conversation Legacy System Assessment, from £2,500