#Migrating Alauda DevOps to Alauda DevOps (Next-Gen)

This guide details the upgrade strategy and procedures for Alauda DevOps to Alauda DevOps (Next-Gen) when migrating from Alauda Container Platform v3.16 or v3.18 to v4.0.

#Prerequisites

#Upgrade ACP Platform

First, upgrade the ACP platform to version v4.0. For detailed instructions, refer to .

#Upgrade Alauda DevOps to v3.20

After upgrading ACP to v4.0 version, you must first upgrade Alauda DevOps to v3.20 version in order to complete the migration from Alauda DevOps to Alauda DevOps (Next-Gen). Please refer to Upgrading Alauda DevOps to v3.20

#Migrating Alauda DevOps

Starting from ACP v4.1, the following Alauda DevOps v3 Operators will no longer be maintained, so it is strongly recommended that you complete the migration on ACP v4.0 as described in this document.

#Download the Operator

1.Download the following versions of the Operators separately or in bulk based on templates from the Alauda customer portal.

2.Navigate to the CLI Tools section in the Alauda Customer Portal and download the violet tool to upload Operators toACP, For specific operation steps, refer to .

#Migrating Alauda DevOps

Please refer to the following documents for migrating each operator:

• Migrating Alauda DevOps Pipelines
• Migrating Alauda Build of Gitlab
• Migrating Alauda Build of Harbor
• Migrating Alauda Build of SonarQube
• Migrating Alauda Build of Nexus

#Next Steps

You have now completed the migration from Alauda DevOps to Alauda DevOps (Next Generation). In Alauda DevOps (Next Gen), if you want to use the updated version for each Operator, you can further learn how to upgrade to the updated version in each operator's documentation.