Help Center/
CodeArts Repo/
User Guide/
Migrating Code and Syncing a Repository/
Migrating a Third-Party Git Repository to CodeArts Repo/
Migrating a Codeup Repository
Updated on 2025-07-24 GMT+08:00
Migrating a Codeup Repository
Prerequisites
- Configure the personal access token by referring to Configuring an Access Token.
- Obtain the Apsara DevOps URL by referring to Configuring the Apsara DevOps Access Point.
- Obtain the organization ID by referring to Obtaining the Organization ID.
Prerequisites
As shown in the following figure, you must have the permission to create repositories. For details, see Configuring Project-Level Permissions.
Figure 1 Permissions required

Steps
- Go to the CodeArts Repo homepage, click New Repository, and select an existing project from the Project drop-down list box or create a project.
- Set the repo type to Imported and import from Codeup.
- Obtain and fill in the Apsara DevOps URL by referring to Configuring the Apsara DevOps Access Point. The format is https://Apsara DevOps URL.
- Obtain and fill in the Organization ID by referring to Obtaining the Organization ID.
- Obtain the personal access token and fill in the Authorization by Personal Access Token box by referring to Configuring an Access Token. If an error message indicating authorization failure is displayed, it means your access token is incorrect or invalid. In this case, reconfigure your access token in Codeup.
- Select repositories to be imported, click Next, click OK, and the project repositories list is displayed. Set Basic Information and Repo Sync Settings by referring to Configuring Basic Information for a New Repository and table 1 parameters for synchronizing a repository.
- If the following figure is displayed, the Codeup repository is successfully imported.
Figure 2 The Codeup repository is successfully imported.
Parent topic: Migrating a Third-Party Git Repository to CodeArts Repo
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot