How to plan a PHP version upgrade

PHP versions have defined support periods and introduce performance, language and security changes. Upgrading regularly keeps an application on supported infrastructure and prevents several years of dependency changes accumulating into one risky project.

Inventory the complete application

Record the framework, packages, extensions, server configuration and background workers using PHP. A public website may be only one consumer; scheduled commands and queue workers need the same compatibility review.

Check supported version combinations

Confirm whether the current Laravel, WordPress or other framework version supports the target PHP runtime. Review package constraints and replace abandoned dependencies before the runtime upgrade forces the issue.

Use static analysis and deprecation evidence

Tools can identify removed functions, changed signatures and type assumptions. Application logs from current versions may already report deprecations. Resolve them deliberately rather than hiding warnings.

Test valuable workflows

Automated tests should cover authentication, permissions, transactions and integrations. Manual acceptance should include forms, uploads, exports and administration. A successful homepage is weak evidence for a business system.

Rehearse the deployment

Upgrade a representative staging environment with anonymised or safe data. Confirm web servers, command-line jobs and workers all use the intended version. Measure performance and logs before scheduling production.

Keep a rollback route

Database migrations and dependency changes must be compatible with the release plan. Deploy at a time when the team can monitor errors and restore the previous runtime if a serious issue appears.

Our ongoing PHP support includes planned runtime and Laravel upgrades, regression testing and production monitoring.