Migrate from License Server to IDE Services
If you are using the legacy License Server (also known as Floating License Server or FLS) to manage your licenses, you can switch to IDE Services in a few steps. This is a recommended flow.
Prerequisites for migration
Get started with IDE Services: If you have not started using IDE Services yet, follow this guide to set up your instance.
Set up user authentication: Refer to the instructions on access management.
Customize the client machine configuration file: Update the organization title and logo and customize the Data Collection Statement. Refer to Setting up the client machine configuration for instructions.
Set up License Vault: Configure your License Vault according to your organization’s needs.
- FAQ: If my company has more than one License Server, should I merge them into a single IDE Services instance?
We do recommend merging instances if all your users are connected through the same authentication provider and the granular access rules in IDE Services fully address your license policy requirements. This approach provides more convenient centralized management and billing.
However, merging is not obligatory. If your infrastructure limitations or policies require maintaining multiple separate License Server instances, you can replicate that setup using IDE Services. In this case, each IDE Services instance will be managed and billed separately.
In any case, you can begin by migrating one of your License Servers and test the setup to determine which approach works best.
Instructing your team and migrating
Once your IDE Services instance is up and running, your developers can activate their JetBrains tools through License Vault. Follow these instructions to smoothly migrate your team to IDE Services without disrupting their work.
Notify your team about the migration in advance.
Agree on the specific date and time when the transition will take place. Make sure that your developers get the new activation instructions by this date before you start transferring your licenses.
Instruct your team.
Ask your developers to install the Toolbox App and connect to IDE Services. Make sure to send them an invitation link for the Toolbox App, which can be generated according to the Manage users guide.
If you have several authentication modules, specify which one your users should use to log in. If only one module is set as the default, users will be automatically directed to it when clicking Log in.
Start transferring licenses to IDE Services.
On the agreed date, start transferring the licenses from your existing License Server to License Vault. For instructions, refer to Adding licenses to your License Vault.
For a more controlled and smooth transition, we recommend transferring the licenses in batches. Start by transferring a portion of your licenses and then keep an eye on your License usage statistics and Denials Report for a while. Once you have confirmed that your developers can successfully obtain licenses, move on to the next batch.
Assisted migration
If you are concerned about the migration disrupting your team's workflow, contact us for assistance.
Go to the IDE Services management page in your JetBrains Account.
In the License Vault section, click Migration assistance.
In the popup dialog, click Request migration assistance.
Our Sales team will get in touch shortly to discuss your migration options.
Using License Vault without the Toolbox App
The Toolbox App is required to fully utilize all capabilities of IDE Services. But if your organization currently uses only License Vault and prefers not to use the Toolbox App, your users can activate their JetBrains tools manually. You will need to send them the following information:
The activation instructions along with the URL of your IDE Services instance.
If you have set up automatic server discovery for your IDE Services instance, let the users know they can use the Discover server option in Step 5 of the instruction.
Without automatic server discovery, make sure to share the URL of your IDE Services instance.
If you have several authentication modules, specify which one your users should use to log in. If only one module is set as the default, users will be automatically directed to it when clicking Log in.