You can copy or move artifacts to different repositories. The destination repository must be of the same package type as the item you want to move, or a Generic type. For example, you can only move a Debian artifact to a local Debian repository or a local Generic repository.
Note
Copy operations are executed using Unix conventions. For example, copying org/jfrog/1 from a source repository to org/jfrog/1 in a target repository will result in the contents of the source being copied to org/jfrog/1/1.
To achieve the same path in the target repository, copy the source into one folder up in the hierarchy. In the above example, that would mean copying source org/jfrog/1 into target org/jfrog.
Requirements: For move operations, you need DELETE permissions for the source repository and DEPLOY permissions for the target repository.
To move or copy an artifact or folder:
On the Artifacts page, right-click the item in the browser.
Select Copy Content or Move Content.
A Move or Copy window appears.
Select a destination from the Target Repository list.
The available repositories include local repositories and virtual repositories with a default deployment repository configured. The repositories are either Generic or match the package type of the selected item.
Optionally, select the custom path checkbox and enter a location within the target repository in the Target Path field. If you do not enter a target path, the source will be copied into the target repository's root folder.
Warning
If you are copying or moving your source artifacts to a repository with a different layout, specifying a custom path suppresses cross-layout translation. This means that your client may not be able to resolve the artifacts, even in cases of a same-layout operation.
Optionally, click Dry Run to simulate the copy or move operation and check for warnings or errors. For more information, see Dry Run.
Click Copy or Move to complete the operation.
All metadata is updated once the operation is completed.
Dry Run
An operation may fail or generate warnings for several reasons. For example, the target repository may not accept all the items due to its own specific policies, or you may not have the required permissions to perform the operation.
Before actually doing an operation, you can check if it will succeed without errors or warnings by clicking Dry Run. JFrog Artifactory runs a simulation of the operation and shows applicable errors or warnings.