Use ImportAssist database migration when the source platform and record types are supported. For existing cPanel, Plesk or DirectAdmin accounts, the native Sync Accounts feature can compare remote accounts with WHMCS. When neither fits, enter the client and service through the documented manual order workflow.

WHMCS 9.0 ImportAssist CSV supports client data. Do not assume a client CSV file also imports the services, invoices and payment arrangements belonging to those clients.

Record the remote server, username, domain, package, customer identity, billing cycle, recurring price and next payment date. Review suspended and orphaned accounts separately. A panel email address is useful evidence, but it may be outdated or shared and should not be the only basis for assigning ownership.

1. Back up WHMCS and verify the server connection under System Settings and Servers.
2. Open Sync Accounts for the intended server and wait for the comparison report.
3. Review the remote data beside its WHMCS match. Investigate discrepancies before selecting records.
4. Select Import/Sync only for the intended rows. Existing remote accounts can create local records, while a WHMCS-only service can be marked terminated if selected.
5. Review the confirmation screen and continue with the approved selection.
6. Check Activity Log and inspect each imported service's customer, product and server mapping.

Remote panels usually do not contain the customer's full billing details. Verify those fields manually, including currency, recurring amount and due date. Review generated products before exposing them for public sale.

For manual service entry, suppress unnecessary order confirmation and invoice generation as documented, then enter the correct existing-account details. Do not run Module Create for an account that already exists. Check the service status only after confirming the actual remote service.

Prepare a service-by-service exception list for data the provider could not supply. Assign each missing recurring amount, billing date or customer relationship to a reviewer, and keep that service outside automatic charging until the mapping is resolved. A complete count of imported accounts does not establish complete financial records.

Also review customer communications before activating the new arrangement. Imported customers may already have an external recurring payment agreement or an unpaid invoice in the source platform. Record which system owns the next charge and explain the intended payment route, so moving a service record does not leave two active collection processes.

• Plan a client-data import into WHMCS
• Use WHMCS server groups to control provisioning placement
• Change a WHMCS service due date without creating a billing gap
• Define acceptance checks for a completed website migration

• WHMCS Sync Accounts
• WHMCS: migrate data to WHMCS
• WHMCS ImportAssist
• WHMCS Products/Services tab