> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/artifact-registry/3.0/artifacts/copy-a-version.md).

# Copy a version

Copy a single artifact version to another Harness registry in a different project or organization, without re-pushing from your local machine.

Copy Version moves one artifact version from a source registry to a target registry within Harness. Use it to promote a validated image from a development registry to a staging registry, or to make an artifact available in a different project without pushing again from your machine.

The artifact's name and version identifier are preserved in the target registry. The operation copies the version data only; it does not copy registry configuration, policies, or metadata from the source registry.

If you need to use a different artifact name in the target registry, download the artifact and push it under the new name.

## Before you begin

To copy a version, your role must include:

* **View** permission on the source registry
* **Create/Edit** permission on the target registry

If the Copy Version option does not appear, ask your account administrator to review your role assignments. Go to [RBAC and permissions](https://developer.harness.io/artifact-registry/3.0/reference/rbac-and-permissions.md) for the full permission list.

## Copy a version

1. **Open the artifact's version list**. In the navigation menu, select **Artifacts**. Click the artifact name to open its version list.

   Alternatively, navigate to the source registry, select the **Packages** tab, and click the artifact.
2. **Open the row menu for the version**. Find the version you want to copy. Click **Show more actions** (**⋮**) at the end of that row.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Copy Version or Copy Command</strong></p><p>The row menu shows both <strong>Copy Version</strong> and <strong>Copy Command</strong>. <strong>Copy Command</strong> copies the client pull command text to your clipboard. <strong>Copy Version</strong> opens the dialog to move the version to another registry. Select <strong>Copy Version</strong>.</p></div>
3. **Choose the target registry**. The Copy Version dialog shows the source registry, artifact name, and version as read-only fields.

   Under **Target**, select the **Organization**, **Project**, and **Registry** where the version should be copied. If the **Registry** dropdown is empty, select an organization and project first; the registry list is scoped to the project you choose.

   The target registry must be the same package type as the source. A Docker version can only be copied to another Docker registry.
4. **Confirm the copy**. Select **Copy Version** to start the operation, or **Cancel** to exit without changes.

   When the copy completes, the version appears in the target registry under the same artifact name and version identifier.

## Copy with the hc CLI

To copy versions from the command line or from automation, use the `hc` CLI. Go to [CLI reference](https://developer.harness.io/artifact-registry/3.0/reference/cli.md) for syntax and examples.

For Docker images, you can also use `skopeo` to copy between registries. Authenticate to each registry using the identity token from **Setup Client** as the password. Use `_token` as the username for service account tokens, or your Harness account email for Personal Access Tokens. Go to the [skopeo documentation](https://github.com/containers/skopeo) for installation and usage.

## Troubleshooting

<details>

<summary>Can I rename the artifact while copying it?</summary>

No. Copy Version preserves the original package name and version identifier. To use a different name, download the artifact and push it under the new name in the target registry.

</details>

<details>

<summary>Can I copy more than one version at a time?</summary>

No. Copy Version copies one version at a time. For bulk operations, repeat the copy for each version or use `skopeo` for Docker images.

</details>

<details>

<summary>The target Registry dropdown is empty</summary>

The dropdown shows only registries that match the package type of the source artifact and exist in the selected project. Create a registry of the matching type in the target project, then retry the copy.

</details>

<details>

<summary>Copy Version fails with a permissions error</summary>

Your role on the target registry may not include Create/Edit. Ask your account administrator to assign a role with Create/Edit permission on that registry. Go to [RBAC and permissions](https://developer.harness.io/artifact-registry/3.0/reference/rbac-and-permissions.md) to review what permissions are required.

</details>

## Next steps

* [Browse and search artifacts](https://developer.harness.io/artifact-registry/3.0/artifacts/browse-and-search.md)
* [Delete an artifact or version](https://developer.harness.io/artifact-registry/3.0/artifacts/delete-an-artifact.md)
* [CLI reference](https://developer.harness.io/artifact-registry/3.0/reference/cli.md)

{% @harness-feedback/feedback %}
