YouTrack Server
 
2019.2
Get YouTrack Standalone
You are viewing the documentation for an earlier version of YouTrack Server. View this page in the current documentation
  1. Installation and Upgrade
  2. Working with External Hub
  3. Migrate YouTrack Data to External Hub

Migrate YouTrack Data to External Hub

Last modified: 17 December 2019

YouTrack comes with a built-it Hub service. This service handles user and access management for the application.

To switch your current installation of YouTrack to use an external standalone Hub service, you need to migrate the user, access, and project-related data to this external Hub. Starting with YouTrack 2018.2, you can connect any type of YouTrack Standalone distribution to an external Hub service.

warning

Two-factor authentication

The service that supports Hub to Hub migration uses an application token for authentication. The service doesn't support two-factor authentication.

If you need to migrate Hub data to an external installation, you need to disable 2FA for the account that you use to log in to the migration service. Once the migration is complete, you can re-enable 2FA for your account.

For more information about connecting JetBrains team tools to Hub, refer to the Hub documentation.

To migrate data from built-in Hub to an external Hub service:

  1. Install and configure an external Hub server.

  2. In the YouTrack instance with the built-in Hub, create a backup of the database.

  3. Open and log in to the YouTrack migration service:

    • To open the migration service, open the Administration menu > Hub Integration and click the Migrate to external Hub link in the information pane on the page.

      External hub migration link

      • The log in page for the application migration service opens.

      Migration log in to console

    • Log in to the migration service.

      To log in to the migration service, you need to prove that you are a system administrator and have access to the file system of the server where the application is installed. To confirm your access rights, the migration service asks for a token that is located on the application server.

      • Click the Show token location link.

      • Open the awcToken.properties file that is stored on the server.

      • Paste the token from the file into the Token field.

      • Click the Log in button.

  4. Enter the base URL of the external Hub server.

  5. Click the Verify URL button.

  6. Click the Accept button to confirm the request access to the external Hub service.

    • The migration process starts.

  7. Review and resolve conflicts (if any were found) and confirm the migration.

    • The data from the built-in Hub is migrated to the external Hub service.

    • When finished, the application uses the external Hub service for user and access management.

    • The built-in Hub service is shut down.