On this page
When we show a host the WP Care + PHP Upgrade Bundle, the first question is almost always the same: is this cheaper than what we pay to keep old PHP patched?
The honest answer, on most fleets, is no. And that answer is the whole point.
Two products, two units
Extended PHP support is sold per server. One license covers every site on the machine, so on a shared box holding a few hundred accounts, the cost of keeping PHP 5.6 or 7.4 patched works out to cents per site. Whether that protection comes from a third-party patch provider, from secured legacy builds bundled into a server OS license, or from a host’s own engineers backporting fixes, the math lands in the same place. Runtime patching is cheap at scale, and it should be.
WP Care is priced per site, because a website is the unit that gets maintained. Updates, backups, malware scanning, monitoring and a monthly report happen one site at a time.
So when a host divides a per-server patch fee across a dense shared server and compares it to a per-site care plan, the patch looks cheaper. It is cheaper. It is also a different product. One keeps a site old and safe. The other makes it current and keeps it that way. Even the companies that sell extended PHP support describe it as a bridge: protection for the period before a site can be upgraded. A bridge is only useful if someone is walking across it.
The comparison that matters is not what the host pays to patch. It is what the customer is getting for their money. On most extended PHP programs, the answer is an old version of PHP they cannot see.
The server type changes everything
“Cents per site” is only true on one kind of server. The math depends on how many sites share the license, and who is paying for it.
Shared hosting (cPanel and similar). The host licenses extended PHP support per server and spreads it across hundreds of accounts. Per site, the patch costs almost nothing, and the customer usually never knows it exists. This is where a care plan will always cost more than the patch. The case here is entirely about outcomes: a current site, a care plan the customer can see, and a fleet the host can retire version by version.
VPS and dedicated servers. The math flips. These customers often buy the extended PHP add-on themselves, per server, for a machine running one site or a handful. Per site, that can cost as much as a care plan or more, and it buys nothing but a patched old runtime. Upgrade the sites and the customer cancels the add-on outright. On a single-site server, the conversion can be cheaper for the customer from day one, and it is the cleanest server-elimination story in the fleet: one customer, one server, one license that goes away.
Managed WordPress. Billing is already per site, so the customer is often paying a per-site fee to stay on an old PHP version, sometimes a substantial one. There is no dense-server discount to compete with. The conversion is a like-for-like swap: the same per-site line, now paying for a current site and a care plan, often with room to step the customer up a tier instead of down.
| Server type | Sites per server | Who pays for extended PHP | Patch cost per site | WP Care vs the patch | What converting does |
|---|---|---|---|---|---|
| Shared (cPanel) | 100 to 500 | The host, per server | A few cents | Always more | Trades a hidden patch for a visible care plan; savings come as versions and servers clear |
| VPS or dedicated | 1 to 5 | Often the customer, per server | $1 to $20 | Cheaper with one site, more with several | The customer cancels the add-on; cheapest on single-site servers |
| Managed WordPress | Per site | The customer, per site | Already per site | Like for like | Same line on the invoice, now buying a current site and care |
Illustrative, based on a per-server patch fee of $5 to $20. Your actual cost depends on your provider and how densely your legacy sites are packed; the audit replaces these ranges with your numbers.
Four kinds of hosts, one destination
Every host we talk to falls into one of a few positions, and the conversion looks different for each.
| Charges the customer | Absorbs the cost | |
|---|---|---|
| Uses a patch provider | Convert the extended PHP SKU to WP Care at the same price. The customer gets a current site and a care plan for what they already pay. | Upgrade the site and add WP Care as a hosting benefit, or at a small fee that covers the plan. The spend finally produces something the customer can see. |
| Patches internally | Same conversion, plus engineering hours come back each time a legacy version is fully retired. | The legacy spend is real salaried time with no customer-facing result. Converting sites gives that spend a return. |
For the customer, the whole conversion is one message: “We upgraded your site to a current version of PHP and moved you to WP Care+. Your price has not changed. You now get safe updates, malware scanning, backups, monitoring and a monthly care report.” Nothing is required from them.
Some hosts with shared hosting get secured legacy PHP bundled into their server OS license. There is no separate fee to cut, but the cost is still there, built into the price of the license. For them, the case is mostly about the customer: current PHP, a care plan, and a monthly report.
In every case, the destination is the same. The site comes current, the customer lands on WP Care+, and the host gets a legacy count that shrinks instead of sitting flat for another five years.
Nothing goes unprotected in the meantime. Sites waiting their turn stay on their WP Care plan with scanning, updates, backups and monitoring, and a runtime patch can stay in place underneath until the last site on a server is upgraded.
Where the cost actually falls
Cost savings are real in this model. They are just not where most people look first.
Support tickets. Legacy sites generate compatibility tickets that rarely show up on a budget line. Few hosts have calculated what those tickets cost, and the number is usually larger than they expect.
Engineering time. For hosts that backport patches themselves, every legacy version is a standing commitment. That commitment ends the day the last site is upgraded off that version.
Whole servers. This is the one to understand precisely. A per-server patch fee does not fall when a site upgrades. It falls when no site on the machine still runs old PHP. Upgrade five of ten sites on a server and the fee stays exactly where it was. Clear all ten and the license can go.
That changes how a legacy fleet should be worked. Not site by site across the whole estate, but server by server, starting with the boxes that are closest to zero. The last site on a server is usually the hardest one, a rebuild candidate or a refactor, and it is the one that cashes the savings. One fully cleared server can be worth more than fifty scattered upgrades.
There is one caveat. Server savings only apply where legacy sites are concentrated. On shared hosting, that means dedicated legacy servers, not old and current PHP running side by side on the same box. On VPS and dedicated, it is automatic: the customer’s server is the unit, and upgrading its sites ends the license.
Old operating systems. Legacy PHP is often the reason a server never moves off an end-of-life OS, because the migration would break the sites on it. Get the sites current and that reason goes away, which is what finally lets the box be migrated and its extended OS support dropped.
What the host actually gets
So we lead with the things a patch cannot deliver, in this order:
- The customer is on current PHP. Faster, compatible, off the countdown, without doing anything or paying anything more.
- The customer has WP Care they never had. Safe updates, malware scanning, backups with rollback, monitoring and a monthly Proof-of-Care report.
- Every report is an upsell placement. A customer who sees the work every month is the easiest customer in the fleet to move to a higher care tier.
- The legacy burden shrinks. Tickets fall, versions retire, and servers clear on a schedule.
Three of those are about the customer and the host’s revenue. One is about cost. That order is deliberate.
The part that doesn’t show up in a cost analysis
Every number in this article is about what legacy PHP costs to keep. The bigger number is what a current customer is worth.
A customer on extended support is paying to stand still. A customer on WP Care has a faster site, a current version of PHP, and a monthly report proving their host is looking after them. That customer renews. That customer complains less. And that customer, reading a care report every month, is the easiest one in the fleet to move to a pro care tier.
That’s the real trade. Not a cheaper patch, but the same line on the invoice turned from a cost into a customer who’s happier and a revenue path that didn’t exist before.
Start with three questions
If you are weighing this for your own fleet, start where we start with every host:
Do you charge customers for extended PHP, or absorb the cost? Who does the patching, your team or a provider? And which servers are the legacy sites on: shared, VPS or managed?
The answers tell you which conversion fits. The next step tells you the size of it: send us your legacy PHP list and we will audit a sample free. You get back:
- how many sites upgrade cleanly, need code work, or should be rebuilt
- projected hours for each lane and the causes
- which servers are closest to fully clear
- what the conversion looks like on your invoice
PHP 8.2 loses security support on December 31, 2026. The pool refills every January. Patching keeps it safe. Upgrading keeps the customer, and grows revenue by giving them more, not by charging them to stand still.
See the Legacy PHP Fleet Program or request your fleet audit.