WP Maintain manages the full PHP lifecycle across your fleet in four motions: find the at-risk sites, protect them while they wait, upgrade the ones that can move, and convert the fleet you already bill for legacy support into WP Care+.
Real-Time Fleet Visibility
See the exact PHP version behind every site in your portfolio. Outdated and end-of-life runtimes are flagged automatically, with no manual auditing.
Early Warnings, Not Emergencies
Alerts fire when sites run unsupported or soon-to-be-deprecated versions, giving your team runway ahead of every end-of-life date and every forced-upgrade deadline.
Sorted Into Lanes Before Anyone Touches Production
Each flagged site is scanned against the target PHP version and cloned to staging for a test run. The result places it in a lane: upgrades cleanly, needs a quick fix, needs code patches, needs a rebuild. Your team sees the whole fleet by lane before a single upgrade is scheduled.
Protect Sites While They Wait
Every fleet has stragglers: legacy custom code, abandoned owners, plugins that break on modern PHP. Forcing them breaks sites. Ignoring them leaves unpatched runtimes on your servers.
Protection Is Part of the Plan, Not a Separate Product
Every enrolled legacy site is on a WP Care plan, so it keeps getting malware scanning, safe updates, backups with rollback, uptime and PHP monitoring while the runtime is not current. WP Care+ offers virtual patching and malware removal at the application layer, which is where the overwhelming majority of WordPress compromises actually enter. Nothing extra to buy, and nothing to cancel later. When the site upgrades, the plan continues as it was.
A Legacy Risk Report, Only While It Is Legacy
The monthly Proof-of-Care report carries a legacy PHP section for every site still on an end-of-life runtime: exposure, what blocks the upgrade, and where it sits in the queue. The section disappears the month the site comes current.
We Do Not Patch PHP Itself
Manufacturing security patches for dead runtimes forever is the model we reject. It gets paid when sites stay old. Protection is the waiting room. The upgrade is the destination.
PHP Upgrades: Managed Migrations Off Dead Runtimes
Audit First
Each site is scanned for code that fails on the target PHP version. Outdated plugin and theme code is identified before anything moves.
Fix, Then Migrate
Incompatible code is resolved, the upgrade is proven on staging, and the site moves to a fast, supported runtime with approval and rollback at every step. No white screens, no surprise fatals.
Fleet Migrations, Not One-Offs
Sites move in controlled batches, lane by lane, cheapest wins first. Compatible sites can upgrade automatically on an annual cycle, with failed upgrades rolled back instantly. Sites that are cheaper to rebuild than to patch are quoted as rebuilds. Sites that never change can be converted to Managed Static, where WordPress stays the CMS and no PHP runs on the public site.
Convert Extended PHP Into WP Care+
Most hosts already bill customers to keep old PHP running. That recurring line can become WP Care+ instead.
Same Subscription, Same Price, Current Site
Enroll your extended PHP fleet. We audit it, upgrade every site that can be upgraded in place, and you switch the billing SKU from extended PHP to WP Care+. The customer pays what they paid before and gets a maintained, monitored, current site. You keep the revenue.
No New Billing Motion
No product launch, no sales cycle, no customer to convince. The line the customer already sees changes its name and delivers more.
The Upgrade Is Included for Enrolled Fleets
For hosting partners under a volume agreement, the PHP upgrade is included with WP Care+ on every enrolled legacy site: minor fixes and code patches, with heavier engineering through Pro Services.
The Line That Matters Is What You Charge, Not What You Pay
Whatever you pay a vendor to patch old PHP is pennies per site, and it never ends. The number that matters is the $5 to $25 a month you bill for it, for something the customer cannot see. WP Care+ turns that same line into a current site and a care plan the customer can see, at the same price.
Why Hosts Run the Full Lifecycle
Retire Infrastructure Risk
End-of-life PHP on your servers is a security liability with your name on it. The lifecycle clears it systematically instead of one emergency at a time.
Free Your Platform Roadmap
Legacy sites are what stop infrastructure teams from retiring old runtimes. Protect the stragglers, migrate the rest, and deprecate on your schedule. Get the sites current and the reason to keep an old OS goes with them, which is what finally lets you migrate the box and retire the extended support fees on it.
A QBR Number That Goes to Zero
Legacy PHP Sites, Upgraded, Rebuild Candidates, Remaining Opportunity. One funnel per PHP version, reviewed every quarter. Your leadership sees the legacy problem shrinking on a schedule, and your customers see the plan they pay for taking them somewhere.
Monitor finds them. WP Care+ protects them. Upgrades graduate them. The platform keeps them current from then on. For hosts carrying legacy fleets, these capabilities are packaged as the Legacy PHP Fleet Program with WP Care+ and the PHP upgrade included: upgrade or rebuild, both ending on current PHP.