App down? Emergency Recovery
Illustration of a server rack in brand blue

Tier B: by arrangement

CakePHP developer for support, upgrades and migration

CakePHP applications on old framework and PHP versions that still run portals and back-office tools.

Request a quote Takeover Assessment

Who still runs CakePHP

CakePHP is a PHP framework that gained popularity in the late 2000s for its convention-based approach, and many small businesses and agencies built portals, booking systems, directories and admin tools on it. BuiltWith trends for the top 1M sites (October 2026) show CakePHP on about 900 sites, a small but real group that is mostly forgotten by general PHP advice.

These applications are often between five and fifteen years old and were built by freelancers.

What goes wrong when nobody is looking after it

  • The PHP version underneath is out of support. Hosts retire old PHP, and CakePHP 1.x and 2.x code written for old PHP stops working after a hosting change.
  • Old major versions are retired. The project ends support for older lines on its published schedule, so a very old application gets no framework fixes.
  • The upgrade path is a port. CakePHP 3 changed the ORM and naming conventions, so older apps cannot simply update.
  • Plugins and vendor code are frozen. Third-party plugins were copied into the project and are no longer maintained.
  • Configuration is hand-set. Database credentials, salts, email and cache settings sit in files that differ between servers.
  • Few developers know old Cake. Searching for help brings up answers for versions that do not match.

Support and takeover options

CakePHP is Tier B, taken on by arrangement with a PHP specialist. The Takeover Assessment is read-only: identify the CakePHP and PHP versions, list plugins and custom code, document hosting and configuration, and test a database backup restore.

Options after that:

  1. Keep it running. Pin a supported hosting environment for the PHP version the app needs, tested backups, monitoring and a person to call. Ongoing Support is arranged case by case.
  2. Upgrade in stages. Move to a current CakePHP and PHP, fixing the ORM, templates and plugins at each step. Fixes and Upgrades.
  3. Re-platform. Move to Laravel or another stack if that is the better long-term fit. Modernization and AI.

If the site is down after a hosting change or a crash, Emergency Recovery is the first call. It covers outages from errors, crashes and neglect.

An upgrade from CakePHP 2 in outline

We typically build a new CakePHP application skeleton alongside the old one, port the database layer and models first, then controllers and views by feature, and run both side by side with a shared database until the last pieces are moved. At each step we compare screens and outputs. This takes longer than a rewrite on paper but carries far less risk, because the old site keeps working throughout.

CakePHP shares most of its hosting and PHP-version concerns with other PHP software, so our page on PHP, WordPress and Laravel applies as well. Teams sometimes find that CakePHP code was mixed with plain PHP scripts or Perl, and we handle those in the same assessment.

How we work

Tier B and C stacks are by arrangement with a stack specialist. We scope each in writing and tell you plainly when we are not the right fit. Every engagement starts read-only. Write access is set out in a signed agreement first, and a person reviews every change before it reaches a live system. Work is AI-assisted and human-reviewed, and we explain how at the start.

See PHP, WordPress and Laravel, Perl and CGI and Ruby on Rails.

Request a quote for your CakePHP application and tell us the version if you know it, what the app does and where it is hosted.

Frequently asked questions

Is CakePHP still maintained?

Yes. CakePHP is an active open-source project with current releases, and the project retires old major versions on its own published schedule. Check the CakePHP release page for the current supported lines.

Can an old CakePHP 2 application be upgraded?

Usually yes, but not in one step. CakePHP 3 and later were substantial rewrites, so upgrading from 1.x or 2.x is closer to a port than a version bump, done in stages with the old app kept running.

Does CakePHP need a newer PHP?

Current CakePHP releases require a recent PHP, while older ones were written for PHP versions that are long out of support. The PHP version is often the first thing that forces a decision.

Should we rewrite in Laravel instead?

Sometimes, if the application is small or the team prefers it. For larger applications, moving to a current CakePHP usually keeps more of the existing structure. We compare both after reading the code.

Our CakePHP developer left. Can you take over?

Yes. We start read-only, document the application, plugins and hosting, and test backups before we change anything.

Related stacks

PHP, WordPress and Laravel

PHP, WordPress and Laravel applications that still run the business but have lost their developer, their updates or their hosting plan.

Perl and CGI

Perl scripts and CGI sites that process forms, files and orders, often written by someone no longer around.

Ruby on Rails

Rails applications on old Ruby and Rails versions that still earn money but have lost their original developers.

See all stacks we support

Tell us what you have

In two weeks we know it, document it, and keep it running. Send a few lines about your software and we will reply by email.

Request a quote [email protected]
Email Request a quote