Inedo’s newest whitepaper, “Migrating from Sonatype to ProGet“ releases this month, available both as a free PDF eBook, or as a series of articles on our blog.

Migrating from Sonatype Nexus to ProGet is more than just copying your packages over. Nexus spreads its features across different products—Repository, Lifecycle, Firewall—while ProGet rolls everything together: storage, SCA, license checks, and governance all live in one place. And while both platforms are private package repositories, ProGet’s feed model gives you finer control out of the box. Things like per-feed policies, connectors, and promotion workflows don’t require extra add-ons the way they do in Nexus.

Our guide, “Migrating from Sonatype to ProGet,” breaks all of this down step-by-step. You’ll see how to set up feeds and connectors, map your existing roles, and recreate common Nexus Firewall or Lifecycle rules using ProGet’s built-in vulnerability and license controls.

Here’s a few of the key points covered inside:

💡 Repositories and Feeds: Understand ProGet’s feed based approach to package storage, including using connectors to proxy OSS packages and implementing approval flows.

💡 Self-Managing Your ProGet Instance: Set up ProGet on Windows, Linux, or in a high-availability cluster, with version upgrades and rollbacks handled effortlessly.

💡 Security and API Keys: Set up administrative and developer roles and permissions, and manage API keys.

💡 Retention and Cleanup Policies: Keep repositories lean and disk space free with customizable, automated feed-level retention policies.

💡Backup and Restore: Protect your data with straightforward and reliable backup and restore processes, and transparent, readable file system.

For planning a smooth migration of your team’s packages to ProGet, download your free copy today!