Tool
PHP end-of-life calculator
Pick a PHP version and an approximate line count. You get the support end dates from the PHP release cycle, your size band, and an indicative Assessment and migration range. A range is not a quote.
- Support status
- End of life
- Active support until
- —
- Security support until
- 31 Dec 2025
- Size band
- 20,000–100,000 PHP lines
- Assessment (range)
- $1,600–$3,700
- Migration per 1,000 lines
- $210–$340
- Illustrative migration total
- $10,500–$17,000
Dates follow the PHP release cycle (php.net). A price range is not a quote. HIGH complexity uses the upper half. Verify dates on php.net.
PHP support dates
A crawlable overview. Status is relative to today; end dates are fixed from php.net.
| Version | Active support until | Security support until | Status today |
|---|---|---|---|
| PHP 8.5 | 31 Dec 2027 | 31 Dec 2029 | Active support |
| PHP 8.4 | 31 Dec 2026 | 31 Dec 2028 | Active support |
| PHP 8.3 | 31 Dec 2025 | 31 Dec 2027 | Security support only |
| PHP 8.2 | 31 Dec 2024 | 31 Dec 2026 | Security support only |
| PHP 8.1 | — | 31 Dec 2025 | End of life |
| PHP 8.0 | — | 26 Nov 2023 | End of life |
| PHP 7.4 | — | 28 Nov 2022 | End of life |
| PHP 7.3 | — | 6 Dec 2021 | End of life |
| PHP 7.2 | — | 30 Nov 2020 | End of life |
| PHP 7.1 | — | 1 Dec 2019 | End of life |
| PHP 7.0 | — | 10 Jan 2019 | End of life |
| PHP 5.6 | — | 31 Dec 2018 | End of life |
Dates follow the PHP release cycle. If anything disagrees, php.net wins. Source · EOL table .
Frequently asked questions
When does each PHP version reach end of life?
Each PHP branch gets two years of active support, then two years of security-only support. After the security window ends, the branch is end of life. Exact dates are published on php.net; this calculator mirrors those dates.
Is running an EOL PHP version a security risk?
Yes. After end of life, the PHP project no longer ships security fixes for that branch. Hosts and Linux distributions also retire old runtimes, which can create compliance pressure for SOC 2, ISO 27001, and PCI DSS programmes.
How are the price ranges calculated?
Line count maps to MigrateForge’s published size bands (under 20,000, 20,000–100,000, or over 100,000 PHP lines). You see the Assessment band and the migration band per 1,000 lines for that size, plus an illustrative migration total of (lines ÷ 1,000) × the per-1,000 band. A range is not a quote. HIGH complexity uses the upper half.
Does MigrateForge migrate me off PHP automatically from this page?
No. This page is a planning tool. A free migration report gives size, risks, an indicative wave plan, and an indicative price range without uploading source code. Cutover still requires recorded journeys to match on the Java Spring Boot system.