SUPPORTED VERSIONS

WHMCS to Fleio migration app was latest tested with Fleio version 2021.12.1 and WHMCS version 8.3.1. However, tickets import works only from Fleio version 2022.01.1. If you encounter problems using this to migrate WHMCS data to your Fleio installation, send email to support@fleio.com.

Also note: client email field was removed in Fleio 2022.05.0, thus current client import no longer takes it into consideration.

SUPPORTED RESOURCES

The current WHMCSync app supports the following:

• Users
• Clients
• Clients groups
• Client contacts
• Servers
• Server groups
• Products
• Product groups
• Product prices
• Configurable options data
• Services
• Services hosting account settings
• Cancellation requests
• Currencies
• Hosting accounts
• Tax rules
• Tickets data
• Domains data

WHMCS TO FLEIO SYNC INSTALLATION

Copy this directory to Fleio backend installation dir and rename it to "whmcsync" (so it would look something like fleio/backend/whmcsync).

Create a new database, call it whmcs and copy the actual WHMCS database here. This new database will be used to copy all the needed data.

Add the database in Fleio settings.py:

DATABASES = {
    'default': {
        # default fleio database settings
    },
    'whmcs': {
         'ENGINE': 'django.db.backends.mysql',
         'NAME': 'WHMCS',
         'USER': 'root',
         'PASSWORD': '',
         'HOST': 'localhost',
         'OPTIONS': {'charset': 'utf8mb4'}
         }
    }

Add the database router in settings.py

# WHMCSYNC settings

INSTALLED_APPS += ('whmcsync.whmcsync', )
DATABASE_ROUTERS = ['whmcsync.whmcsync.routers.WhmcSyncRouter']
AUTHENTICATION_BACKENDS = ('whmcsync.whmcsync.auth_backend.WhmcSyncAuthBackend',
                           'django.contrib.auth.backends.ModelBackend')
    

Activate Fleio env. and run django migrate whmcsync after finishing the above setup.

Use the command by activating Fleio env. and running django whmcsync command from the backend dir.

NOTES

The whmcs_models.py file contains the Django models representation from WHMCS. If you wish to import additional data, these models will help. After installing this app, do not forget to run django migrate to setup the new whmcsync database in Fleio. This database is used to allow authentication for users with their old password.

To import tickets, ticket replies & ticket notes attachments, add the attachments' dir from whmcs at the same location as this readme (after adding repo files to fleio installation).

To see import options, activate Fleio environment and run django whmcsync -h.

You can run django whmcsync --all-configs first to setup everything is needed for clients & other related data import (currencies, tax rules, products, etc). Then you can use the --all-client-data flag along with django whmcsync --clients [whmcs_id, ] or django whmcsync --all-clients in order to import all client related data from a single run.

Known limitations

Users:

• users are imported without related permissions from WHMCS and have owner role on related client in Fleio

Staff users:

• staff users are imported as inactive, so super admins in Fleio can review their permissions

Configurable options:

• configurable options are matched by name, thus if you have duplicated conf. options by name only the last one will be imported, others will be overridden

Servers:

• passwords are not synced, they have to be re-set

Tax rules:

• tax rules that apply to all countries in WHMCS are not imported since Fleio does not support this

Tickets

• ! importing tickets works only using Fleio 2022.01.1 and above
• tickets, ticket replies & notes created by admins will match staff users in fleio by their related WHMCS admin field which represents first name and last name of the admin at the date of creation of the ticket/reply/note
• Fleio does not support multiple predefined reply categories using the same name so only the first by ID category from WHMCS will be imported with related predefined replies