Maintenance · Upgrades · Migration

Core PHP and CodeIgniter: Maintenance, Upgrades and Migration to Laravel

Much Indian business software was built between 2010 and 2020 in core PHP or CodeIgniter, by a developer who has since moved on. It still runs the business, but PHP versions reach end of life and nobody dares touch the code. We audit, stabilise and upgrade these systems, add the features the business needs, and migrate to Laravel when that is right. We do not start new projects in CodeIgniter or hand-rolled PHP.

Core PHP appPHP 5.6, mysql_* calls
CodeIgniter 3PHP 7.2, end of life
Audit, stabilise, secure
stagingbackupsGit
CodeIgniter 4 on PHP 8upgrade in place
Laravelmodule by module, same URLs
PHP 8upgrades from 5.x and 7.x
CI3 → CI4migrations, module by module
6Laravel systems as the destination
Nonew builds in CodeIgniter
Sound familiar?

The Situations We Are Called Into

The hosting notice

Your host is retiring PHP 7.x and nobody knows what will break on PHP 8.

The developer has gone

No documentation, and a feature request open for a year.

Slow and fragile

Pages time out at month-end and every fix breaks something else.

Security

Plain-text passwords, concatenated SQL, no CSRF protection.

CodeIgniter 3 is end of life

CI4 is a rewrite, not an upgrade, so the move needs a plan.

It has outgrown itself

A few pages became the company’s system, and every change takes weeks.

What We Do With Core PHP and CodeIgniter Applications

Audit and stabilise

We read the code and database, find what is fragile or dangerous, and give you a plain-language plan. Urgent items are fixed first.

PHP version upgrades

PHP 5.x or 7.x to 8.x: deprecated functions, mysql_* to PDO, and hosting moved too. Cloud & DevOps

CodeIgniter 3 to 4

Routing, services and validation changes, migrated with the application running.

Security hardening

Parameterised queries, password hashing, CSRF and XSS protection, upload controls.

New features in the existing structure

Features built inside a system sound enough to keep, and documented.

Restructuring hand-rolled PHP

A proper data layer, version control and a deploy process.

Migration to Laravel, when it is time

Module by module behind the same URLs, with no big-bang cutover. Laravel Development

Keep It, Upgrade It, or Migrate It? How We Decide

ChooseWhenWhat it looks like
Keep and maintainThe code is reasonable and the main risk is the PHP version or hostingAudit, PHP 8 upgrade, security fixes, documentation, a support retainer
Upgrade in place (CI3 → CI4)A CodeIgniter 3 application you will keep developing for yearsPlanned CI4 migration, module by module, then feature work on CI4
Migrate to LaravelHand-rolled PHP that has outgrown itself, or a system that needs a mobile app, API or AI layerLaravel beside the old app, modules moved behind the same URLs
RewriteRarely: only when the data model itself is wrongA new Laravel build with data migration; the old system runs until cutover
Honest note: we will not push migration where an upgrade does the job, and we do not take on new builds in CodeIgniter or core PHP. Migrated systems are brought to the standard of our Laravel work, such as Keystone QS, TripMall and Pandit Constructions.
From audit to support

How a Takeover Runs

  1. Access and audit (week 1)

    Access, a database copy and one walkthrough; then a written assessment and a quote.

  2. Stabilise

    Security, backups, staging and a deploy process that is not FTP.

  3. Upgrade

    PHP and framework versions, with a regression pass on the flows that move money or data.

  4. Build or migrate

    Feature work, or modules moved to Laravel behind the same URLs.

  5. Support

    Monthly retainer or on call; documentation grows with every change.

invoice.php: before and after
// Before: PHP 5.6, removed in PHP 7, open to injection
$r = mysql_query("SELECT * FROM invoices WHERE id = " . $_GET['id']);

// After: PHP 8, PDO with a bound parameter
$stmt = $pdo->prepare('SELECT * FROM invoices WHERE id = ?');
$stmt->execute([(int) $_GET['id']]);
$invoice = $stmt->fetch();

An illustrative example of the most common fix in a PHP 8 upgrade.

Cost: the audit is quoted on a short call; a PHP upgrade is usually days to a few weeks; CI4 or Laravel migration is quoted per module.
FAQ

Questions from Owners of PHP and CodeIgniter Applications

Something else? Ask us on WhatsApp.

Yes. That is the usual starting point. We read the code and the database, document what we find, and give you a plain-language assessment before any changes.

Something usually breaks. We find it in a staging copy first and fix it before the live upgrade, with a regression pass on critical flows.

CI4 if the codebase is sound and you will keep developing it. Laravel if it has outgrown itself or needs an API, mobile app or AI layer. We recommend one after the audit.

Yes. We run the new Laravel modules beside the old application behind the same URLs and move one module at a time; users keep working throughout.

No. We maintain, upgrade and migrate them, but new builds go on Laravel, the framework we would migrate your application to, so you do not inherit the same problem again in five years.

The audit is quoted on a short call. A PHP upgrade is usually days to a few weeks depending on size; CI4 or Laravel migration is quoted per module after the audit. Support is a monthly retainer.