Account linking connects an existing WHMCS service to the remote hosting account that belongs to it. It does not create a new account, move website files or migrate billing. Use it when bringing current hosting services into the suite or after changing a server profile.
IN THIS ARTICLE
01 Check WHMCS first
Open the service in WHMCS and verify its assigned server, hosting username, main domain and customer. These values must agree with the real account on the selected control panel. A nickname, customer email address or domain alias is not a substitute for the hosting account's username or primary domain.
Confirm that the platform is enabled and that its connection profile reads the correct WHMCS server credential. Fix incomplete records before a bulk pass; services without a server or username cannot be verified.
02 Link one service
- Open Account Manager > Existing accounts.
- Search by domain, username, client, product or service number. Use the panel and server filters to narrow similar records.
- Choose Verify and link, or Verify link again for a previously linked service.
- Review the remote account identity and save the verified link.
- Choose Open account workspace. Confirm the correct domain and account data appear.
03 Verify several accounts
Select the required rows and choose Verify and link selected. The dialog has two stages: Verify accounts reads each remote identity, and the subsequent save action records the links that passed. Review failed or skipped rows before saving. The process does not justify guessing missing usernames or selecting every result on a server.
A record can be linked successfully and still have no customer tools if its product features are disabled. Likewise, a suspended service can appear in the administrator's directory while normal customer hosting tools require an active service. Account linking, feature entitlement and service status are separate checks.
What should I do when a linked account does not match?
Compare the failing record directly with the panel's primary account information. Check for an old server assignment after migration, renamed username, changed main domain, or a service linked to the wrong subscription. Correct the authoritative records, then repeat verification.
After changing a server's provider profile or authentication mode, reverify accounts on that server. Do not weaken ownership checks to make a row pass. If you cannot establish which account owns the service, keep its management actions unavailable and resolve that identity before making customer data changes.