Why CI3 apps need a plan
The CodeIgniter project lists CodeIgniter 3 as in maintenance, receiving mostly just security updates, and "intended for use with PHP 5.6+". CI3 apps lean on dynamic properties, which PHP 8.2 deprecated, so on modern PHP they fill logs with warnings, and the PHP versions they run happily on are end of life. CodeIgniter 4 is a rewrite rather than an update, so moving takes planning.
What changes in CodeIgniter 4
- Structure: namespaces, a new folder layout and Composer-based installs.
- Controllers and models: new base classes; models gain built-in validation and entities.
- Libraries: some CI3 libraries no longer exist and need replacing.
- Configuration: config files become classes, plus
.envsupport. - Routing and filters: auto-routing is off by default; filters replace many hooks.
How it works
- 1
Code review
Size of the app, custom libraries, database use and hosting checked; fixed quote.
- 2
Fresh CI4 base
A new CodeIgniter 4 project on PHP 8.3+, with your config and database connected.
- 3
Move module by module
Controllers, models and views converted and tested one area at a time.
- 4
Test and go live
Full test on staging, then switch with a rollback plan and documentation for your team.