Paid services are in preparation. Online payment and server jobs are not open yet. Check a PHP version free or email [email protected] about your setup. Prices below describe the planned services.
Upgrade an old PHP website.
Move an application to supported PHP with a compatibility review, staging and an agreed production change. Get a clear scope before paying for a larger upgrade.
Technical sources reviewed
A runtime update or an application upgrade?
A security update within a PHP branch and a move from PHP 7.4 to PHP 8 are different jobs. An old application may use removed functions, incompatible dependencies or extensions that need attention before the new runtime can serve it.
- Your supported PHP branch has a fixed build
- The PHP2Shell Patch service may be sufficient. You can plan a later branch upgrade separately.
- Your host requires a newer PHP version
- Check the application and its dependencies on staging, a separate copy of the site, before changing production.
- Your custom app has no clear maintenance history
- Start with the $490 audit. We identify the upgrade scope before quoting application work. The audit is credited in full toward the upgrade.
Test the application before switching.
Inventory the application
Review PHP, extensions, dependencies and the application's hosting requirements. Identify integrations and scheduled tasks that need checking.
Choose a supported target
Match the target PHP version to the application's requirements and support dates. Review changes between the starting and target versions.
Upgrade on staging
Run the application with the new PHP version and address the agreed compatibility issues. The starting scope includes up to three hours of code fixes.
Agree checks and cut over
Agree which business functions must work, confirm recovery and schedule the production change. Check those functions again after the switch.
The application's useful checks depend on what it does. For example, a site might need login, file-upload or scheduled-job checks. These are examples for planning; we agree the actual checks with you.
A usable backup and a recovery method belong in the upgrade plan. Restoring code alone may be insufficient if a change also affects data or the PHP package.
Choose a target with enough support time.
PHP's published security-support dates help decide whether a target is worth the migration effort. The application still needs to support the version you choose.
| PHP branch | Security support ends |
|---|---|
| 8.2 | December 31, 2026 |
| 8.3 | December 31, 2027 |
| 8.4 | December 31, 2028 |
| 8.5 | December 31, 2029 |
If an older PHP package is maintained by your distribution or an extended-support vendor, check that vendor's actual coverage. Its support period and fixes can differ from PHP's community schedule.
Sources: PHP supported versions and the PHP 7.4 to 8.0 migration guide. Your upgrade plan needs the relevant guides for each version change.
From $749 per site, with a confirmed quote.
Upgrade starts at $749 per site. It includes a server assessment, compatibility review, staging, up to three hours of code fixes and the agreed production cutover. Complex applications need a confirmed scope and price.
Custom applications start with a $490 audit, credited in full toward the upgrade. Additional engineering is $150 per hour, quoted before work starts and billed in 30-minute blocks.
Upgrade requests go through a quote rather than direct payment for the starting price. Tell us how many sites and servers are involved. A site price and a server count measure different parts of the job.
If you also need urgent PHP2Shell protection, include that in the request. A vendor patch or temporary mitigation may be possible while application changes are planned; its suitability depends on your setup.
Prices are in US dollars. Scope and service-specific guarantees are covered in Terms.
Send enough detail to scope the upgrade.
Include the current PHP version, application or framework, hosting provider, number of sites and servers, access you control and any deadline. Mention custom extensions, payment integrations and scheduled jobs if they matter to the application.
Do not send passwords, private keys, customer records or a database through the request form. We arrange the access and information needed for the agreed assessment.
Will changing PHP in my hosting panel fix old code?
A hosting setting selects a runtime. It does not repair application code or incompatible dependencies. Test an application copy before changing the live setting.
Can I move from PHP 7.4 to PHP 8?
That is a common upgrade path, but the amount of application work depends on the code, extensions and dependencies. The assessment establishes the target and scope.
Does an upgrade include ongoing maintenance?
The upgrade is a separate job. The existing Care plan covers PHP security maintenance from $490 per server per year. Review its scope on the pricing page.