Repository Migration Status

The migrator tool migrates artifacts one repository at a time and creates a repositories.yaml file that tracks migration status for each repository. A repository can be in the in_progress or completed state. The in_progress state indicates migration has started but not finished. The completed state indicates artifact migration succeeded. If migration has not started, the status field is absent for that repository.

📘
Note
Migration status is maintained only for migration from Nexus 3.

in_progress

When the migrator tool starts migrating artifacts in a repository, it sets the repository status to in_progress in repositories.yaml. If migration is aborted, the migrator tool checks which artifacts already exist in Artifactory and migrates only those that are not yet available.

completed

When all artifacts in a repository are migrated, the migrator tool sets the status to completed in repositories.yaml. If you run the migration again, the tool skips repositories with the completed status.

To migrate new artifacts added to a completed repository, set the repository status back to in_progress and run the migration again. To re-run migration for an entire repository, remove the repository entry from repositories.yaml and run the migration again.

📘
Alternative approach:
To migrate new artifacts added to a repository after the initial migration (delta migration), use the ma (Migrate Artifacts) command with the --force and --check-binary-exists flags. This forces the tool to re-scan the repository and upload only the new or modified artifacts without requiring you to manually edit the repositories.yaml file.
For example
./jfrog-nexus-migrator-<version>.sh ma --force=true --check-binary-exists=true