Legacy Module Removal

Old PHP code may introduce breakage on newer versions of PHP runtime. WHMCS performs an inspection for any unused legacy modules. Legacy modules are deprecated modules that we no longer maintain or distribute and are typically for older and, often, discontinued services. Because deprecated modules no longer receive updates, we recommend migrating to a supported alternative and then removing the deprecated module.

This document describes automatic module removals that WHMCS performs during the update process. For the steps to manually remove modules, see Migrate to a Supported Alternative.

Inspection Process

During updates, WHMCS will check for modules that we no longer maintain or support If a module is active and you have configured it, the system considers it to be in use and WHMCS will not attempt to delete it.

Deletion and Notification Process

After the inspection process, WHMCS will create log entries at Configuration () > System Logs and sends notifications using the following logic:

Detected Use	Deletion Attempt	System Actions	Recommended Solution
In Use	No	The system logs a `One or more legacy modules were found to be in use and were not attempted to be deleted` message. The system sends admins a notification with a comma-separated list of retained modules.	Contact the module’s author and determine whether an update is available.
Not In Use	Yes	The system logs a `Unused legacy modules were deleted` message naming the deleted modules (for example, `Unused legacy modules were deleted: Hipchat`).	None.
Not In Use	Failed	The system logs a `One or more legacy modules could not be deleted` message or a `A recent WHMCS update failed to remove legacy modules. These modules may cause negative behavior if you upgrade PHP and leave them on the system. We recommend working to remove them manually.` message. The system sends admins a notification with a list of modules for which deletion failed.	Investigate the reasons why deletion failed and then remove the modules manually. Deletion typically fails due to file permission restrictions. When deletion fails, the module state may become inconsistent due to potential partial deletion.

After legacy module deletion is complete, we recommend going to Utilities > System > PHP Version Compatibility to check for any incompatible files in your WHMCS installation.

Modules That Remain Active After an Update

The update process only deletes legacy modules that are not in use. If you have configured a deprecated module, WHMCS considers it to be in use and does not delete its files. As a result, the module remains active after the update. Deleting a module’s files does not remove its stored configuration.

Because of this, a deprecated payment gateway, domain registrar, server, addon, fraud, or support module can continue to run after an update, even though it no longer receives updates. This can lead to unexpected behavior, especially after a PHP upgrade. We recommend migrating to a supported alternative and then removing the deprecated module.

Migrate to a Supported Alternative

To replace a deprecated module:

Identify a supported alternative for the module’s service. Review the available modules in the relevant section of the Admin Area or in the WHMCS Marketplace.
Configure and test the supported alternative.
Migrate your existing services, products, and configuration to the supported alternative.
Deactivate the deprecated module, remove its stored configuration, and delete its files from your installation. For more information, see the documentation for your module type:

updates whmcs-versions

Last modified: 2026 August 25