First-Generation Managed Packaging Developer Guide
jWhy Switch to Second-Generation Managed Packaging?
About Package Conversion and Package Migration
Three Phases of Package Migration Development
Plan Your Package Migration
Before You Begin Package Migrations
Migrate Your Subscribers from 1GP to 2GP
Test Converted Packages and Subscriber Migrations
Complete the Move to 2GP Package Development
Considerations for Package Migrations
Register a Namespace for a First-Generation Managed Package
Newer Version Available
Move to 2GP Package Development
After you thoroughly test converted packages and migrations, complete your move to 2GP development.
-
Test Converted Packages and Subscriber Migrations
When you complete your move to 2GP development, you can no longer create any new major or minor 1GP versions of that package. Before you make this transition, it’s critical that you thoroughly test packages converted to 2GP and the migration of subscribers to 2GP. -
Complete the Move to 2GP Package Development
To fully transition to 2GP package development, you retrieve the source files for your package’s latest converted version. Then, you confirm in Setup for your packaging org that you’re ready to develop and distribute your package solely using 2GP packaging.