Skip Navigation

First-Generation Managed Packaging Developer Guide

j

Summer '26 (API version 67.0)

Spring '26 (API version 66.0)

Winter '26 (API version 65.0)

Summer '25 (API version 64.0)

Spring '25 (API version 63.0)

Winter '25 (API version 62.0)

Summer '24 (API version 61.0)

Spring '24 (API version 60.0)

Winter '24 (API version 59.0)

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

AppExchange App Analytics for First-Generation Managed Packages

Developing and Distributing Unmanaged Packages

First-Generation Managed Packages

/

Move to 2GP: Migrate Your Managed Packages with Ease

/

Move to 2GP Package Development

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.