What Should I Check Before Upgrading the PHP Version?
By Adrian Butnaru · Independent developer · Blanes (Girona), working remotely across Spain.
Published: · Last technical review:
Before upgrading PHP, I review the entire codebase of your application. Dependencies and behaviours that must be retained are matters to be reviewed. An external reference does not prove your code's compatibility. The target version, procedure, and verification of results must be defined for your case, without promising an automatic migration.
Criteria: do not confuse a target version with a review
I suggest first defining the need: do you want to resolve a specific problem, maintain an application, or assess an environment upgrade? Choosing a version does not in itself answer what must be retained. To prepare the scope, I would write down the tasks you use and the questions that require review. I would not ask you to diagnose the code or consider a migration accepted merely because a target version was chosen.
My published offering includes maintenance and evolution of existing PHP and MySQL applications, with security updates, backups, and bug fixes. New features are quoted separately. That description does not substantiate cross-version compatibility for a third-party application. I would not use a general rate or an example of my own as a substitute for the technical review your case may need.
Proposed checklist before deciding on a change
- Application code and syntax
- Review of deprecated functions, type handling, and error notices between the current version and the target PHP version.
- Dependencies and extensions
- Inventory of external libraries, PHP extensions required by the server, and MySQL queries.
- Integrations and document generation
- Verification of email delivery, PDF report export, and connections with external services.
- Staging environment testing
- Validation of critical business workflows outside production before changing the active version on the server.
- Scope agreement and backup
- Written definition of deliverables, prior backup, and separation of any new features from the upgrade.
I do not present this checklist as an approved technical procedure.
If you do not know the dependencies, leave that answer open. I do not suggest deducing them from the appearance of a screen. Likewise, a version list someone may have provided warrants distinguishing what information is confirmed from what remains open. The goal of the inquiry is to prepare a scope assessment, not to force you to certify that your application can be upgraded before I have reviewed it.
My own proof and the limit of comparison
I suggest separating the version you currently run from the version you want to evaluate. Describe what change you need and what questions your environment raises, without treating a portfolio reference as proof of compatibility. Reviewing dependencies and behaviours must be agreed upon for your application; I do not offer a universal upgrade formula or an intervention that is already included by default.
I do not assert compatibility for an application without first reviewing it. I maintain your application by default; I only propose rebuilding if the code review shows that maintenance is unfeasible. Before upgrading PHP, I review the entire codebase. That review does not allow asserting an application's compatibility in advance, nor does it establish a universal upgrade procedure. I accept PHP 7.x applications solely to migrate them to PHP 8 under a separate quote; I do not maintain them on PHP 7.x. I do not add a list of breaking changes or migration instructions that are not documented in authorised sources.
What dependencies I would propose identifying
To prepare questions, I would suggest distinguishing your application code, the libraries it uses, the hosting, and the services with which it communicates. This is a proposed inventory to be agreed upon, not a claim about what your tool contains. We would need to confirm what components exist, who can provide information, and what part falls within the review you are requesting.
I would also ask what operations rely on documents, notifications, or external information. I do not assume that your application has those features. If they exist, I would suggest noting them down as behaviours requiring attention when defining testing. If you do not know how they connect, you can describe what you do on screen and what outcome you need to observe. There is no need to replace that description with an invented technical explanation.
When you should NOT promise a direct upgrade
I would not take a migration as accepted simply because a screen loads or because the hosting provider offers a different version. As preparation criteria, I would suggest reviewing what tasks matter to your business and what remains to be verified. This is not a conclusion about your installation: it is a boundary of what I can state with the information in this article. I do not guarantee an absence of incidents or automatic compatibility.
From a prudent technical perspective, it is advisable to compare upgrading the current application against rebuilding only after reviewing the actual state of the code and its dependencies. The first alternative aims to preserve its functionality; the second requires defining a different scope. I would not present rebuilding as the default solution, nor maintenance as an obligation if the requirements you need to resolve are no longer clear.
Separate upgrading from feature requests
If you want to add an operation alongside the upgrade, I would suggest describing it separately. My offering separates maintenance from new features. That distinction ensures the document does not attribute a capability that does not yet exist to an upgrade. It also helps formulate what behaviour you want to keep and what you want to modify. It does not on its own determine what work is ultimately included or establish a fixed quote.
How I would approach it with you
I begin with a written diagnosis and agree on deliverables, budget, and timeframe before development. For this requirement, I would propose that the document distinguish review, pending decisions, and potential intervention. I would not treat these stages as services already authorised merely by sending an inquiry. Nor would I publish a universal technical sequence of commands for you to execute on production without having reviewed your application.
During development, I show functional progress for you to test from your browser or mobile phone. In an upgrade, I would suggest agreeing beforehand on which specific tasks to observe. I do not consider a compatibility review passed based on an isolated demonstration. What tests, environments, and authorisations would be required are part of the procedure to be agreed upon, not a detailed feature that can be deduced from the homepage.
To prepare your inquiry, indicate what PHP/MySQL application you run in production, what you need covered as maintenance or upgrade, and what new features or deliverables you would like quoted separately. I suggest bringing those answers as context, without passwords or invented compatibility conclusions. If technical information is missing, we will note it as pending before turning an upgrade expectation into a commitment.
What I would bring to the final decision
I suggest reviewing a list of operations you want to retain alongside still-open questions. I would not call it a passed test if the corresponding check has not yet been performed. Nor would I mix an upgrade with the acceptance of new features that emerge during our discussion. If information is missing to choose the target version or describe the work, it should remain visible. A sound technical decision can acknowledge boundaries; it does not need to conceal them to appear definitive, nor turn a hosting expectation into a guarantee about your code.
Technical checklist I propose reviewing in a staging environment
I review the entire codebase before upgrading PHP. The following questions guide that review; they are not an upgrade manual, nor do they allow asserting your application's compatibility in advance.
- Functions and syntax: what deprecated usages or potential incompatibilities should be reviewed between the current version and the chosen one, without deducing them from a screen that still loads?
- Server extensions: what PHP extensions does the application require, and what should be confirmed regarding their availability in the target environment?
- External libraries: if
composer.jsonexists, what library requirements and relationships with the PHP version should be reviewed? I do not promise that every package will upgrade without changes. - Types and errors: what strict typing, exception handling, and error notices would be relevant to the workflows we need to preserve?
- Critical operations: what user authentication, forms, and PDF generation, where present, should be tested with sample data outside production?
The outcome I would seek to agree upon is a record of tests performed, pending incompatibilities, and necessary decisions. I would not call it a validated upgrade merely because only part of the checklist was completed.
Frequently asked questions
What dependencies do I need to review?
I suggest identifying what code, libraries, hosting, and services participate in your application, without assuming that all of them exist or fall under maintenance. The inventory and specific procedure require review and approval. My offering substantiates PHP maintenance, not a universal list of dependencies or the compatibility of every component with a specific version.
How do I verify compatibility?
Before upgrading PHP, I review the entire codebase; I cannot state in advance that your application is compatible. For your case, what critical workflows and dependencies would need to be tested, and in what environment? I accept PHP 7.x applications solely to migrate them to PHP 8 under a separate quote; I do not maintain them on PHP 7.x.