1. Obtain an appropriate development licence and confirm its access conditions. Protect the test address with authentication or a network restriction.
2. Create a separate file location and separate database. Copy the production files and a controlled database backup into them.
3. Update the staging configuration.php to point only to the staging database and private storage locations.
4. Set the staging WHMCS System URL to its own HTTPS address.
5. Enable Disable Email Sending or configure a controlled test mail sink before triggering application activity.
6. Replace live gateway and registrar connections with supported test credentials, and disconnect production provisioning servers.
7. Keep staging cron disabled until its outgoing integrations and test data have been reviewed.

Inspect absolute paths for attachments, downloads, templates and cron scripts. A copied configuration can still point at production storage. Also review remote storage, notification services, webhooks, addon API keys and custom scheduled jobs.

Use clearly labelled test products and disposable hosting accounts. A gateway's test mode does not put a separate registrar or server module into test mode. Verify each integration independently and do not use a real customer's service as the target of a provisioning test.

Exercise customer and administrator sign-in, checkout, invoice generation, a supported test payment, provisioning, ticket submission and scheduled tasks. Record expected results before starting so an unexpected email or account action is easy to identify.

For an upgrade, compare behaviour before and after the change using the same test cases. Inspect System Health, logs and automation reports, and verify customised templates and third-party modules.

Limit access to the team performing the test and avoid sharing unnecessary customer information with external tools. Keep the original encryption configuration available for a legitimate recovery, but never substitute staging configuration back into production without a reviewed deployment plan.

Keep the successful test record, exact software versions and remaining limitations with the change plan. Staging success supports deployment but does not replace a production backup or a check of the real server environment. After the live change, repeat a small set of safe acceptance checks and confirm that only the production scheduler owns real billing activity.

• Check WHMCS requirements before installing or updating
• Use the WHMCS automatic updater safely
• Run an end-to-end WHMCS test order before launch
• Manage test accounts and credentials for billing integrations

• WHMCS: set up a test environment
• WHMCS: configuration.php