First-Generation Managed Packaging Developer Guide

First-Generation Managed Packages
Why Switch to Second-Generation Managed Packaging?
Move to 2GP: Migrate Your Managed Packages with Ease
About Package Conversion and Package Migration
Three Phases of Package Migration Development
Plan Your Package Migration
Before You Begin Package Migrations
Convert Your Managed 1GP Package to 2GP
View Details about Your Converted 2GP Package
Specify Dependencies on Unpackageable Metadata
Test Your Converted Managed 2GP Package
Migrate Your Subscribers from 1GP to 2GP
Considerations for Package Migrations
Troubleshoot Package Conversion Failures
Register a Namespace for a First-Generation Managed Package
Create a First-Generation Managed Package Using a UI
Create a First-Generation Managed Package using Salesforce DX
Components Available in First-Generation Managed Packages
Behavior of Specific Metadata in First-Generation Managed Packages
Package and Test Your First-Generation Managed Package
Update Your First-Generation Managed Package
Publish Upgrades to First-Generation Managed Packages
Manage Licenses for Managed Packages
Manage Features in First-Generation Managed Packages
AppExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Newer Version Available

This content describes an older version of this product. View Latest

View Details about Your Converted 2GP Package

So you’ve converted your 1GP package to a 2GP package. You can use one of two Salesforce CLI commands to retrieve details about your 2GP packages.

To see details about the new managed 2GP package, run: 

1sf package list --verbose

In the verbose command output, there's a column labeled Converted From Package Id. When that field is populated it indicates that the package was originally created using 1GP, and has been converted to 2GP. The 033 ID that displays in that column maps to the original 1GP package.

To see details about the new managed 2GP package version, run:

1sf package version list

If the value in the Released column of the command output is false, this indicates that the package is a beta package version, and you must promote the package to the managed-released state before you migrate the package. See Get Ready to Promote and Release a Second-Generation Managed Package Version.

The package convert command creates a new managed 2GP package, and a new managed 2GP package version, and both are now associated with your Dev Hub org. The association between the Dev Hub org and your package can’t be changed. And you can't associate the package with a second, separate Dev Hub org. This means any subsequent package conversions you initiate for this package, must be associated with the Dev Hub org you specified the first time you converted a particular package.