...
Tip | ||
---|---|---|
| ||
When installing Blesta, you should choose a username that does not exist in your WHMCS installation, or it will result in an error when trying to import your WHMCS staff users. |
Tip | ||
---|---|---|
| ||
Often times WHMCS has mixed database collations and this can cause issues during import. For this reason we recommend:
|
Tip | |||||
---|---|---|---|---|---|
| |||||
Blesta uses an int(10) column for ticket codes. If you have any non-numeric characters in your ticket system in WHMCS, you can update them to match the internal ID to prevent any errors during import. Do this to a cloned copy of your WHMCS database, not your production copy.
|
Info |
---|
If you prefer, you can create a copy of your WHMCS database and import from that instead of your live system. |
...
The following data is imported from WHMCS to Blesta:
Import Type | Description | Import Type | Description | |
---|---|---|---|---|
Payment Accounts | Credit / Debit cards saved in WHMCS. | |||
Admin (Staff) | Staff who log into your WHMCS. | |||
Affiliates | ||||
Calendar | Calendar events. | |||
Domains | Domain Names | |||
Emails | Emails sent to clients. | |||
Invoices | Invoices generated to your clients. | |||
Support Departments | Support departments made on WHMCS. | |||
Taxes | ||||
Clients (Active / Inactive) | Clients on your WHMCS installation. | |||
Admin (Staff) | Staff who log into your WHMCS. | Configuration | WHMCS settings. | Affiliates|
Contacts (Client's contacts) | Contacts on your clients account | .Calendar | Calendar events. | |
Currencies | Currencies on your WHMCS installation. | |||
Emails | Emails sent to clients. | Products (Packages) | Packages on your WHMCS. | |
Invoices | Invoices generated to your clients. | Services | Services created on your customers. | |
Support | DepartmentsSupport departments made on WHMCS. | SupportTickets | Support tickets created on WHMCS. | Taxes |
Importing from WHMCS
Preparing WHMCS (If importing from your live WHMCS installation)
...
This redirect may need to be adjusted depending on your path to paypal.php in your WHMCS and your Blesta installation directory. Also, the 1 in /callback/gw/1/paypal_payments_standard/ references the company ID in Blesta. If you do not have any addon companies, then the company ID is 1. Note that normally the IPN URL for each client is unique, and look something like /callback/gw/1/paypal_payments_standard/?client_id=12345 where 12345 is the internal ID for the client. If this is ID is missing, Blesta attempts to match the transaction to a client based on the client's email address. If there is no match on the client's email address, the transaction will not be recorded.
Return to complete the Final Steps.
...