Changing the address of a self-hosted WHMCS installation affects more than links in the client area. Payment callbacks, login integrations, mail processing and licence validation may also use the old address. Prepare those dependencies before switching customers to the new URL.
IN THIS ARTICLE
01 Choose whether the files must move
A new subdomain can point to the existing installation directory, or the application can move to a different directory. Keeping the files in place avoids unnecessary path changes when the hosting configuration permits it. Create the destination hostname, install a valid HTTPS certificate and confirm that it serves the intended WHMCS installation.
02 Update the application and integrations
- Back up the database and configuration. Record the old System URL and any absolute filesystem paths that will change.
- Arrange the licence reissue required for the new domain or location through your licence supplier.
- In General Settings, review the General tab values for the company domain, logo URL and WHMCS System URL. Set the System URL to the actual HTTPS installation address.
- If files moved, update cron, private storage and mail piping paths. A URL change alone does not require changing a working filesystem path.
- Review gateway callback addresses, registrar webhooks, OAuth redirects and external links. Change each provider's registered destination where its integration requires it.
- Test administrator login, client login, checkout, password reset links and a sample email template. Confirm that links lead to the new address without mixed HTTP content.
How should I preserve access from the old WHMCS address?
Use an appropriate redirect for ordinary browser visits to the old client area after testing. Payment notifications can use POST requests, so verify each gateway's documented callback behavior separately. Do not assume a browser redirect will preserve every callback correctly.
Keep the old hostname and certificate working during the transition where practical. Review access and integration logs for remaining callers using the old address, then update their configuration. If customer bookmarks still reach the old address, they should receive a clear route to the active installation.