> For the complete documentation index, see [llms.txt](https://easycatalog.nousmedis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://easycatalog.nousmedis.com/getting-started/1.-first-steps/transferring-an-activation.md).

# Transferring an activation

EasyCatalog can only be activated on one computer, but you can easily transfer the license to another

To transfer an activation for all registered modules, press the `Deactivate` button on the `About EasyCatalog` dialog.

<figure><img src="https://1939597359-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FazTsFGbHKYYVlYs8LIQv%2Fuploads%2F1IXBG43c5y4jahAhorir%2Fdeactivate.png?alt=media&amp;token=de3d7ccc-e32a-41d1-bd97-1b692ef91990" alt="Acerca de EasyCatalog"><figcaption><p>Highlight one serial number and click <strong>Deactivate</strong></p></figcaption></figure>

To transfer an activation for an individual module, highlight the serial number that you would like to transfer in the list of active modules and press the `Deactivate` button.

After a few seconds your serial number will deactivate and you should be able to activate the serial number on another machine in around 5 - 10 minutes.

If you have any problems with activation, please contact us using the [contact form](https://nousmedis.com/en/get-in-touch-with-us/) on our website.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://easycatalog.nousmedis.com/getting-started/1.-first-steps/transferring-an-activation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
