Migration · WHMCS
Migrate from WHMCS to NexCMP
WHMCS and NexCMP model a customer differently, so moving between them is a rebuild with careful mapping, not a file copy. In the 30 working days of NexCMP Source an expert engineer reads your data out of WHMCS, rebuilds what belongs in NexCMP and runs both systems side by side until you switch.
Included with NexCMP Source ($499 one-time), not with NexCMP Free. VMware, WHMCS, HostBill, Blesta, Paymenter, StackBill, Virtualizor and Apache CloudStack are trademarks of their respective owners. NexCMP is independent and not affiliated with or endorsed by them.
The problem: two different billing models
WHMCS is a general web-hosting billing and automation platform: clients, products and services with billing cycles, invoices and many gateways and modules. NexCMP is built for selling cloud servers: each customer has a prepaid wallet, virtual machines are charged hourly or monthly from it, and invoices are produced when customers buy, renew or top up.
Because of that, a WHMCS service with a next due date does not map one to one to anything in NexCMP. The balance a customer holds, the cloud servers they run and the plan they are on do map, and the engineer's job is to find the right mapping for each of your products and to say honestly which parts are rebuilt, which are archived and which do not move at all.
NexCMP does not include a built-in WHMCS importer, and this page does not claim one. The migration is work done by our engineer with scripts against the WHMCS admin API or database and against the NexCMP admin console, API or, where those do not reach, the source code you hold.
What moves, what is rebuilt, what is archived
Each row is checked against the WHMCS API reference. Anything the reference does not show is handled by reading the WHMCS database instead, or is left out.
Clients
- What WHMCS lets us read
- GetClients lists clients, and GetClientsDetails returns the details, including status, currency, credit balance, custom fields and notes. The example response shows no password or password hash.
- In NexCMP
- Moved: a customer account is created for each client in the NexCMP admin, with an invitation or password-reset e-mail so the customer sets a new password.
Source: WHMCS — GetClientsDetails · accessed 2026-10-19
Credit balance
- What WHMCS lets us read
- The client record includes a credit amount, and GetCredits returns a client's credit log.
- In NexCMP
- Moved: the balance is added to the customer's wallet by an administrator credit with a reason. Amounts in NexCMP are in US dollars, so balances in another currency are converted at a rate agreed with you.
Source: WHMCS — GetCredits · accessed 2026-10-19
Services (cloud servers)
- What WHMCS lets us read
- GetClientsProducts returns each service with its status, billing cycle, next due date, recurring amount, domain, dedicated IP, server details and configurable options.
- In NexCMP
- Moved when the service is a virtual machine on CloudStack or Proxmox VE: the machine is attached to the right customer and plan. The WHMCS next due date does not carry over, because VMs are charged from the wallet.
Source: WHMCS — GetClientsProducts · accessed 2026-10-19
Services (other products)
- What WHMCS lets us read
- The same call returns every service, including domains, hosting and add-ons.
- In NexCMP
- Not moved: NexCMP sells cloud servers and its own modules. These stay in WHMCS or are archived.
Source: WHMCS — GetClientsProducts · accessed 2026-10-19
Products and prices
- What WHMCS lets us read
- GetProducts returns products with a name, group, module and a price for each billing cycle.
- In NexCMP
- Rebuilt: each product you want to keep becomes a NexCMP plan with an hourly or monthly price that you confirm.
Source: WHMCS — GetProducts · accessed 2026-10-19
Invoice history
- What WHMCS lets us read
- GetInvoices and GetInvoice return invoice numbers, dates, status, subtotal, tax, total, balance, credit, items and transactions.
- In NexCMP
- Archived: the history is exported as files you keep for accounting. NexCMP numbers its own invoices from the first one it issues.
Source: WHMCS — GetInvoice · accessed 2026-10-19
Saved cards and pay methods
- What WHMCS lets us read
- GetPayMethods shows only the last four digits of a card and, for remote cards, a gateway token. WHMCS documents that a card saved through a tokenised gateway is tied to that gateway.
- In NexCMP
- Not moved: customers add a card or PayPal account again. NexCMP keeps only references to the Stripe or PayPal vault, never card numbers.
Source: WHMCS — Working with Tokenization · accessed 2026-10-19
Subscriptions at gateways
- What WHMCS lets us read
- Each service record carries a subscription ID.
- In NexCMP
- Ended at cutover: NexCMP charges from the wallet, so recurring subscriptions held at a gateway are cancelled on the switch date to avoid double charges.
Source: WHMCS — GetClientsProducts · accessed 2026-10-19
Tickets, promotions and other records
- What WHMCS lets us read
- Not covered by the calls above.
- In NexCMP
- Archived by default. Vouchers and the affiliate programme can be rebuilt in NexCMP if you use them.
How the data is read: the WHMCS API needs API credentials created for an admin user whose role has the API Access permission. WHMCS also documents the database connection settings in its configuration file, which is the route when a table is not exposed by the API. We use read-only access whenever possible.
The plan, week by week
Typical, adjusted to your case. The 30 working days of continuous work are about six calendar weeks.
Week 1 — Inventory and mapping
We read your WHMCS: clients, products, services, currencies, gateways, add-ons. Together we decide for each product whether it becomes a NexCMP plan, stays in WHMCS or is archived, and we write the mapping that the scripts will follow.
Week 2 — Build the NexCMP side
NexCMP is installed (or an existing install is used) and connected to your CloudStack and/or Proxmox VE. We set up branding, plans and prices, payment channels, e-mail and the invoice seller details, so the new system is ready before any customer is touched.
Week 3 — Dry run
The scripts run against a copy of the data into a test NexCMP. We compare customers, balances and services row by row with WHMCS, fix mismatches and rehearse the cutover steps.
Weeks 4 and 5 — Real data and parallel run
Customers and balances are created in the production NexCMP and virtual machines are attached to them. WHMCS stays the system of record for billing while you and the engineer check accounts and customers receive their invitation. Final balances are synchronised just before the switch.
Week 6 — Cutover and handover
On the date you chose, billing moves to NexCMP, WHMCS gateway subscriptions are cancelled, WHMCS is set read-only or retired for the migrated products and notices go to customers. We hand over the scripts and notes, and stay available for the move until the end of the 30 working days.
Outline only. The real plan comes out of week 1, and the only dated commitment in the offer is the 30 working days.
Risks and how we reduce them
We do not promise zero downtime or a perfect first run. This is what can go wrong and what we do about it.
Balances that do not match
A balance must be right to the cent. The dry run compares every balance with WHMCS, and the final balances are re-read just before the switch so that late payments are included. NexCMP's ledger is append-only, so a mistake is corrected by a reversing entry that stays visible.
Double charging at cutover
Recurring subscriptions at the old gateways would keep charging after the move. We end them on the switch date and keep both systems in parallel beforehand, with a billing cut-over date agreed with you.
Customers cannot sign in
The WHMCS client-details response shows no password or hash, so we do not plan on carrying passwords over. Every customer gets an invitation or reset link. We schedule these with your announcement, and your support team can send a new link from the NexCMP admin.
Saved cards disappear
A tokenised card cannot be reused outside its gateway, so customers add a payment method again. Their first top-up in NexCMP can save it. We prepare the wording for your announcement.
Machines change addresses
If servers also move platform, addresses and DNS records may change. The inventory lists them, TTLs are lowered ahead of the cutover and customers are told in advance. If machines stay where they are, nothing on the machine side changes.
Old data is needed later
Invoice history, tickets and other records that do not move are exported to files you keep. We recommend keeping WHMCS available read-only for as long as your accounting rules need it.
Rollback
WHMCS is not deleted. Until you confirm the migration is complete, customer records can be re-read from it and billing can return to it.
Who does what
API credentials for an admin role with API Access, or read-only database access
- The expert does
- Reads the data and writes the migration scripts
Decisions on which products become plans and at what price
- The expert does
- Proposes the mapping and builds the plans in NexCMP
Accounts and keys for your payment channels, and your seller details for invoices
- The expert does
- Configures them in NexCMP and tests a payment
Access to CloudStack or Proxmox VE if services are virtual machines
- The expert does
- Connects it and attaches machines to customers
The cutover date and the announcement to your customers
- The expert does
- Rehearses the cutover, runs it and checks balances afterwards
What you get in the 30 working days
The migration is part of the NexCMP Source upgrade: a one-time $499 that includes the complete source code (Rust server, Vue portal and admin, Go node agent, CLI, build scripts), the right to modify and build your own version without limit, 12 months of new source releases, all apps and 30 working days of continuous work with an expert engineer.
In those 30 working days the expert migrates you from WHMCS to NexCMP at no extra charge, or does a VMware to Apache CloudStack move, a migration from another system, or a complete A-to-Z setup and the building of your apps. The clock starts when you start the work with the expert and is shown on your license page. Support for the move lasts the same 30 days.
NexCMP Free does not include this. Free is free for one year with all modules and no technical support, only fixes of source-code bugs, and renews at $99 per year.
WHMCS to NexCMP — frequently asked questions
What does it cost?
Is this included in NexCMP Free?
Does NexCMP have a WHMCS importer?
Will my customers keep their passwords?
Can saved cards be copied?
Do I lose my invoice history?
Does everything I sell in WHMCS move?
Sources and notes
WHMCS facts come from the official WHMCS developer and administrator documentation. NexCMP facts come from NexCMP's own documentation. The documentation of both products changes, so check the version you run. VMware, WHMCS, HostBill, Blesta, Paymenter, StackBill, Virtualizor and Apache CloudStack are trademarks of their respective owners. NexCMP is independent and not affiliated with or endorsed by them.
- WHMCS — API authentication
- WHMCS — GetClientsDetails
- WHMCS — GetClientsProducts
- WHMCS — GetProducts
- WHMCS — GetInvoice
- WHMCS — GetInvoices
- WHMCS — GetCredits
- WHMCS — GetPayMethods
- WHMCS — Working with Tokenization
- WHMCS — The configuration.php file
- NexCMP documentation — Managing customers
- NexCMP documentation — Invoices and ledger
- NexCMP documentation — Saved payment methods
- nexcmp.com/pricing
Move from WHMCS with an engineer at your side
Upgrade to NexCMP Source for $499 and start your 30 working days, or ask [email protected] about your WHMCS setup first.
Last updated: