# WHMCS Upgrade Service

> WHMCS patch and maintenance updates within your branch: 8.13.x security releases, older 8.x to 8.13, or 9.0 to 9.1.

WHMCS updates within your major version, applied safely: release notes read, full backup, staging trial, the right update channel, then logins, orders, payments and cron checked.

- **Price:** Starting at $149
- **Billing:** One-time, fixed scope
- **Category:** WHMCS
- **Quote turnaround:** Fixed-price quote within 24 hours
- **Start a project:** https://whmcspilot.com/start-project
- **Details:** https://whmcspilot.com/services/whmcs-upgrade-service
- **Last updated:** 2026-11-05

## Overview

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](/services/whmcs-9-upgrade).

## Which updates this covers

You are onMoving toWhat to watch8.13.xThe latest 8.13 releaseSecurity and maintenance fixes only; PHP 8.1 or later staysAn older 8.x release8.13Release notes for each version passed, PHP and ionCube Loader versions9.0.x9.1.xionCube Loader 15.0.0 or later installed first, PHP 8.2 to 8.4, legacy Stripe modules deprecated in favor of Stripe Dynamic Payments8.x9.xNot 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](/blog/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

1. **Read the release notes** for your target and every version in between.
2. **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.
3. **Back up** the database and the whole WHMCS directory, with configuration.php copied separately.
4. **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.
5. **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.
6. **Apply it** through Utilities &gt; 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.
7. **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](/services/whmcs-monthly-support), 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

ScopePriceOne update within your branch, with backup, staging trial and checksFrom $149A catch-up across several 8.x releases with a custom theme or many modulesFixed quoteA third-party module that breaks during the update$65/hour, or a fixed quoteThe major move from 8.x to 9.xWHMCS 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](/services/whmcs-legacy-module-rescue)
- WHMCS Cloud, which WHMCS updates for you

Send us the version shown at Utilities &gt; Update WHMCS, and the scoping call can confirm straight away which route applies.

## What's included

- Release notes read for the target and every version in between
- Automatic Updater requirements checked before the update
- Full database and file backup, with configuration.php stored separately
- Staging trial with mail, gateways and provisioning disabled
- Update channel set to Current Version or Stable as the job needs
- Update applied through Utilities > Update WHMCS or install.php on the command line
- Custom theme and edited open-source files protected from overwrite
- Post-update checks on logins, orders, payments, tickets, cron and Module Queue
- System Health reviewed for 24 hours after the update
- Optional schedule for unattended maintenance updates on WHMCS 9.1

## Business outcomes

- Security fixes reach your live install without a broken checkout
- Customizations survive because they are kept out of folders the updater replaces
- A tested backup is in place before anything changes
- You know which updates can run unattended and which need a person
- 9.0 installs move to 9.1 before 9.0's anticipated end of life

## Frequently asked questions

### Is this the same as the WHMCS 9 upgrade?

No. This service covers updates within your major version, such as 8.13.x patches or 9.0 to 9.1. Moving from 8.x to 9.x is the WHMCS 9 upgrade service, from $299.

### How do I apply a patch without moving to a newer WHMCS version?

Set the update channel to Current Version in Configure Update Settings at Utilities > Update WHMCS, then check for updates. That channel only offers maintenance releases for the version you have installed.

### When does WHMCS 8.13 reach end of life?

Its anticipated end of life is December 31, 2026, a date it shares with 9.0. The 9.1 release is supported until September 30, 2027.

### Can WHMCS update itself automatically?

WHMCS 9.1 can apply maintenance releases unattended on a schedule. It still needs a working cron, write access to the whole install and your own database backups, because it only backs up the files it replaces.

### How much does a WHMCS update cost?

From $149 per install for one update within your branch. Catch-ups across several releases on heavily customized installs are quoted after the call.

### What if a third-party module breaks after the update?

We roll back or fix it, whichever is safer for billing. Fixes to open code are billed at $65 per hour or quoted; for encoded modules we gather the error details for the vendor.
