A structured migration strategy minimizes risk, maintains service continuity, and ensures thorough validation throughout the transition from CodeShip to CloudBees Unify. The following phased approach outlines the recommended stages for a successful migration.
Inventory and Assessment
Start by identifying all active CodeShip Basic and Pro projects. Document build steps, environment configurations, secrets, integrations, and service dependencies. Evaluate each project’s complexity and determine priority based on its business impact and release cycle significance.
Initialization
Begin by setting up CloudBees Unify organization and inviting relevant team members. Connect repositories by integrating with supported source code management systems, such as GitHub or Bitbucket.
Migrate essential secrets, such as API tokens, environment credentials, SSH keys, and registry authentication details. Establish integrations with key external services including GitHub, AWS, GCP, Slack, and artifact repositories to maintain existing workflows and toolchain compatibility.
Enable notifications to track workflow activity and job statuses. Set up email and messaging notifications through the integrations tab. Review available notification options and add appropriate notification steps to workflows to support team visibility and response.
Workload Migration
For each project identified during the initial assessment , create a matching component in CloudBees Unify. Align the component’s structure with the original configuration in CodeShip. Assign relevant variables and secrets to optimize organization and maintain secure, reusable configurations.
Translate existing CodeShip pipeline definitions into workflows using CloudBees-native YAML. Recreate build logic by including parallel steps, conditional logic, build matrices, and Docker references. Ensure these definitions reflect the behavior and intent of the original pipelines.
After running workflows, access detailed run data using the Runs feature. Review job statuses, logs, and result metrics to monitor performance and support debugging or analysis. Conduct test builds to confirm that workflows execute as expected. Verify accuracy of logs, responsiveness of integrations, and integrity of deployments.
Use the dashboard and output data to detect issues and fine-tune configurations as needed.
Finalization
Once workflows have been validated, disable build triggers in CodeShip to prevent conflicts. Closely monitor initial workflow runs to confirm reliability and correctness. After confirming a stable migration, download any needed artifacts from CodeShip and remove legacy project configurations. Complete the transition by deactivating CodeShip accounts in accordance with CloudBees deprovisioning guidance.