Secure PHP Update (PHP version upgrade support)
Beyond Service Guide
Upgrading unsupported PHP without stopping it
We handle PHP version upgrades, incompatibility fixes, and post-migration operation without interrupting your live website. Engineers specializing in server construction and operation will provide comprehensive support from investigation to deployment to production
Transition in stages while operations continue
We handle everything from investigating incompatibilities to fixing them
Post-migration operation and maintenance will also continue
\ Response within one business day at the earliest /
Get started with a free consultationWHAT IT IS
About the service
Secure PHP Update is a version upgrade service that handles everything from current status analysis and incompatibility fixes to production deployment and subsequent operation for websites running on PHP versions that are no longer supported or nearing end of support
The difficult part of upgrading PHP isn't the upgrade process itselfThe key is whether you can identify in advance what parts might stop workingWe will prepare a testing environment identical to the production environment, identify incompatible parts, and then proceed with the corrections* The duration and cost will vary depending on the scale, configuration, and frameworks and libraries used in the target system. Please contact us first to discuss a current situation assessment
Difference from typical practices
| - | Request to a production company | Request to server company | Secure PHP Update |
|---|---|---|---|
| Investigation of incompatible parts | △ Try moving it and check | × Not applicable | ◎ Identify dependencies in advance |
| Code modification | ○ Can handle | × Not applicable | ◎ Support |
| Server-side configuration changes | × Outsource to another company | ○ Can handle | ◎ The same team is in charge |
| Setting up the testing environment | △ Many environments are simple | △ Often excluded | ◎ Construction equivalent to the actual event |
| Pruning procedure | △ Not explicitly stated | △ Not explicitly stated | ◎ Prepare in advance |
| Post-migration operations | △ Maintenance contracts are separate | △ Server only | ◎ Continued until the app is released |
* The two columns on the left summarize general organizational trends. Actual scope of service may vary depending on each company's contract
WISSUES
Do you have any of these concerns ?
- The PHP version you are using is no longer supported
- I received a notification from the server company that they are discontinuing their service
- I'm afraid it will stop working once I raise it, so I'm holding it still
- There is no one who can investigate where the incompatibilities are
- I can't get in touch with the production company that made it
- My WordPress plugins have stopped working
- They're still using an outdated environment for handling personal information
- I don't know by when I need to take action
DEADLINE
PHP officialsupport end date
| - | situation | End of regular support | End of security fixes |
|---|---|---|---|
| PHP 8.5 | Standard Support | December 31, 2027 | December 31, 2029 |
| PHP 8.4 | Standard Support | December 31, 2026 | December 31, 2028 |
| PHP 8.3 | Security fixes only | December 31, 2025 (Ended) | December 31, 2027 |
| PHP 8.2 | Security fixes only | December 31, 2024 (Ended) | December 31, 2026 |
| PHP 8.1 or below | End of support | Completed | Completed |
PHP 8.2 will no longer receive security fixes on December 31, 2026Each version typically has a 2-year support period followed by a 2-year security update period, for a total of 4 years. Therefore, if you do nothing, you will need to make the same decision every 4 years
Source: PHP official website, "Supported Versions" (as of August 29, 2026). Please check php.net for the latest information
SERVICE
What we offer
01Operational Version Investigation:We will check what is currently running on the actual machine.
02Identifying Dependencies:We will organize the compatibility status of frameworks and libraries.
03Identifying the scope of impact:Create a list of which functions may be affected.
04. We will determine the target version, process, and timeframe for formulating the transition plan.
05Setting up the verification environment:Prepare an environment equivalent to the
06Fixing incompatible parts:Identify and fix code that stops working.
Replace the update dependency packages for the 07 library with compatible versions
08Operation Test:We will check if the main functions work as before.
09Preparing for the rollback procedure:This creates a state where you can revert to the previous state if a problem occurs.
10. Switch to a time slot that will have minimal impact on deploying to the production environment.
11.After the changes are reflected and the monitoringswitch is made, we will monitor the status for a while.
The plan for the next End-of-Life (EOL) is to prepare for the same problem to occur in four years.
* 01-04 are for investigation, 05-09 are for correction and verification, and 10-12 are for the post-implementation stage. Requests for investigation only are also accepted
HOW IT WORKS
Transition process andestimated timeframe
STEP 1
Current situation survey and identification of the scope of impact
Consultation and current situation survey Identify the operating version, dependencies, and scope of impact, and create a list of where modifications are needed
STEP 2
Corrections and preparations in the testing environment
Verification and correction We will prepare a testing environment identical to the production environment and correct any incompatibilities. We will only touch the production environment after preparing the rollback procedure
STEP 3
Secure deployment to production and continuous monitoring
Reflection/Operation The changes will be implemented during a time when the impact will be minimal, and the status will be monitored for a while. Operation and maintenance after the migration can continue as usualEstimated duration
| Consultation and current situation survey | 2 weeks |
|---|---|
| Quotations, approval processes, and contracts | 4 weeks |
| Building a testing environment / Compatibility check and correction | 6 weeks |
| Testing and deployment to production | 3 weeks |
| total | Approximately 15 weeks (one example) |
* The timeframe is an example only. It will vary depending on the scale, configuration, and scope of testing. Working backward from the end-of-support date, the work will begin several months prior to that date
OUTCOME
What will change if you request our services ?
01
Prior elimination of production failure risks
We don't proceed by suddenly switching to a production environment and causing the screen to go blank. We first identify and fix incompatibilities in an environment equivalent to the production environment before implementing the changesWe will switch over with a procedure in place to revert to the previous state in case a problem occurs02
Proactive measures to address End-of-Life (EOL)
If the hosting provider discontinues support for older PHP versions, the site will go down after a noticeIf you understand the deadlines and take action in advance, your site won't be shut down due to other companies' circumstances03
Routineand ongoing maintenance
PHP support typically ends after a total of four years, consisting of two years of support and two years of security updates. Since we will continue to be responsible for its operation after the migration,We will contact you before the next deadlineCONTACT
