The migrator tool has been deprecated and you should use the new transfer commands available with the JFrog CLI for transferring settings and binaries from a self-hosted JFrog installation to JFrog Cloud. For more information, see Transfer Artifactory Configuration and Files to JFrog Cloud.

JFrog Cloud provides the same cutting edge functionalities of a self-hosted JFrog Platform Deployment (JPD) without the overhead of managing the databases and systems. If you are an existing JFrog self-hosted customer, you might want to move to JFrog Cloud for the ease of operations. The JFrog Cloud Migrator Tool enables you to replicate your self-hosted JPD to a JFrog Cloud JPD quickly and painlessly. For more information on configuring and running the migration tool, see JFrog Cloud Migrator Tool.

The migration tool supports migrating artifacts together with their metadata and your configuration settings. The migration tool also supports complex scenarios like one-to-many and many-to-one migrations. 

You must run the tool on the same machine as the self-Hosted JPD. The self-hosted instance can remain active during migration, but you have to take into account the network and bandwidth impact. For more information, see Migrator Tool Performance Enhancements.

Currently, the JFrog Cloud Migration Tool migrates only the JFrog Artifactory in a JPD. You cannot migrate other products such as JFrog Xray and JFrog Pipelines.

This section, contains following pages that provide you information on migration.

Migration Scenarios

The migration tool facilitates the following use cases.

Migrate a Self-Hosted JPD into a JFrog Cloud JPD

You can migrate your existing user settings and configurations along with the repositories and artifacts from a self-hosted JPD to JFrog Cloud. All pre-existing configuration and artifacts that exist in the JFrog Cloud is overwritten by the contents of the self-hosted JPD. You can continue to use the self-hosted JPD and sync the artifacts and repositories with JFrog Cloud. Configuration information is not automatically synchronized and you have to enable Access Federation to synchronize the changes in configuration.

Copy Artifacts from a Self-Hosted JPD to JFrog Cloud JPD

If you have an existing JFrog Cloud JPD, you can migrate your artifacts from a self-hosted JPD to JFrog Cloud. You must create the repositories that you wish to migrate from the self-hosted JPD in JFrog Cloud before you start the migration process. You cannot migrate your configuration information from the self-hosted JPD.

Consolidate Several Self-Hosted JPDs into a Single JFrog Cloud JPD

You can migrate repositories and artifacts from all JPDs to a single JFrog Cloud JPD. But you can migrate configuration data only from a single self-hosted JPD. To migrate configuration settings for all self-hosted JPDs to JFrog Cloud use Access Federation to consolidate the configuration data between the self-hosted JPDs before you start the migration process .

Before You Begin

  1. Set up a JFrog Cloud instance and contact your account owner to enable migration for the instance.
  2. Ensure that you have the administrator credentials for both the source and target JPDs
  3. The JFrog Cloud migration tool is available as a plugin for JFrog CLI. You must set up JFrog CLI on the self-Hosted  JPD. For more information, see Configuring JFrog CLI
  4. Add the migration tool plugin to JFrog CLI. For more information, see Adding the JFrog Cloud Migrator Tool to JFrog CLI.

Source JFrog Platform Requirements

The migration tool supports migration of artifact and configuration settings from any version of Artifactory 7.x and Artifactory version 6.23.21 and later. The space required to run the migration tool depends on the size of the artifacts. The migration tool performs a check before proceeding with the migration. You can disable this check if required. For more information, see Space Requirements.


  1. You must run the migration tool from the machine that hosts the self-hosted JPD.
  2. The user running the tool must have sufficient permissions to access the JFrog home folder and JFrog CLI home folder.
  3. The user must have sudo permission to run the migration tool.
  4. The user that runs the Artifactory service in the self-hosted JPD must have write permissions on the <work-dir> folder. The <work-dir> folder by default is the JFrog CLI home directory.


The following limitations need to be kept in mind before you start the migration process

  • The Archive Search Enabled feature has been deprecated on JFrog Cloud. If you are using this feature in your self-hosted JPD, reach out to JFrog Support before you start the migration.
  • System Properties are not migrated and JFrog Cloud defaults are applied after migration. Reach out to JFrog Support before you start the migration to clarify this impact.
  • Artifacts in remote repositories and federated repositories are not migrated.
  • User plugins are not migrated.
  • Artifact properties longer than 2.4K characters are not supported in JFrog Cloud. Properties greater than 2.4 K characters are generally seen in Conan artifacts.
  • Artifact Cold Storage is not supported in JFrog Cloud.
  • Xray, Distribution, and Insight is not support by the migrator tool.
  • Some artifacts might be blocked from download by certain Xray policies. You must align your migration plan accordingly.

Migration Process

The migration process consists of the following steps.

Step 1: Set Up the JFrog Cloud Instance for Migration

You can skip this step if you want to migrate the artifacts alone and not the configuration

  1. Configure a JFrog Cloud instance according to your requirements.
  2. Contact the account owner to enable the cloud instance for migration.
  3. You will receive an email with the migration guidelines.

  4. Log into the MyJFrog Portal to generate the token for the JFrog Cloud Migration Tool.
    MyJFrog Portal is JFrog’s Cloud solution for cost management and billing services. For more information, see MyJFrog Cloud Portal.
    You cannot generate a token unless the cloud instance is enabled for migration. For more information, see Generating Admin Token for Migration.

Step 2: Configure the Source and Target Environments

  1. Configure JFrog CLI for both the source and target JFrog Platform servers. For more information, see Configuring JFrog CLI.
  2. Install the migrator-tool plugin for JFrog CLI. For more information, see Adding the JFrog Cloud Migrator Tool to JFrog CLI.
  3. Run the migration tool with the migrate-config command to set the source and target JFrog Platforms and the token to access JFrog Cloud. For more information, see Configuration Command Options.

    Do not proceed to the next step unless the configuration command runs successfully. You can skip this step if you wish to transfer the artifacts alone and no other data.

  4. Configure the JFrog CLI for the target JFrog Platform server with the source JFrog Platform credentials since the configuration command overwrites the target JFrog platform with settings from the source platform.

Step 3: Enable Push Replication

  • Enable push replication to the target JFrog Cloud instance from the source JFrog Platform so that you can migrate the artifacts that are added to the self-Hosted JFrog Platform instance after you start the migration process. For more information, see Push Replication.
    We recommend that you s
    etup the replication before starting the artifact migration and after migrating the configuration, thereby preventing a full replication and replicate only based on events. This is the preferred approach, if you have repositories with a large number of artifacts.
    You can use the migrator tool to set up push replication with the set-replication command. For more information, see Set Replication Command Options.
    If you manually configure push replication, use a cron expression to a time farther away (for example, 2-3 weeks away). If you use a cron which is very near, it might jam the network bandwidth and resources during the cron trigger.

Step 4: Run the Migrator Tool

  1. Run the JFrog Cloud Migration Tool with the migrate-artifacts command to start the migration.
    You can provide options to the tool based on your network and the size of the Artifactory database and filestore. For more information, see Migrate Artifacts Command Options.

    The tool might cause a network slowdown if you do not configure the parameters based on your needs.  

    The tool copies artifacts and other settings from the self-Hosted system to your JFrog Cloud instance. The time required to complete the task depends on the network speed and the volume of data. The tool provides a pause/resume function to manage the migration activity.

  2. Run the JFrog Cloud Migration Tool with the status command to check the migration status. You can run the command during the migration process to see the current status of the migration. For more information, see Status Command Options.

Step 5: Post Migration Actions

  • After you complete the migration, ensure that you verify the post-migration actions to check if there are any issues that need to be resolved. For more information, see Post Migration Actions.