Our WHMCS upgrade service applies updates that keep you on your current major version: security and maintenance releases such as 8.13.x, a catch-up from an older 8.x release to 8.13, or a move from 9.0 to 9.1. It costs from $149 per install and suits owners who would rather not run the updater on a live billing system themselves. Moving from WHMCS 8 to 9 changes PHP requirements, templates and invoice behavior, so that job has its own page: the WHMCS 9 upgrade service.
Which updates this covers
| You are on | Moving to | What to watch |
|---|---|---|
| 8.13.x | The latest 8.13 release | Security and maintenance fixes only; PHP 8.1 or later stays |
| An older 8.x release | 8.13 | Release notes for each version passed, PHP and ionCube Loader versions |
| 9.0.x | 9.1.x | ionCube Loader 15.0.0 or later installed first, PHP 8.2 to 8.4, legacy Stripe modules deprecated in favor of Stripe Dynamic Payments |
| 8.x | 9.x | Not this service; see the WHMCS 9 upgrade |
Timing matters this year. Per the supported-versions table in the WHMCS docs, support for 8.13 and 9.0 is expected to stop on December 31, 2026, and for 9.1 on September 30, 2027. An install on 9.0 should plan its move to 9.1 now, and an 8.13 install should at least be on the last 8.13 release while the 9.x move is planned. Our WHMCS 9 upgrade guide covers that larger decision.
Why even small updates break things
- Edited default files. Updates overwrite the twenty-one and six themes, the default order forms, the language files and WHMCS-supplied modules. Changes made directly in those folders disappear.
- Open-source files changed in place. Files such as aff.php are shipped open so they can be edited, and the updater replaces them anyway.
- Encoded third-party modules. A module encoded for an older ionCube Loader stops with a "cannot be decoded" error once the Loader or PHP moves on.
- Leftovers. An install folder left behind shows Down for Maintenance (Err 2), and old files in the admin folder cause GuardedForUpdate errors.
- Permissions. A configuration.php the updater cannot write to, or files owned by the wrong user, make the update stop halfway.
How we apply an update
- Read the release notes for your target and every version in between.
- Check the updater's requirements: a 128 MB PHP memory limit, 250 MB of free disk, allow_url_fopen on, max_execution_time of 60 seconds or more, the Zip extension or proc_open, and open_basedir off or set to include the install and moved folders.
- Back up the database and the whole WHMCS directory, with configuration.php copied separately.
- Trial the update on a staging copy with mail, gateways and provisioning disabled. If you bought your license directly from WHMCS, you can request a free development license for it.
- Pick the update channel. Current Version applies the newest patch for your installed version without moving you up; Stable offers the latest general release. We switch back to Stable afterwards if that is what you normally use.
- Apply it through Utilities > Update WHMCS, with the Temporary Update Path outside the web root. Where the Automatic Updater cannot run, we upload the release and run install/install.php from the command line.
- Verify: admin and client logins, a test order, a test payment, a ticket, the next cron run and the Module Queue, then System Health for the following 24 hours.
Staying current afterwards
WHMCS 9.1 can install maintenance releases unattended on a schedule you set, through Configure Update Settings. It backs up only the files it replaces, not your database, it needs the cron running, and the WHMCS user must be able to write to the entire installation. We can set it up with a quiet-hours schedule, or you can hand updates to our monthly maintenance plan, which tries each release on staging first.
What we need
- An admin role with the Update WHMCS and Modify Update Configuration permissions
- SSH, SFTP or control panel access to the server
- A list of third-party modules and where you bought them
- A low-traffic window for the live update
Prices
| Scope | Price |
|---|---|
| One update within your branch, with backup, staging trial and checks | From $149 |
| A catch-up across several 8.x releases with a custom theme or many modules | Fixed quote |
| A third-party module that breaks during the update | $65/hour, or a fixed quote |
| The major move from 8.x to 9.x | WHMCS 9 upgrade, from $299 |
Outside this service
- WHMCS license fees and paid updates for third-party modules
- Rebuilding modules whose vendors have gone quiet, which is legacy module rescue
- WHMCS Cloud, which WHMCS updates for you
Send us the version shown at Utilities > Update WHMCS, and the scoping call can confirm straight away which route applies.