Documentation
Book a demo

Migration phases

Phase 4: Validation and decommissioning

With your Cloudsmith Workspace configured and the migration executed through pilot, rollout, and cutover, the final phase validates the result and decommissions the platform you are leaving.

Validation milestones

Workspace configuration complete

All key elements are in place, including repository structures, access controls, and automation integrations. Validation at this stage confirms readiness for production artifact flows.

Pilot ready

A successful pilot means selected teams have validated core functionality in Cloudsmith, confirming performance, compatibility, and integration integrity across their workflows.

Rollout complete

Wider adoption has reached multiple teams or business units. Depending on your migration strategy, you may have staged the rollout or run it in parallel across environments. At this point, teams use Cloudsmith in production.

Note

Rollout is often split into multiple waves, based on your organizational structure and how critical each system is.

Cutover complete

Cloudsmith is now the primary artifact management platform. All build, deployment, and consumption workflows run within Cloudsmith.

Onboarding complete

All relevant teams have access based on their roles, and have been trained. Documentation, process ownership, and support paths are agreed, with feedback loops in place.

Decommissioning

Once the validation milestones are met, you can retire the legacy platform. Work through the following in order:

  1. Archive any historical data you need for audit or regulatory purposes, so compliance obligations remain satisfied after the platform is gone.
  2. Revoke credentials and remove network access to the legacy platform, which closes off a set of unused entry points.
  3. Update all CI/CD pipelines and documentation to reference Cloudsmith as the single source of truth for artifacts.
  4. Tell your stakeholders the transition is complete, and where to go for support.

Before you decommission anything, confirm that:

  • All artifact traffic flows through Cloudsmith.
  • Monitoring and alerting is operating against Cloudsmith.
  • No mission-critical dependency still resolves from the legacy platform.
  • A rollback plan is documented and reviewed.

Next steps

If you need help at this stage, see Migration support.