> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/add-ons/floating-license/admin/hex-rays-license-server-migration-guide.md).

# Migrate from Legacy Hex-Rays License Server

## Introduction

Up to 9.0 release, our floating license management has been based around the following components:

* the license server manager, lmadmin, provided by Flexera
* the vendor daemon, hexrays, provided by Hex-Rays

As of the IDA Pro new release (9.0) and its new licensing model these have been replaced by:

* The Hex-Rays License Server, and
* lsadm command line tool

Both components are provided by Hex-Rays.

## Differences between the servers

|                    | Flexera                                                                                   | Hex-Rays                                                                                         |
| ------------------ | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| **Server setup**   | Two binaries and processes: `lmadmin` or `lmdrd` server + `hexrays` vendor daemon         | Single binary (`license_server`)                                                                 |
| **Ports required** | Two ports required, plaintext communication                                               | Single TCP port, communication protected by TLS                                                  |
| **OS supported**   | Server available for Windows, Linux, or macOS x64. Manual service configuration on Linux. | Server available for Linux x64 only. Automatic configuration of systemd service at install time. |

## Migration steps

Moving from the 8.4 to the 9.0 license server management infrastructure is really easy:

* First make sure that you have the license server admin guide at hand.
* Follow the installation steps (section 2 of the admin guide).
* Install an IDA 9.0 instance and test your installation by trying to connect to the license server, to select a license, borrow and finally return it.

You are now ready to switch.

## Attention points for the switch

Since an 8.4 client will not be able to connect to the new license server (and a 9.0 client won't be able to connect to the 8.4 license server), you should make sure that all users are using the new clients which are configured with the correct server and port. If your workflow requires using 8.4, you can keep the old server running until all users have switched to the new IDA version. Then you can stop and decommission the old server.


---

# 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://docs.hex-rays.com/add-ons/floating-license/admin/hex-rays-license-server-migration-guide.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.