Considerations for Package Migrations

Review these limits and considerations for converting and migrating packages.

Packages converted before June 15, 2025 can’t be promoted or migrated. Instead, run the convert command on your latest package version, and move forward with that package version.
The daily package conversion limit is the same as your Dev Hub org’s scratch org allocation. See Scratch Org Allocations for Salesforce Partners for details.
The convert command may fail on your first attempt to convert a package. If this happens, retry again in a few minutes. This issue is most likely to occur if you create a new package for testing purposes, and immediately try to convert that package version.
The package conversion process performs limited validation when creating the managed 2GP package version.
1. In some instances the limited validation could mask issues that would otherwise result in package conversion failure.
2. You can expect to see cryptic error messages in certain scenarios. Please share those error messages with us so we can improve them.
During migration, the managed 1GP package version installed in the target org has the same version number as the managed 2GP migration package version.
Only package versions created using API version 57 (Spring ’23) or above, can be converted. To promote a package version, it must have been created using API version 64 (Summer ’25) or later.
Large packages containing 20,000+ metadata files aren’t supported at this time.
Packages containing Data Cloud metadata can’t be converted.
After you convert a managed 1GP package to 2GP, you can’t transfer the converted package to another Dev Hub org.