Help Center/ CodeArts Artifact/ Best Practices/ Migrating Repository Data from Nexus to CodeArts Artifact/ Migration Preparations
Updated on 2026-03-13 GMT+08:00
View PDF
Share

Migration Preparations

In enterprise software development, teams often need to manage numerous dependencies, which may be spread across different repositories, such as hosted, proxy, and group repositories in Nexus. However, this distributed management complicates operations and reduces efficiency. How can we manage all repositories centrally and streamline operations? CodeArts Artifact provides a batch migration tool to quickly migrate hosted, proxy, and group repository data on Nexus to self-hosted repos. This streamlines operations and management for greater efficiency.

Confirming Repository and Package Types

The following uses Nexus3 as an example. Log in to Nexus3 and go to the administration page. Confirm the repository type (in the Type column) and package type (in the Format column) to be migrated, as shown in the following figure.

The migration method varies depending on the repository type (in the Type column).

Confirming CodeArts Artifact Repository Capacity

Check the number and size of files displayed in Blob Stores (as shown in the following figure) to evaluate whether the remaining repository capacity of CodeArts Artifact meets the requirements.

Confirming Repository Usage Scenario

Repositories are provided for all projects. You are advised to create a project separately. For details about how to create a project, see Creating a CodeArts Project.

If projects are planned with separate repositories, you do not need to create a project.