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.

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.

Before you complete your move to 2GP package development, it’s critical that you thoroughly test package conversions and subscriber migrations first. See Test Converted Packages and Subscriber Migrations.

Important

  1. To retrieve the source files for your package’s latest converted version, run the sf package version retrieve CLI command. This example retrieves the package metadata for a converted subscriber package version ID into my-folder/ within a Salesforce DX project directory: 
    1sf package version retrieve  --package 04tXXX --output-dir my-folder –-target-dev-hub devhub@example.com
  2. Open the new sfdx-project.json file and update the versionName, versionNumber, and ancestorVersion.
  3. From Setup in the packaging org, enter Package Manager in the Quick Find box, and then select Package Manager.
  4. Click the package that you want to move to 2GP development.
  5. On the package’s detail page, click Move to 2GP.
    The Move to 2GP button on a package's detail page
  6. Carefully review and acknowledge the statements in the Move to Second-Generation Managed Packaging window, then click Proceed.
    The statements to acknowledge before you proceed with moving to 2GP.
After you click Proceed, you can no longer create new major or minor versions in the packaging org. To innovate on the package using 2GP, you create new package versions using the sf package version create CLI command.

You can continue to create 1GP patch versions for versions prior to moving to 2GP development. For example, if you moved package version 6.0.0 to 2GP development, you can create patch version 5.0.1 or 4.1.1 using 1GP, but you can’t create patch version 6.0.1 or later using 1GP.

If a subscriber has installed the version that was moved to 2GP, the subscriber must be migrated to the 2GP version of the package. You create all future patch versions and fixes on 2GP.