How licensing works, and how to move a licence

A Baxelo licence is tied to one installation, not to you and not to a server. Understanding what "one installation" means saves a ticket the first time you move, upgrade or clone something.

1. What the licence binds to

Domain	The hostname in your WHMCS System URL
Directory	The path WHMCS runs from on disk
WHMCS licence	A fingerprint of your own WHMCS licence key — never the key itself

All three are recorded the first time the module validates. Before that the licence belongs to nobody, which is why a brand-new key shows not activated yet in your client area.

The same key on a second installation is refused, and the refusal names the reason: registered to another domain, another directory, or another WHMCS. That is what stops a copy of your server becoming a second free seat — including copies you make yourself, like a staging clone.

2. Moving to another server

In your client area open Services → your service → Move Installation. It shows what the licence is bound to and how many moves remain.

Confirm. The licence is released immediately and stops working on the old installation at its next check.

Install on the new server, paste the same key, press Test Key. It binds there.

Release when you are ready to install, not before. The moment you release, the module stops working where it is. And each move is counted — there are ten, which is generous for honest use and finite on purpose.

3. Things that count as moving

Changing your WHMCS domain, including adding or dropping www.
Moving WHMCS into a different directory on the same server.
Migrating to a new host.
Replacing your WHMCS licence key.

Any of those makes the installation a different one as far as the licence is concerned. Release first, then change, then re-test.

4. Staging and test copies

A clone of your production WHMCS will be refused — same key, different directory. That is working as intended. If you need a licence for a genuine staging installation, open a ticket and ask; do not release your production licence to test something.

5. If we cannot be reached

A brief outage on our side is invisible to you. Each successful check is signed and valid for 48 hours, and the module keeps working on that window while it retries by itself. Your data is never at risk from a licensing problem.

6. The activation email

You get an email the moment a licence of yours binds anywhere, naming the domain and the path. If one arrives that you did not cause, release the licence straight away and open a ticket — the other installation stops working at its next check.

7. What travels to us

A check sends your licence key, the module version, your installation domain and directory, and your IP address. Nothing else. No client data, no ticket content, no database contents. Every check is recorded on our side, which is what lets us answer "where is my licence bound and when did that happen".