HOWTO: Migrate from MyGet to ProGet

Migrating your existing MyGet feeds to ProGet is a straightforward process. By bulk downloading your packages from your feeds via MyGet you can then import them into your ProGet feeds. This article will walk through how to use the Bulk Package Import feature to migrate a MyGet feed to ProGet.

Step 1: Download Your MyGet Packages

MyGet allows you to have multiple package types per feed and comes with unique URLs for each package type. However, ProGet requires a different feed for each package type, so you will need to download your packages for each feed type separately.

Your MyGet packages can be easily downloaded by navigating to your MyGet feed and selecting "Download".

This option will provide you with a .zip file which will automatically organize your packages by type, if your MyGet feed contains multiple package types.

An alternative option is to download your MyGet packages by package type using an automated script. This option will require using your MyGet feed URLs.

Each package type in your MyGet feeds will require a different feed URL to be downloaded, available in the Feed Details tab.

Here is a list of simple PowerShell scripts for downloading common MyGet package types:

NuGet Packages

$nugetPath = "<Path to nuget.exe>"
$feeds = @("<Feed One Name>, <Feed Two Name>, <Feed Three Name>")
$outputRoot = "<Choose Output Folder Location>"
New-Item -ItemType Directory -Path $outputRoot -Force | Out-Null
foreach ($feedURL in $feeds) {
    Write-Host "Fetching packages from: $feedURL"
    $packages = & $nugetPath list -Source "https://www.myget.org/F/$feedURL/api/v2" -NonInteractive | ForEach-Object {
        ($_ -split ' ')[0]
    }
    foreach ($packageID in $packages) {
        Write-Host "Downloading $packageID..."
        & $nugetPath install $packageID -Source "https://www.myget.org/F/$feedURL/api/v2" -OutputDirectory "$outputRoot\$feedURL\$packageID" -NonInteractive -DependencyVersion Ignore -Prerelease
    }
}

npm Packages

$packages = @("<Packge One Name>", "<Package Two Name>")
$feed_url = "<Feed URL>"
$outputRoot = "<Choose Output Folder Location>"
New-Item -ItemType Directory -Path $outputRoot -Force | Out-Null
foreach ($package in $packages) {
    Write-Host "Packing $package from $feed_url"
    Set-Location $outputRoot
    cmd /c npm pack $package --registry $feed_url | ForEach-Object {
        Write-Host "Downloaded: $_"
    }
}

PyPi Packages

$pipExe = "pip"
$packages = @("<Packge One Name>", "<Package Two Name>")
$feed_url = "https://www.myget.org/F/<Feed Name>/simple/"
$outputRoot = "<Choose Output Folder Location>"
New-Item -ItemType Directory -Path $outputRoot -Force | Out-Null
foreach ($pkg in $packages) {
    Write-Host "Downloading: $pkg from $feed_url"
    & $pipExe download $pkg --no-deps --index-url $feed_url --dest $outputRoot    
    if ($LASTEXITCODE -ne 0) {
        Write-Warning "Failed to download $pkg"
    } else {
        Write-Host "$pkg downloaded successfully."
    }
}

Step 2: Create a Feed in ProGet

ProGet supports the creation of multiple feed types, but for demonstration purposes we will be migrating a NuGet feed from from MyGet to ProGet.

To create a new feed, navigate to the banner at the top of the page and click on "Feeds". Next select "New Feed".

Then select the package type. In this case, we will select "NuGet (.NET) Packages".

As we will be uploading packages from our MyGet feed, here we will select "Private/Internal NuGet (.NET) Packages".

Now name your feed. We will call ours internal-nuget.

You'll be taken to your new NuGet feed, currently empty.

Step 3: Import Packages to ProGet

Now we have created a NuGet feed, we can import our MyGet packages. From the "View Packages" tab, navigate to the dropdown menu and select "Import Packages".

To upload your packages, select "Import/Copy Package Files on Disk".

Next, enter the file path of the downloaded packages from your MyGet feed and select import.

The internal-nuget you created is now populated with your imported MyGet packages.