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.
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
| Choose | When | What it looks like |
|---|---|---|
| Keep and maintain | The code is reasonable and the main risk is the PHP version or hosting | Audit, PHP 8 upgrade, security fixes, documentation, a support retainer |
| Upgrade in place (CI3 → CI4) | A CodeIgniter 3 application you will keep developing for years | Planned CI4 migration, module by module, then feature work on CI4 |
| Migrate to Laravel | Hand-rolled PHP that has outgrown itself, or a system that needs a mobile app, API or AI layer | Laravel beside the old app, modules moved behind the same URLs |
| Rewrite | Rarely: only when the data model itself is wrong | A new Laravel build with data migration; the old system runs until cutover |
How a Takeover Runs
Access and audit (week 1)
Access, a database copy and one walkthrough; then a written assessment and a quote.
Stabilise
Security, backups, staging and a deploy process that is not FTP.
Upgrade
PHP and framework versions, with a regression pass on the flows that move money or data.
Build or migrate
Feature work, or modules moved to Laravel behind the same URLs.
Support
Monthly retainer or on call; documentation grows with every change.
// 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.
Still Running on a PHP Version Nobody Supports?
Send us access to the repository or server and a short description of what the application does. We will come back with an assessment, a keep-upgrade-migrate recommendation and a quote for the first phase.