View Categories

Moving a license to another domain

1 min read

Moving a licensed DotwebApps installation to a new production domain, server, hosting provider, or deployment environment should be handled carefully so the replacement installation remains within the limits of the purchased license.

What this article covers #

This article explains the license-movement process at a general level. It does not replace product-specific instructions for moving application files, databases, configuration, uploads, or other data.

Exact migration steps vary by product. Always follow the documentation for the software you purchased when moving the application itself.

Recommended sequence for moving a production installation #

A safe general process is:

  1. Prepare the replacement environment. Confirm that the new domain, server, hosting account, or deployment environment is ready for the product.
  2. Back up the existing application and data according to the applicable product documentation before making changes to the current production installation.
  3. Deactivate or release the license on the old production installation where supported. This helps free the relevant activation allocation before the replacement installation is activated.
  4. Move or install the product on the new environment using the product-specific installation or migration documentation.
  5. Activate the purchased license on the replacement production installation.
  6. Verify the new installation. Confirm that the licensed product is working correctly before permanently retiring the old environment.

License limits still apply #

Moving an installation does not change the rights or activation limit of the purchased license.

The replacement production installation must remain within the finite activation limit of the applicable license tier. A license move should not be treated as an unlimited-transfer right or as permission to keep additional production installations active beyond the purchased limit.

Where supported, deactivating the old installation before activating the replacement can help release an activation slot.

License movement is different from application or data migration #

Releasing and reactivating a license is only one part of moving a production system.

Depending on the product, the application move may also require separate handling of files, databases, configuration, uploaded content, environment settings, or other product-specific components. Follow the relevant product documentation for those steps.

Standard license support should not be assumed to include a complete data or server migration service unless that service is explicitly provided.

If the old installation cannot be accessed #

If the old production installation is unavailable and you cannot perform the normal deactivation process, contact DotwebApps support for guidance.

Provide only the product, order, license, and installation information needed to identify the issue. Never send passwords, private keys, API secrets, payment credentials, or unrelated authentication information.

Do not assume that a license will reset automatically or that a domain transfer is guaranteed. Product-specific behavior may vary, so follow the applicable documentation and support guidance.