The complete guide to running an LMS inside Salesforce

Every buyer who searches for a Salesforce LMS starts with the same question: doesn't Salesforce already have this? The answer comes in two parts. No, Salesforce does not sell a general-purpose learning management system, and its former learning product was announced for retirement in 2026. And yes, there is a sanctioned path: an LMS installed inside your org from the AppExchange, running on your data, your security model, and your automation.

The stakes justify getting this right. Providing learning opportunities is the number one retention strategy companies report, per the LinkedIn Workplace Learning Report 2025. If the people you most need to train already spend their day in Salesforce, where that training lives is an architecture decision, not a procurement detail.

I build a learning platform that runs entirely inside Salesforce, and this guide is the map of everything that decision touches. It draws on seven detailed guides published in this series, each linked where it goes deeper. It covers what "native" really means, what Salesforce itself offers and doesn't, the architecture that changes when learning data lives in your org, and the seven decisions every deployment has to make.

What "Salesforce-native LMS" actually means

A Salesforce-native LMS is a learning management system installed inside your Salesforce org as a managed package. Courses, learning paths, enrolments, quiz results, and completions exist as custom objects and records in your own database. No learner data sits on the vendor's servers, because the vendor doesn't have servers in the data path. The application runs where your CRM runs.

That definition changes four things in practice:

• Your security model governs learning data. Profiles, permission sets, and sharing rules apply to a course record the same way they apply to an Opportunity.
• Your automation reaches learning data. A Flow can enrol a new hire or react to a completion, because both are record changes in the same org.
• Your reporting includes learning data. Completions sit one report builder away from pipeline, cases, and activity.
• Your admins run it. The skills that run your org run your LMS.

One nuance matters before you compare vendors: the word "native" in marketing and the native specification on an AppExchange listing are not the same thing. Any vendor can write "native for Salesforce" on its website, and some of those products are external platforms with a connector or an embedded widget. The AppExchange itself distinguishes app types, and every listing goes through Salesforce's security review. Salesforce's official AppExchange Basics guide explains how listings work and what to check before installing. A fully native app is built and runs entirely on the Salesforce Platform. Check the listing's app-type specification, then ask where the data lives.

Full disclosure: I build Daniwoo, a 100% native LMS, so I hold a position here. The definitions and tests in this guide hold regardless of which vendor you evaluate. The decisive test is one question: where does a completion live? If the answer is a record in your org, you're looking at a native architecture. If it's a row in the vendor's cloud that a sync job copies over, you're looking at an integration. The native versus integrated comparison unpacks everything that follows from that answer.

What Salesforce itself offers (and doesn't)

Salesforce does not sell a general-purpose LMS in 2026, and its learning product line has moved twice in four years. Here is the factual record, because most of it has almost no third-party coverage.

Trailhead is Salesforce's free learning platform, and it does one job well: teaching Salesforce skills. Modules, trails, and superbadges cover the platform, its clouds, and its ecosystem roles. What Trailhead does not do is host your content. You cannot upload your compliance course, your product training, or your partner certification to it. It teaches Salesforce; it does not teach your business.

myTrailhead was Salesforce's answer for custom content: a paid product that let companies publish their own training in the Trailhead format. In February 2022, Salesforce renamed it: the product became Sales Enablement, and its content sites became Enablement Sites, as documented in the Spring '22 release note. The repositioning was explicit. Learning content became one ingredient in a seller-productivity product rather than a standalone learning platform.

On March 17, 2026, Salesforce announced the retirement of Sales Enablement, in help article 002475099. The terms are orderly: existing subscriptions are honored until their service end date, and Salesforce recommends exporting your content starting 90 days before your term ends. If your team built training on myTrailhead or Enablement Sites, with terms ending on a rolling basis through 2026 and 2027, the export window is now a planning item, not a someday task. The migration guide covers the export mechanics and the learner data the export leaves behind.

Sales Programs is the current product, listed at $100 per user per month as of 2026 on Salesforce's enablement page. It is positioned as enablement inside Sales Cloud: programs, milestones, and outcome tracking for sellers. It is a credible product for that job. It is not an LMS: there is no SCORM runtime and no general-purpose certification management. Partner-facing enablement is a separate product: Salesforce's Partner Cloud ships Partner Tracks, in a tier listed at $50 per member per month as of 2026. That is in-app guidance and ramp resources for partners, not a learning management system either.

None of this is a criticism of Salesforce. That matches how Salesforce has long handled specialized apps: the platform from Salesforce, the apps from the AppExchange. That is the conclusion that matters for a buyer. Salesforce does not sell a general-purpose LMS in 2026; the AppExchange is the sanctioned path.

The architecture: what changes when learning data lives in your org

The practical difference between a native LMS and an external one is not the feature list. It is four properties that no connector can replicate, because each one depends on the data physically living in your org.

Security and sharing are inherited, not rebuilt. An external LMS needs its own user directory, which means provisioning, deprovisioning, and a second identity surface to audit. A native LMS has no second directory: learners are your Salesforce users, and access to learning records follows the sharing model you already maintain. When someone leaves, deactivating their user closes everything. The native versus integrated guide walks through what the duplicate-directory tax costs in practice.

Automation is Flow, on training records. The events worth automating on are CRM events: a hire activating, a rep changing roles, a deal entering a regulated stage. An external rule engine cannot see them; a Flow fires on them natively, in the same transaction context. Assignment, escalation, and recertification become Flows your admins can edit, not vendor tickets. The training automation guide is a pattern library for exactly this.

Reporting is your report builder, not an export. Completions stored as records join pipeline, cases, and activity in the same dashboards, with no BI stitching. You measure training where you measure revenue, which is what makes ramp and readiness reportable to executives. The onboarding guide shows this side by side with pipeline.

External audiences ride Experience Cloud. Partners, resellers, and customers can learn on a branded site in the same org, without entering your internal directory. Their completions land next to their Accounts. The partner training portal guide covers the build and the licensing.

There is a constraint to own honestly: living in your org means sharing its governor limits and its record locks. A native LMS is a write-heavy tenant of your database, and its tracking architecture must respect that. The tracking at scale guide explains the locking model and the design that survives it.

The seven decisions of a native LMS deployment

Every deployment in this series reduces to seven decisions. Each one has a full guide behind it; here is the map.

1. Native or integrated

Decide the architecture before the feature comparison, because the architecture decides what the features can do. An integrated LMS is an external platform plus a connector: two user directories, sync jobs, and data that arrives late and flattened. A native LMS keeps courses and completions as records in your org, where security, Flow, and reporting already operate. The test that cuts through every demo is a single question: where does a completion live? The native versus integrated LMS comparison runs the full side-by-side, including the recurring costs that never make the pricing page.

2. Content standards

Make SCORM 1.2 and 2004 support non-negotiable in any player you evaluate, with cmi5 as the forward path. Salesforce has no SCORM runtime in any cloud, so the player application is what makes standards-based content work at all. The launch data says which standards matter: 92% of SCORM Cloud registrations in 2025 were SCORM, per Rustici's SCORM Cloud data (2025). The SCORM in Salesforce guide covers the architecture and four production failures worth knowing before your first upload.

3. Assignment automation

Automate assignment on CRM events, not on LMS-side lists. When training data lives as records, assignment is a Flow: a new hire triggers an enrolment, a completion updates a certification field, a schedule re-runs compliance annually. Three Flow patterns cover most programs, and because they are Flows in your own org, your admins can open and extend them. That is the capability external platforms lack by design, since their rule engines cannot see your org's events. The training automation guide documents the patterns and the production lesson that keeps them alive at scale.

4. Program design

Design ramp as a sequenced path with a measurable finish line, not a folder of courses. The benchmarks set the bar: median SDR ramp is 3.0 months, per The Bridge Group's 2025 SDR report, and median AE ramp is 6.2 months, per The Bridge Group's 2026 AE report. Beating them is structural: auto-assigned paths, lessons attached to real records, ramp progress on the same executive dashboards as revenue. The onboarding guide covers the week-by-week design and the graduation gate.

5. Extended enterprise

Plan for learners who don't work for you, because for many companies they matter most: 75% of world trade flows through indirect channels, per Forrester, 2017, citing the WTO. Partners won't adopt your internal LMS and shouldn't enter your directory. The native answer is an Experience Cloud academy in the org your channel already runs on, with certification status readable next to partner Accounts as a sales-authorization gate. The partner training portal guide covers the architecture, the licensing, and a real deployment of that gate.

6. Delivery model

Deliver training at the point of need, not only on the calendar. Reps spend about 60% of their time on non-selling tasks, per Salesforce's State of Sales research, so a separate training destination competes with everything else and loses. Contextual learning puts the lesson inside the record where the question arises, sized to the gap it fills. The memory science supports spaced, in-context delivery, and one viral forgetting statistic it doesn't support gets debunked along the way. The contextual learning guide covers the science and the two architectures.

7. Tracking architecture

Press on the tracking design before you buy, because it decides whether the LMS survives your busiest hour. Learning is a write-heavy workload: thousands of learners writing at once, and those writes funnel into a handful of shared parent records. Salesforce resolves that contention with record locks on a documented 10-second timeout, per Salesforce's knowledge article. Naive write-per-interaction designs fail exactly there. The durable pattern keeps granular progress lightweight and writes the reportable cascade once, at completion. The tracking at scale guide covers the locking model and the design rules, including a production incident from our own postmortem at roughly fifty thousand concurrent learners.

Evaluating vendors: the questions that separate them

Four questions, asked in writing, separate architectures faster than any demo. Every vendor's deck says "seamless Salesforce integration"; the answers below cannot be vague and still be answers.

1. Where does a completion live? Ask for the object name in your org. A native product names a custom object; an integrated one describes a sync.
2. What happens at 1,000 concurrent completions? Ask how tracking writes are batched and how parent-record contention is handled. Silence here is a load-test you'll run in production.
3. Which automations ship, and as what? Assignment, escalation, and recertification should arrive as Flows or Flow-triggerable records, visible in Setup.
4. Who can extend them? The right answer is your admin, in Flow Builder, without a vendor ticket.

Weight the questions by who you are. A sales enablement leader cares most about questions 3 and 4, because programs change faster than vendor roadmaps. A support operations leader training agents at scale should press hardest on question 2. A partner or channel leader should add a fifth question: how do external learners sign in, and which license do they use?

Get the answers on paper. The LMS RFP kit packages these questions, and the follow-ups each answer should trigger, into a ready-to-send document.

Cost shape: what you pay for in each architecture

Compare cost structures before comparing prices, because the two architectures don't buy the same list of things. This section names no vendor prices, on purpose; the only public figure in this guide is Salesforce's own, in the section above.

A native LMS has a short bill: the LMS subscription itself, running on Salesforce licenses you already own for internal users. There is no middleware line, no connector subscription, and no integration project, because there is no integration. Upgrades arrive as managed package versions, tested by the vendor against each Salesforce release.

An integrated LMS carries the platform subscription plus the connector, and often middleware to move data between the two directories. It also carries the recurring costs that rarely make the first-year spreadsheet: integration retests after each release on either side, admin time reconciling two user lists, and BI work to rejoin data that started out separated. The native versus integrated comparison lays these out in a full table.

One line item applies to both architectures: external learners. Partners and customers accessing training through a portal consume Experience Cloud licenses, which Salesforce sells in member-based and login-based models. Which model fits depends on how often each partner logs in, and the partner training portal guide covers how to choose.

FAQ

What is a Salesforce native LMS?

A Salesforce-native LMS is a learning management system installed inside your Salesforce org as a managed package. Courses, enrolments, and completions are records in your own database, governed by your security model, automated by your Flows, and reported in your own dashboards. No learner data sits on the vendor's infrastructure.

Does Salesforce have a built-in LMS?

No. Salesforce sells no general-purpose LMS in 2026. Trailhead teaches Salesforce skills and cannot host your content. The former myTrailhead/Sales Enablement product was announced for retirement in 2026, and its successor, Sales Programs, is a seller-enablement product rather than an LMS. The AppExchange is the sanctioned path for a general-purpose LMS.

Can Salesforce be used as an LMS?

Yes, by installing an LMS from the AppExchange as a managed package. The platform provides the database, security, automation, and reporting; the package provides players, paths, quizzes, and certifications. Building one from scratch is technically possible but rarely wise, given what content standards and tracking alone require.

Is Trailhead an LMS?

No. Trailhead is Salesforce's free platform for learning Salesforce itself: the products, the ecosystem, the certifications. It does not accept your content, so it cannot train your workforce on your products, processes, or compliance material. Treat it as a complement to your LMS, not a substitute.

What replaced myTrailhead and Sales Enablement?

Sales Programs is the current product. The lineage: myTrailhead was renamed to Sales Enablement, with Enablement Sites, in February 2022. On March 17, 2026, Salesforce announced the retirement of Sales Enablement in help article 002475099. Existing subscriptions are honored until their service end date, and Salesforce recommends exporting content starting 90 days before term end.

What is Salesforce Sales Programs, and is it an LMS?

Sales Programs is Salesforce's seller-enablement product inside Sales Cloud, listed at $100 per user per month as of 2026. It runs programs, milestones, and outcome tracking for sellers. It is not an LMS: it has no SCORM runtime and no general certification management, and it targets internal sellers. For partners, Salesforce offers Partner Tracks in its separate Partner Cloud product, which is enablement guidance, not an LMS.

How much does a Salesforce LMS cost?

Expect a per-user LMS subscription layered on Salesforce licenses you already own, with no middleware or connector line if the product is native. External learners add Experience Cloud licenses, sold per member or per login. Integrated architectures add connector, middleware, and ongoing integration upkeep to that base.

What does "100% native" mean on the AppExchange?

It means the application is built and runs entirely on the Salesforce Platform, so your data never leaves your org to be processed elsewhere. Check the listing's app-type specification rather than the vendor's marketing, since every AppExchange listing passes Salesforce's security review, then ask where the learner data lives.

Is there an LMS on the AppExchange?

Yes, several, spanning fully native apps and external platforms with connectors. Search the AppExchange for "LMS", then read each listing's specifications and reviews. The architectural question that sorts them fastest is the one this guide keeps returning to: where does a completion live?

How do I evaluate a Salesforce LMS?

Ask four questions in writing: where a completion lives, what happens at 1,000 concurrent completions, which automations ship as Flows, and who can extend them. Then weight them by your role and scale. The LMS RFP kit turns the full list into a sendable document.

Conclusion

The one thing to remember: Salesforce doesn't sell a general-purpose LMS, and running one natively inside your org is the architecture that inherits everything your org already does well. Security, automation, reporting, and external portals stop being integration projects and become properties of where the data lives. The seven decisions above are the whole deployment: architecture, standards, automation, program design, external audiences, delivery, and tracking. Each has a full guide in this series, and together they are the case that native is worth insisting on.

The category is moving: with Sales Enablement retiring, teams that built on it are choosing their next home this year. If that's you, or if you're choosing a first LMS for a Salesforce-centric team, book a demo and bring the four vendor questions. You can also see it running at enterprise scale first.

Keep reading, the full series:

• Native vs integrated LMS: the comparison
• SCORM in Salesforce: what actually works
• Automate training assignments with Salesforce Flows
• Onboarding reps faster with in-CRM training
• Partner training portals on Experience Cloud
• Contextual learning in Salesforce
• LMS tracking in Salesforce: designing for scale
• The LMS RFP kit

About the author. Brice Mbouani is the founder of Daniwoo and a Salesforce engineer. He designed and built the Salesforce-native learning platform this series is drawn from, which runs in production orgs at organizations including KPMG. The architecture and evaluation frameworks in this guide come from those deployments.