Beta is mostly an ISV-side workflow. The mechanics are straightforward; the discipline is using Betas productively and graduating to Released on time.
- Develop the package in a Dev Org
Build the managed package's metadata in a Development Org. Test locally before considering the Beta upload.
- Upload the version as Beta
From the AppExchange Publishing Organization (APO), upload the package version with the Beta flag set. Salesforce generates an install link.
- Share the install link with testers
Send the link to internal QA, partner testers, or pilot customers. Testers install in sandbox or Developer Edition orgs. Document that production install will fail.
- Iterate based on feedback
Each Beta supersedes the previous. Testers may need to uninstall the prior Beta before installing the next. Plan the Beta cycle to be short; long Beta cycles delay real customer value.
- Graduate to Released
When confident, upload the package as Released. The Released version installs in production, supports in-place upgrades, and (for AppExchange) enters Security Review.
- Beta packages cannot install in production. Always tell testers to use sandbox or Developer Edition.
- Beta versions cannot be upgraded in place. Each new Beta requires uninstall and reinstall.
- AppExchange Security Review only runs on Released versions. Beta is a free pre-review channel.
- Production customers must wait for Released. Long Beta cycles delay real value; cut to Released as soon as the build is stable.