License Management Organization (LMO)
The License Management Organization (LMO) is the Salesforce org that an AppExchange partner designates as the home for their License Management Application (LMA).
Definition
The License Management Organization (LMO) is the Salesforce org that an AppExchange partner designates as the home for their License Management Application (LMA). Every managed package an AppExchange partner offers gets linked to exactly one LMO; when customers install the package, Salesforce creates License records in that LMO. The partner uses the LMO to track every customer install, manage subscriber data, run partner-side reporting, and integrate with their billing system. The LMO is the partner-side mirror of the customer''s Salesforce subscription business.
Designation of the LMO is a one-time decision made when the partner registers their first managed package with the Salesforce Partner Program. Most partners use their primary internal Salesforce org as the LMO; some create a dedicated org separated from internal sales-and-service operations. The decision is permanent in practice: re-pointing managed packages to a different LMO requires Salesforce Partner Support intervention and risks losing License history. Picking the LMO wisely at registration is one of the highest-stakes early decisions for any new AppExchange partner.
Why LMO designation is a permanent decision
One LMO per partner per package
An AppExchange partner can have one LMO that hosts the LMA for all of their managed packages. Some large partners with separate product lines designate different LMOs per product, but Salesforce strongly recommends a single LMO for simplicity. The LMO designation happens through the Partner Console when the partner first registers a managed package.
Internal-org vs. dedicated-org tradeoffs
Most partners use their primary Salesforce org (the one running their internal CRM) as the LMO. The advantage is unified data: Sales pipeline, Service cases, and License records all live in one place. The disadvantage is permission complexity: every internal user with broad access can see License records by default. Some partners create a dedicated LMO to isolate licensing data; the tradeoff is the duplication of customer Account records across two orgs.
LMO selection criteria
Pick the LMO with three criteria in mind: who needs access to License data (typically support, customer success, partner ops), what other systems the LMO will integrate with (billing, support, marketing), and the long-term stability of the org (a sandboxed test org should never be an LMO). The right LMO is usually the partner''s primary production org.
Switching LMOs
Salesforce supports LMO changes but treats them as significant administrative work. The partner submits a Partner Support case; Salesforce re-points the managed package to the new LMO; License records do not migrate automatically. Existing customers'' License records stay in the old LMO; new installs go to the new LMO. The transition window produces a messy bifurcated install base unless carefully managed.
Trial-org pitfalls
The single most common LMO mistake is designating a Developer Edition or trial org as the LMO during initial testing. The trial org has a finite lifespan; when it expires, the LMA is unreachable, and the partner has to recover with Partner Support. Use a permanent, paid org as the LMO from day one.
Org-level permissions and visibility
The LMO''s sharing model applies to License and Subscriber records. By default, the partner''s admin sees all License records; other users see only what sharing rules grant. Partners with sensitive customer data on Subscribers should review the default sharing model and restrict as needed.
Integration patterns
The LMO typically integrates with the partner''s billing system (Stripe, NetSuite), CRM (often the same org), and support tools. The integration runs via Apex triggers on License updates, custom REST endpoints exposing License data to external systems, or iPaaS (MuleSoft, Workato) orchestrating the data flow. The LMO is the central data hub of the partner business.
Designate and configure your LMO
LMO setup happens once. Get it right at partner-program registration; fixing it later is painful.
- Pick the right org
Permanent, paid org with stable infrastructure. Most often the partner''s primary internal Salesforce org. Never a Developer Edition or trial.
- Register through Partner Console
Salesforce Partner Community, Partner Console, designate the org as the LMO during managed-package registration.
- Install the LMA
Once designated, install the License Management Application managed package into the LMO. License and Subscriber objects appear.
- Configure user permissions
Grant License and Subscriber access to partner ops, customer success, and support roles. Restrict broader access by default.
- Build dashboards and integrations
Surface install-base metrics. Integrate with billing for revenue recognition. Wire support workflows for subscriber engagement.
- Document the org as the LMO
Mark the org clearly so future admins do not accidentally retire it or treat it as a sandbox.
- LMO designation is effectively permanent. Pick a stable, paid, long-lived org; never a Developer Edition or trial.
- Switching LMOs later requires Partner Support intervention and produces a bifurcated install base during the transition.
- Default sharing on License records is permissive. Review and restrict for sensitive customer information.
- The LMO''s storage and API limits apply to License operations. High-volume partners may hit limits if the org also hosts heavy internal CRM data.
Trust & references
Cross-checked against the following references.
- License ManagementSalesforce Help
- Salesforce Partner CommunitySalesforce
Straight from the source - Salesforce's reference material on License Management Organization (LMO).
- LMA Developer GuideSalesforce Developers
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is the License Management Organization?
Q2. What's typically the LMO?
Q3. What gets installed in the LMO?
Discussion
Loading discussion…