Delete a custom feature list only after deciding what its accounts and packages should use instead. Removing it changes feature-list assignments and can expose or hide customer tools through the replacement defaults.
IN THIS ARTICLE
Prepare for the change
Record the list settings and locate packages that reference it. Choose an intentional replacement list before removal. Do not treat the predefined default, disabled or mail-only lists as disposable customer-created templates.
01 Remove a custom WHM feature list
- Create or review the replacement feature list and check its enabled tools.
- Edit affected packages to select the replacement. Review any accounts with independent settings and test a representative customer before removing the old list.
- Open Packages > Feature Manager. Select the unused custom list from the management selector.
- Choose Delete and confirm that the selected name is the obsolete list. Accounts and packages still referencing a deleted list fall back to the default list, which is why reassignment matters.
- Update your internal plan notes so a later package is not configured using the deleted name.
How do I verify removing the feature list caused no disruption?
Check that the list no longer appears and that an affected customer still has the planned file, mail, database and DNS tools. Review the default list if any remaining account unexpectedly inherited it.
If the change does not work
If a customer loses an essential tool, reassign a suitable existing list or recreate the original custom list from your record. Do not respond by broadly enabling all features for every account. A missing deletion control or inaccessible list can reflect your reseller permissions and should be checked with the server administrator.