
Andrew Hanna

Andrew Hanna

TL;DR: An unmanaged package in Salesforce is a first-generation bundle of metadata that you install once and then own completely: every component becomes editable in the target org, there is no namespace, no IP protection and no upgrade path. It is the right tool for templates, sample apps and one-time transfers. For anything you plan to maintain, move it to an unlocked package.
An unmanaged package is a one-time distribution mechanism. You collect components such as custom objects, fields, Apex classes, flows, layouts and reports, upload them from a packaging org, and share an install link. On install, the contents are unpacked into the target org and behave as if an admin had built them there.
That is the whole trade-off. The installer gets full control, and the publisher gives up any way to push fixes later. For a side-by-side view of both models, see managed vs unmanaged packages in Salesforce.
If the words version, upgrade or subscriber appear anywhere in your plan, an unmanaged package is the wrong choice.
The uninstall-to-upgrade rule is where teams lose data. Before you remove an installed package, capture a known-good state. In Serpent, the Backups view does exactly that, recovers supported org metadata and records, and keeps a Restore History. It complements rollback, and already-deleted data is still harder to reverse cleanly, so back up first. Steps are in the backup and restore guide.
This is the part most guides leave out. There is no in-place conversion, so you rebuild the package from source:
package.xml for those
components and run
sf project retrieve start --manifest package.xml --target-org source.
Our
Salesforce CLI guide
covers the setup.
sf package create --package-type Unlocked --path force-app against your
Dev Hub, then cut a version with
sf package version create --code-coverage. Apex needs at least 75%
coverage before you can promote it.
For step 6, Serpent seeds sample or masked data during environment setup and release pipelines, so scratch orgs and refreshed sandboxes come back populated without a manual script run. If you are building for AppExchange instead, the destination is a managed 2GP package; read the secrets of second-generation managed packages before you start.
Serpent's package development support builds, versions and ships 1GP, 2GP and managed packages on every plan, and maps dependencies so version conflicts surface before a target org sees them. More how-tos live in our SF Guides.
Can you upgrade an unmanaged package?
No. You must uninstall the old version and install the new one, which deletes data in its custom objects and fields.
Do unmanaged packages have a namespace?
No. Components install into the default namespace, which is why name collisions are possible.
Can I list an unmanaged package on AppExchange?
No. Commercial AppExchange distribution uses managed packages, which carry a namespace and pass security review.
Can I convert an unmanaged package into an unlocked package?
Not in place. Retrieve the metadata to source control, then create a new unlocked package from it.
Commitment free!