Contents
Moving a License to Another Site
Customers move sites: they relaunch on a new domain, or sell one site and build another. They do it by releasing the old site on their licenses page and activating the new one from the software. To stop one license from being passed round many sites, each product limits how often this can happen:
- Free changes at the start
-
For Free changes after activation (hours) after a license's first activation (48 hours by default), it can be moved as often as needed, to correct a mistake such as activating a staging site first.
- A number of changes per period
-
After that, the license may move to a new site Changes allowed times (2 by default) in any rolling Change period (days) (365 by default). Each change becomes available again a period after it was used.
- A minimum time on each site
-
A customer can't release a site until it has been bound for Minimum binding (days) (30 by default). Administrators can release a site at any time.
Only a move to a site the license has never been used on counts as a change, and only once the license has used as many different sites as it has seats. Filling a new license's seats is free, and moving back to a site the license held before is free. There is no limit over the lifetime of a license.
When a customer has used all their changes, their licenses page says when the next becomes available, and offers . You see the request on the administrator Licenses page, and can grant one extra change with .
Asking for another change records the request and shows it on the administrator page, but sends no email to administrators. Check whether a notification is wanted.