LMS Integration: Types, Methods, Standards, and How to Implement It

LMS integration is the process of connecting a learning management system to other systems that your organization already runs: HR software, CRM, identity providers, content libraries, video conferencing, so that user records, enrollments, and completion data can move between them automatically instead of through manual uploads and spreadsheet exports.

In this guide, we’ll cover which of the 4 connection methods fits your stack, what LTI 1.3, SCORM, xAPI, cmi5, and SCIM each actually do, what a realistic implementation sequence costs and looks like, and how these LMS integrations can tend to break once they’re actually live. If you’re still choosing a platform, our pricing breakdown of affordable LMS systems is the better first read – integration capability is usually a tier decision rather than a product decision.

What Is LMS Integration?

An LMS integration is a configured, maintained connection between your learning management system and another system of record. When it’s working, an employee hired in your HRIS could automatically appear in the LMS with the right courses assigned, log in with their existing company credentials, and their completion record flows back out to wherever compliance reporting lives – without anyone actually touching a spreadsheet.

Basically, an integration is an ongoing agreement between two systems about which one owns which piece of data, how often they reconcile, and what happens when they disagree.

What actually gets exchanged

Integrations can move a narrower set of things than most people expect. In practice, this is what happens:

• User identity – name, email, employee ID, status (active or terminated)
• Organizational context – department, job code, location, manager, or cost center
• Enrollments – course and learning path assignments that are often driven by role or hire date
• Progress and completion – status, score, completion date, and certificate issuance
• Competencies and certifications – including expiry dates that will trigger recertification
• Transactions – orders, entitlements, and refunds, for organizations that are selling training externally

Integration vs. API

An API is the mechanism – it’s the documented interface a system exposes so other software can read and write its data. Whereas an integration is what you build, configure, and maintain on top of that mechanism.

For instance, when a vendor says, “we have an open API,” it is telling you a connection is possible. It’s not telling you a connection exists, who will build it, or who fixes it when it breaks. And that distinction alone is the single most common source of scope surprise during LMS implementations.

Who owns an LMS integration?

LMS integration is owned by three groups:

• L&D or LMS admin defines what needs to happen. This includes who gets assigned what, when, and what reporting the business expects on the other end.
• IT and security own identity, credentials, data handling, and the deprovisioning path – all of them have opinions about SSO, API keys, and where learner data is stored, and those opinions are usually correct.
• The vendor supports the connector they built, within the boundaries of what they built – custom logic is generally yours.

Sometimes, projects go sideways when L&D scopes an integration as a feature request and discovers in the 3rd week that it’s an identity project. So getting IT into the room during scoping is one of the highest-leverage things you can do on a timeline. Where there’s no internal capacity to own the work at all, elearning outsourcing is usually cheaper than adding headcount for it.

Why LMS Integrations Matter

Below covers every benefit of having LMS integrations. Every one of them reduces to the same mechanism: removing a human from a data transfer.

Deprovisioning is a security control, and unified reporting can only change how leadership perceives L&D, given that it’s the only one that can connect training data to a business metric someone outside the function already tracks.

Types of LMS Integration

LMS integrations fall into 8 categories – here’s a table to give you the entire context.

Quick notes on types of LMS integrations:

Identity comes first, always

SSO is the prerequisite integration, as building an HRIS sync before identity is settled means you’ll create user records that are keyed to a field your identity provider doesn’t agree with.

HRIS is where the difficulty actually lives

The payload is genuinely complex here, like manager hierarchies, effective-dated changes, contractors versus employees, people with two job codes, and international entities with different field structures. You need to budget more time for this one.

Bidirectional costs more than it looks

If the CRM and the LMS disagree about whether someone completed a course, one of them has to be authoritative – this decision has to be made before the actual build.

Collaboration and analytics are the ones organizations skip and later regret

Slack or Teams notification – integration here is usually the cheapest adoption lever. Without BI integration, your training data can stay trapped in the LMS’s native reports, which are almost universally the weakest part of any LMS. If reporting depth is your real constraint rather than integration itself, our comparison of the best LMS for training companies goes deeper on where platforms differ.

Video conferencing looks trivial and isn’t

For any attendance write-back, you may confirm during evaluation whether the connector records actual attendance duration or just registration, given that compliance reporting on live sessions will depend entirely on that distinction.

Integration Methods Compared

There are actually 4 ways to connect an LMS to anything else – here’s how you can determine cost, your timeline, and who gets paged when it actually breaks 18 months from now.

Choosing between them

There are 3 questions to help you settle it in most cases:

How many systems? 1 or 2 connections to mainstream platforms: native connectors, full stop. You don’t want to build what you can configure. 4 or more systems that need to talk to each other as well as to the LMS: for instance, iPaaS can earn its licensing cost, given that you’re buying orchestration and error handling.

Real-time, or is nightly fine? Most HR data is fine nightly – for instance, a new hire who appears in the LMS 8 hours after Workday isn’t really the problem. If everything you need is batch-tolerant, flat file may remain a legitimate answer that nobody wants to admit is still in wide use.

Can you own a break in the 14th month? So a custom API build is the cheapest-looking on a one-year view and probably the most expensive on a 3-year view, given that the maintenance cost is invisible at approval time and may land on an engineering team that has since moved on to other work. So if you don’t have a named owner and a runbook, a native connector at $8k a year is actually cheaper than a “free” custom build. Where nobody internally can make that call, an elearning consultant is a cheaper way to get to the decision than a failed build.

LMS Integration Standards, Explained Plainly

Each acronym will solve a different problem, and a normal LMS deployment can use 3 or 4 of them at once.

LTI 1.3 (Learning Tools Interoperability)

LTI is how an external tool runs inside your LMS. For instance, a learner clicks a link in the course, and lands in a third-party tool – a simulation, assessment platform, virtual lab – already logged in, and their score comes back to the LMS gradebook automatically.

LTI 1.1 authenticates with a shared secret, and 1.3 moved to OAuth 2.0 and signed JWTs – which is why security teams increasingly refuse 1.1. These are 3 LTI Advantage services that are worth naming:

• Deep Linking – instructors browse and place specific tool content, rather than linking to a tool’s front door
• Names and Role Provisioning – the tool learns who’s in the course and who’s the instructor
• Assignment and Grade Services – scores flow back into the LMS

Ask vendors for 1.3 specifically. “We support LTI” without a version number usually means 1.1.

SCORM (1.2 and 2004)

SCORM packages a course as a zip file that the LMS can host and track. It’s actually old, browser-bound, and limited to completion status, score, and time spent, but it remains the default format for any off-the-shelf courseware, and roughly everything in the market still ships it that way.

SCORM 1.2 is more widely supported, and SCORM 2004 adds sequencing and better score handling. Most organizations actually use 1.2 given that compatibility beats capability here. And SCORM only tracks what happens inside the LMS, in a browser, or in a launched course. If you’re building rather than buying, our walkthrough on how to create SCORM content covers the packaging decisions that determine whether your courses port cleanly between platforms – and where an existing library predates all of this, legacy content conversion services are usually cheaper than rebuilding it inside the new LMS.

xAPI (Experience API, formerly Tin Can)

xAPI records learning as statements like actor, verb, object, and they are sent from anywhere: mobile app, simulation, job aid, or a piece of equipment on a factory floor. It can capture activity that will never touch the LMS. So the catch is that xAPI statements can go to an LRS (Learning Record Store), not to the LMS.

Given that some LMS platforms will embed an LRS – many don’t, and you really need to buy one separately. So if a vendor says they can “support xAPI”, you can ask whether they can include an LRS, or you can expect you to bring one.

cmi5

cmi5 is actually the bridge between the two. So it uses xAPI for tracking, but it will add the governance SCORM had: launch mechanics, defined completion and pass/fail rules, and a course structure that your LMS can actually administer.

It’s actually the answer to statements like “we want xAPI’s flexibility, but we still need the LMS to manage assignments and report completion.” Adoption here is growing, but not universal – and if you’re publishing from Storyline, our notes on articulate elearning cover which output formats your authoring tool will actually give you.

SCIM (System for Cross-domain Identity Management)

SCIM can automate user account lifecycle between your identity provider and your LMS: this is where you can create, update, or deactivate. SCIM is what makes deprovisioning happen on the termination date rather than just whenever someone runs a report.

Now, if an LMS supports SSO but not SCIM, you’ll have authentication without lifecycle management; this includes accounts getting created but never cleanly retired. And that gap is the direct cause of the orphaned-record problem in the failure modes section below.

SAML 2.0, OAuth 2.0, and OpenID Connect

This is constantly conflated, but genuinely different:

• SAML 2.0 – established enterprise SSO protocol – this proves who a user is to the LMS.
• OAuth 2.0 – authorization, which grants one system permission to act on data in another, and this is what API integrations can use.
• OpenID Connect (OIDC) – an authentication layer on top of OAuth 2.0 – it’s a modern alternative to SAML, which is common with Google and Entra ID.

Which standard for which job

10 Common LMS Integrations and What Data Actually Moves

Below is a list of 10 common LMS integrations giving you what each connection actually moves, in which direction and how – helping you to scope the work properly.

1. Workday

Into LMS – worker records, job profile, org hierarchy, location, hire, and termination dates, effective-dated changes
Out of LMS – completion and certification status that’s written back to the worker profile
Method – native connector or iPaaS; its frequency is nightly

Watch for any effective-dated future changes. Workday knows about a transfer 3 weeks before it happens, so you need to decide whether your LMS should act on the effective date or sync date.

2. SAP SuccessFactors

Into LMS – employee master data, position, cost center, and manager
Out of LMS – completions to the employee record
Method – native connector or middleware; its frequency is nightly

Watch for any overlap with SuccessFactors Learning. So if it’s licensed, you may confirm which system owns the assignment logic before you build anything.

3. Salesforce

Into LMS – contacts, accounts, partner tier, and entitlements
Out of LMS – training status, certification, and expiry dates onto the contact record
Method – native connector or API; its frequency is hourly to near real time

Watch for any classic bidirectional conflict. You may decide which system is authoritative for contact email. This is also the integration that makes external programs measurable – see our guide to customer onboarding training for what’s worth building on top of it.

4. Microsoft Entra ID or Okta

Into LMS – authentication assertions, group membership, role claims, provisioning and deactivation
Out of LMS – nothing
Method – SAML 2.0 or OIDC for login, SCIM for lifecycle; its frequency is real time at login, provisioning on change

Watch for any SSO without SCIM. It’s very common, and it means accounts are created but never retired.

5. Zoom

Out of LMS – session creation, scheduling, registration links
Into LMS – attendance records, join and leave times, and recording URLs
Method – native connector, and its frequency is per event

Watch for whether attendance write-back can capture duration or only registration, as compliance reporting depends on it. If live sessions carry your regulatory obligations, price that requirement against the top compliance elearning providers before you commit to a connector.

6. Microsoft Teams

Out of LMS – meeting creation, assignment notifications, and course launch cards
Into LMS – attendance
Method – native connector, and sometimes LTI for education tenants; its frequency is event-based

Watch for Teams appearing in two categories: video conferencing and collaboration – they’re usually configured separately.

7. Slack

Out of LMS – assignment alerts, due-date nudges, completion celebrations, and course launch links
Into LMS – nothing meaningful
Method – native connector or webhook, and its frequency is event-based

Watch for any notification volume – probably the cheapest adoption lever available and the fastest way to get muted.

8. LinkedIn Learning or Go1

Into LMS – course catalog, metadata, thumbnails, and updated titles
Out of LMS – launches and completions come back from the provider
Method – native connector, that’s often via LTI or content API; its frequency is catalog daily, and completions on event

Watch for any catalog churn. Courses that get retired upstream can leave broken assignments behind. Before you connect a library at all, our roundup of top elearning content providers is worth pricing against the vendor’s own catalog, and our notes on off the shelf elearning cover where library content stops being enough.

9. Stripe or Shopify

Into LMS – order confirmation, payment status, and refunds
Out of LMS – product and pricing data, and entitlement grants and revocations
Method – native connector or API, and its frequency is real-time

Watch for any refund handling. You may confirm whether a refund automatically revokes course access, given that frequently it doesn’t.

10. Power BI, Tableau, or Snowflake

Out of LMS – completion events, enrollment data, xAPI statements, and learner activity
Into LMS – nothing
Method – API, data export, or LRS feed, and its frequency is nightly or streaming

Watch for any granularity. Given that many LMS reporting APIs have exposed summaries rather than event-level data, this may limit what you can analyze later – and event-level data is what makes elearning ROI calculable rather than anecdotal.

LMS Integration Implementation Checklist

Ten steps, in order. The sequencing matters more than the individual items, given that most failed integrations are correctly executed steps done in the wrong order.

1. Scope the systems and name the owner of every field. List every system that will connect, then field by field, name which system is authoritative. Email, employee ID, department, manager, job title, termination date. This is the same discipline that makes instructional design work upstream – decide what you’re actually building before anyone opens a tool.
2. Do identity first. SSO before data sync, every time. Your identity provider determines the unique key everything else will join on.
3. Build the field-level data map. Four columns: source field, target field, transformation rule, and what happens when the value is null. Include contractors, dual job codes, and people with no manager – these are the cases that break the first sync.
4. Choose the method deliberately. Native connector, API build, iPaaS, or flat file. Write down why, including who owns maintenance. That becomes the first line of your runbook.
5. Build in a sandbox with production-shaped data. Not five clean test records. Duplicate names, changed emails, a termination, a rehire. A sandbox that only handles clean data has tested nothing.
6. Run UAT against real scenarios, not features. A new hire on their start date, a transfer, a name change, a termination, a rehire six months later. If UAT is a checklist of “does data appear,” it will pass and production will still fail.
7. Define error handling before go-live. Who receives the failure alert, what the retry policy is, and where the sync log lives.
8. Go live in phases. One department or region first. Watch a full cycle, including a nightly sync and at least one termination, before widening scope.
9. Assign ownership and write the runbook. Name a person, not a team. Cover what it does, which credentials it uses and when they expire, how to check it ran, and who to contact at the vendor.
10. Review quarterly against vendor changes. API versions get deprecated and connectors get updated. A 30-minute quarterly check prevents a multi-day outage.

A realistic timeline

These assume a decision-maker who is available and an IT team with capacity. Both assumptions are optimistic more often than not – the most common cause of overrun on integration projects isn’t technical difficulty, it’s waiting for access, credentials, and approvals.

Security and Compliance

Integration moves employee data between systems, which makes it a security project whether or not anyone called it one. Six things to settle before go-live:

• SSO and MFA enforcement – via SAML 2.0, OAuth 2.0, or OIDC, configured at the identity provider rather than in the LMS.
• Encryption in transit and at rest – TLS on every connection, including SFTP jobs, which are the ones most often left unencrypted.
• Least-privilege API credentials – a service account with only the scopes it needs, plus a documented key rotation schedule.
• Data residency – where learner records physically sit, which matters more the moment you have EU or UK employees.
• GDPR obligations – lawful basis, retention periods, and the right to erasure across both systems, not just the LMS.
• Audit logging – who changed what and when, which is the evidence a compliance auditor will actually ask for.

Common Failure Modes and How to Fix Them

These are the problems that show up 6 to 18 months after go-live, and almost none of them appear on a vendor’s feature list.

Orphaned records and missing completion data are the two that turn into audit findings rather than inconveniences. If regulated training is why you bought the LMS at all, build the sync rules around your compliance training plan rather than the other way round.

12 Questions to Ask an LMS Vendor About Integration

Ask these in writing, during evaluation, before pricing is agreed.

1. Which of our systems have pre-built connectors, and which would be custom?
2. Is each connector included in the plan, or priced separately?
3. Which LTI version do you support – specifically 1.1 or 1.3?
4. Do you support SCIM provisioning and deprovisioning, or SSO only?
5. Do you include an LRS, or do we bring our own for xAPI?
6. Which SCORM versions do you support, and is there an import limit per tier?
7. What is the API rate limit, and what happens when we exceed it?
8. How are breaking API changes communicated, and how much notice do we get?
9. Who supports the connector after go-live – your team or ours?
10. Can we test integrations in a sandbox before production?
11. What tier does each of these integrations require?
12. If we leave, can we export learner records and content in a standards-compliant format?

Question 12 is the one most buyers forget and the one that costs most later. It’s also worth checking any shortlist against a neutral list of top elearning vendors, since most integration roundups are published by platforms selling their own connectors. And if accessibility is in scope, confirm the vendor’s player doesn’t break the work – our guide to accessible elearning covers what survives a platform migration and what doesn’t.