Skip to content
WHMCS Verified service · 5.0 rating

WHMCS Migration from HostBill

HostBill to WHMCS with ImportAssist, payment history and product options moved by script, and a staged parallel check.

Fixed-price quote in 24h 14-day correction guarantee 1 year free support

A HostBill to WHMCS migration replaces HostBill as your billing system while your customers' hosting, VPS and domains carry on untouched. WHMCS documents an official route, its free ImportAssist addon, which supports HostBill 2016 and later. We use it as the base, add the records it leaves behind, and check both systems side by side before switching, from $199. Blesta users should read the Blesta page instead, and anything else falls under general WHMCS migration.

Coverage at a glance

According to the ImportAssist compatibility table on docs.whmcs.com, a HostBill database import brings over:

  • Clients, contacts and currencies
  • Product groups, products, pricing and product addons
  • Servers and client services
  • Domains
  • Invoices with their line items
  • Support departments, tickets and ticket replies

It does not bring over transactions, configurable options and the values chosen on each service, service addons, custom fields, client groups, client notes, promotions, saved payment methods, user logins, internal ticket notes or ticket logs.

The first gap matters most. Without transactions, invoices arrive in WHMCS with no payment records behind them, so client statements, income reports and refund history look wrong from day one. We copy HostBill's payment records into WHMCS against the matching invoices, so a client's history reads the same in both systems.

Rebuilding product options

HostBill products are often built with form components for RAM, disk, location, operating system or IPTV connections. WHMCS calls these configurable options, and ImportAssist does not create them for HostBill. We rebuild each option group, link it to the right products, and set every active service to the values its customer is paying for. Recurring amounts are then compared service by service, because a missing option usually shows up as an invoice that is suddenly cheaper than last month.

Servers and provisioning

HostBill servers do come across, but stored credentials and module names do not always line up with WHMCS. We check each imported server at Configuration > System Settings > Servers, map it to the right WHMCS module (cPanel, Plesk, DirectAdmin, Proxmox-based VPS modules and so on), re-enter API tokens where needed and run Test Connection. A sample of services per server is then checked for correct usernames, so suspensions hit the right account.

HostBill's hourly cloud billing has no direct equivalent in a standard WHMCS install. If you bill VPS by the hour, a module such as our Hourly Pay module covers it, and we plan that mapping during scoping.

The staged parallel check

  1. Export. A copy of the HostBill database is made reachable from the WHMCS server, usually through a remote MySQL user limited to read access.
  2. First import. ImportAssist runs into a fresh WHMCS staging install from Addons > ImportAssist for WHMCS, choosing HostBill under Select Database Import, after a full WHMCS database backup as the WHMCS docs advise.
  3. Gap fill. Transactions, configurable options, custom fields, promotions and client groups are added by script.
  4. Side-by-side review. HostBill keeps billing as normal while your team opens real accounts in both systems and flags differences. We fix the import logic, not individual records, so the final run is clean.
  5. Cutover. HostBill's automation is switched off, the database is exported one last time, the import and scripts run again into the approved setup, and WHMCS cron starts.
  6. Read-only period. HostBill stays available to staff for lookups for as long as you want, with nothing sending from it.

Logins and cards

User logins are not part of the HostBill database import. ImportAssist's CSV format does accept a password_hash column, so we test a few accounts to see whether HostBill's stored hashes work in WHMCS. If they do not, customers get a reset email at launch. Saved cards stay with the old gateway setup, so customers add a payment method on their first WHMCS invoice unless your gateway allows tokens to be linked.

Version and requirements

ImportAssist is free for WHMCS license holders and needs PHP 8.2 or 8.3. A new target install is normally WHMCS 9.x on PHP 8.2 or later, since 8.13 reaches its listed end of life on December 31, 2026. Older HostBill versions than 2016 are not supported by ImportAssist, so we move clients through its CSV upload and the rest by script.

From your side

  • HostBill admin access and a full database export
  • A WHMCS license, or permission to buy and install one for you
  • Server, registrar and gateway credentials for reconnecting
  • One or two staff members to review accounts during the parallel check

Quote structure

ScopePrice
HostBill 2016 or later, small dataset: ImportAssist run, transactions, server checks, reconciliation, cutoverFrom $199
Configurable options, service addons and custom fields across many productsFixed quote by product and record count
HostBill older than 2016, hourly billing or custom pluginsFixed quote after a data review

For a feature comparison before committing, read WHMCS vs Blesta vs HostBill vs Upmind, and browse our migration modules for later moves between servers.

What's included

Every WHMCS Migration from HostBill engagement ships with these.

  • Official ImportAssist import from HostBill 2016 or later into a staging WHMCS
  • HostBill payment records copied into WHMCS transactions against the matching invoices
  • Product form components rebuilt as configurable options with each service's values
  • Service addons, custom fields, client groups and promotions added by script
  • Imported servers mapped to WHMCS modules and connection-tested
  • Service usernames sampled per server so suspensions reach the right account
  • Side-by-side review while HostBill keeps billing
  • Final import at cutover with HostBill automation switched off
  • Password hash test, with a reset email plan if hashes do not carry over
  • HostBill kept read-only for staff lookups after launch

Business outcomes

What hosting operators report after delivery.

  • Client payment history in WHMCS matches HostBill
  • Services keep their exact recurring amounts and options
  • Your team checks real accounts before customers see WHMCS
  • Hosting and VPS services keep running throughout the move
  • Old HostBill records stay available when a billing question comes up

Ready to talk about WHMCS Migration from HostBill?

Quick scoping call, fixed-price quote within 24 hours, no commitment.

Related services

Other WHMCS work hosting operators ask us about.