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
Migrate Your Subscribers from 1GP to 2GP
Move to 2GP Package Development
Test Converted Packages and Subscriber Migrations
Complete the Move to 2GP Package Development
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
AgentExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

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.

Test these scenarios before you complete the move to 2GP.

  • Create 2GP-converted versions for the minimum number of packages necessary to migrate subscribers to 2GP.
  • In test orgs, install the 2GP-converted package versions. Then, test the converted packages thoroughly.
  • Install the corresponding 1GP versions of your packages in your test orgs. Then, migrate these test orgs to 2GP using both manual installs and push upgrades.
  • When you’re comfortable with converting packages and testing migrations, we recommend that you migrate a significant portion of subscribers before completing your move to 2GP package development. After you complete your move to 2GP, any unmigrated subscribers must migrate to 2GP to continue receiving version updates.