Migrating to Cloudsmith
Migration phases
Like building software, a successful migration means understanding your goals, designing the right solution, planning phased activities, documenting each step, and executing methodically while tracking progress and resolving issues as they arise. Working in phases keeps delivery continuous for your developers, gives your stakeholders a clear view of progress, and creates the opportunity to improve your existing setup rather than replicate it.
The four phases
| Phase | Title | Description |
|---|---|---|
| Phase 1 | Project initiation | Establish a migration team, guided by the Customer Success team and led by key stakeholders from your organization. Define the scope and objectives of the migration. |
| Phase 2 | Discovery and migration planning | Build a detailed understanding of your current solution and design a clear target state. Develop a migration plan to reach that target, and identify key dates, milestones, and risks. |
| Phase 3 | Migrating your artifacts | Move your artifacts to Cloudsmith incrementally or in bulk, based on your chosen strategy. Provision your teams and pipelines with the access they need, then test and refine the process. |
| Phase 4 | Validation and decommissioning | Validate that Cloudsmith is running smoothly for your teams, then decommission your previous solution. Document any outstanding issues or improvements. |
Each phase has an exit point, so you can confirm what has been agreed before the next one begins. Phase 1 sets the scope, Phase 2 produces the design, Phase 3 moves the artifacts, and Phase 4 retires the platform you are leaving.
Next steps
Start with Phase 1: Project initiation.
