jf rt transfer-config

Copy full Artifactory configuration from a source Artifactory server to a target Artifactory server.

Synopsis

jf rt transfer-config <source-server-id> <target-server-id> [options]

Aliases: —

Arguments

Argument	Required	Description
`<source-server-id>`	Yes	Server ID to export configuration from
`<target-server-id>`	Yes	Server ID to import configuration to

Options

Flag	Default	Description
`--exclude-repos`	—	Semicolon-separated list of repositories to exclude. Supports wildcards
`--force`	`false`	Set to true to allow transfer to a non-empty Artifactory server
`--include-repos`	—	Semicolon-separated list of repositories to include. Supports wildcards
`--prechecks`	`false`	Set to true to run pre-transfer checks
`--source-working-dir`	`$JFROG_CLI_TEMP_DIR`	Local working directory on the source server
`--target-working-dir`	`/storage`	Local working directory on the target server
`--verbose`	`false`	Set to true to increase verbosity during export

Examples

Verify Command Help

jf rt transfer-config --help

Transfer Full Configuration

jf rt transfer-config source-server target-server --force

Transfer Specific Repositories

jf rt transfer-config source-server target-server --include-repos "libs-release;libs-snapshot"

Run Pre-Transfer Checks

jf rt transfer-config source-server target-server --prechecks --verbose

Warning: This action wipes all Artifactory content on the target server. Use --force only when you intend to overwrite existing configuration.

When to Use

Use transfer-config when migrating an entire Artifactory instance to a new server — for example, moving from self-hosted to JFrog Cloud (SaaS), or upgrading to new infrastructure. This copies all repositories, users, groups, permissions, and other configuration.

Choose this vs alternatives:

Scenario	Use This Command
Full migration to a new empty server	`jf rt transfer-config`
Add repos from source to existing target without wiping	`jf rt transfer-config-merge`
Move only files (config already transferred)	`jf rt transfer-files`

Prerequisites

Install the data-transfer plugin on the source server: jf rt transfer-plugin-install <source-server>
Both source and target servers must be configured: jf config add
Admin access tokens are required for both servers
Target server should be empty unless you use --force

Known Limitations

The target server content is wiped unless --force is used (and even with --force, existing data is overwritten)
Very large configurations (thousands of repositories) may take significant time for pre-checks
Some configuration elements (for example, custom plugins, LDAP settings) may require manual migration
The source server must be accessible from the machine running the CLI