Migrating to Cloudsmith

This help doc will walk you through the steps involved in migrating packages, artifacts, binaries, images, or zip files into Cloudsmith. If you have any trouble migrating, contact us, and we will be happy to assist in the process.

Migrating from another package repository requires the following:

• Export the packages out of your old repositories like JFrog's Artifactory or Sonatype Nexus.
• Importing to Cloudsmith
• Optional setup requirements

Exporting from another repository

If you have been running another repository manager, such as Artifactory, Nexus, MyGet or ProGet and you want to migrate your package hosted on this repository to Cloudsmith, the first step is exporting the packages out of your old repository.

Depending on your package repository and/or package format, you will have to use different approaches to exporting your packages. We have the following documentation on how to:

• Export any package from JFrog Artifactory
• Export from Nexus Sonatype
• Export NuGet packages from any package repository

📘

Export details not here? Contact us and we'll help!

Import into Cloudsmith

After the export, you are ready to import the packages into your new Cloudsmith repository - Yay!
We will assume you have exported all your packages/artifacts/binaries into a folder or a shared location (e.g. S3 bucket).

Importing your packages into Cloudsmith should be a stress-free process; you will need to:

• Create an organization and at least one repository on your Cloudsmith account. it should only take 60 seconds
• Install the Cloudsmith CLI and export your API token.
• Do a bulk import of your packages per package format using the Cloudsmith CLI. For a build import from a folder, follow the instructions here.
• We have specific instructions for certain package types :
  • Import Maven
  • Import npm
  • Import NuGet
  • Import Docker
  • Import Python

📘

Import details not here? Contact us and we'll help!

Other settings to consider

If you are migrating packages and setting up Cloudsmith for the first time, you may need to consider other tasks when getting started, including:

• Update your build tools and configurations to push/pull to the new Cloudsmith endpoints. You may have a configuration file for every package format in your code base, you will find information on how to set up Cloudsmith for each format here.
• Setup your Single Sign-On and Group Mapping instructions if this is your preferred way to log in to your users.
• Setup your upstreams, which will set up Cloudsmith to fetch and cache your 3rd party dependencies hosted on public repositories like NuGet Gallery, RubyGems.org or Maven Central.
• Setup signing keys.
• Setup your service accounts.
• Setup your logs export to s3.
• If you are a distributor, you may want to set up Entitlement tokens to distribute to 3rd parties
• Setup Custom Domains, which allow you to present your brand and domain when distributing from Cloudsmith.