Run the script with the options in the following order if you want to go through the different stages individually.
config
getConfig
createRepo
migrateArtifact
migrateSecurity
The following table provides information about the options available with the migrator script.
Option | Description |
---|---|
| Run the migration script in a single step.
For example, /jfrog-nexus-migrator-<version>.sh all --disable-security-migration="true" |
| Configure information about Artifactory and Nexus Repository. |
| Get configuration information from Nexus Repository.
For example, /jfrog-nexus-migrator-<version>.sh gc --disable-security-migration="true" |
| Create target repositories in Artifactory. |
| Migrate artifacts from Nexus Repository to Artifactory. You can use the following optional commands when you migrate from Nexus 3.
|
| Migrate users, groups, and permission targets from Nexus Repository to Artifactory. |
You can run the migration script with the getConfig
, createRepo
, migrateArtifact
, and migrateSecurity
options in sequence to load the new objects from the currently configured Nexus Repository Manager to Artifactory. If you pause the migration process on a Nexus 3 installation and resume at a later time, the migrator tool migrates only those repositories and security entities added after you paused the process. In case of migration on a Nexus 2 installation, the migrator tool migrates all repositories and security entities in the Nexus repository regardless whether they were migrated before you paused the migration process.
Note
If you convert an existing repository to a federated repository, the migrator tool will migrate new artifacts to the federated repository.
The migrator tool creates YAML files and JSON files based on the Nexus Repository Manager inside the folder, <working directory>/migration/nexus-migrator
.
The migrator tool creates the following configuration files:
migrationConfig.yaml
repositories.list
repositories.yaml
security.json
securityLdapConf.yaml
securityRegexMap.list