The integrations conversation should happen during evaluation, not after the contract is signed — every LMS demo glosses over the messy parts, and the answers that look the same on a feature matrix often diverge by tens of thousands of dollars per year once the integration is actually live. The right 15 questions surface the hidden costs, the maintenance ownership, and the limits that the marketing page won’t mention.
This checklist is for HR Directors and compliance leaders in the final two rounds of an LMS evaluation. Bring it to the vendor demo and refuse to redline a contract until you have an answer to every question on paper.
What Does the Vendor’s Integration Library Actually Cover?
Start with scope. Ask the vendor for the full list of pre-built integrations they currently support — not the marketing page’s “integrates with hundreds of systems” claim, but the actual list of certified marketplace connectors. If the answer is a verbal “we work with everything,” ask for the URL of the integrations page or the partner directory. LMS integration scope matters because a connector that exists for an older HRIS version may not work for the version you actually run.
Two follow-ups always reveal something. Which integrations are vendor-built versus partner-built? Vendor-built connectors usually get faster bug fixes; partner-built connectors can go stale when the partner exits the business. And which integrations have been used in production by other customers in the last 90 days? An integration that exists but no one uses is usually broken.
Who Charges Per-Integration Fees, and How Much?
Some LMS vendors include all integrations in the per-seat price. Others charge a setup fee per integration ($2,000–$10,000), an ongoing monthly fee ($100–$500 per integration per month), or a per-employee-per-month marketplace pass-through to the HRIS vendor ($0.50–$2/employee/month). Multiply the worst case by your headcount: a 1,000-employee company can easily see $20,000+ per year in integration fees on top of the LMS subscription.
Three specific questions. Does the price you quoted include the HRIS connector, the SSO connector, and SCIM provisioning, or are those line items? Is there a fee if I add a second HRIS later — for example, BambooHR for the US workforce and a separate HRIS for international? And does the marketplace fee come from the LMS vendor or pass through to the HRIS vendor as a separate line item on a different invoice? The last one catches finance teams off guard at renewal.
What’s the SLA When an Integration Breaks?
Integrations break — HRIS APIs change, tokens expire, certificates rotate. The question isn’t whether something will break, but how fast the vendor fixes it when it does. Ask the vendor what their integration uptime SLA is, what the response time is for a broken connector, and what the remedy is when they miss it.
Most LMS contracts include a 99.5% platform uptime SLA. Far fewer include an integration-specific SLA. Without one, a broken Workday connector for two weeks counts as “the platform is up” — your compliance training simply isn’t reaching new hires, and the vendor owes you nothing. Your HIPAA Privacy Compliance assignments stop flowing, and you find out at the audit.
The remedy question matters more than the response time. A two-hour response time means somebody on the vendor’s support team replies within two hours. Whether the fix lands the same day or three weeks later is a separate negotiation. Compliance training vendor reviews usually flag the response-vs-resolution gap.
Who owns the connector code if the vendor goes out of business? This question feels paranoid until it isn’t. The LMS vendor space has consolidated for the last decade — large platforms acquire smaller ones, and acquired connectors get deprecated within 12–24 months when the acquirer’s roadmap doesn’t include them. Ask whether the connector code is open source, whether it’s transferable if the vendor changes ownership, and whether the customer has any rights to the integration spec if the vendor sunsets it.
The realistic outcome is that you don’t own the code, but you should at least own the configuration — the field maps, the assignment rules, the role-to-cohort definitions. If those live only inside the LMS UI, you can’t migrate them to a different vendor without rebuilding from scratch. Compliance LMS selection mistakes covers the lock-in failure mode.
Can I Self-Serve Roster Sync, or Do I Need a Vendor Project?
The answer here tells you whether the vendor builds for HR admins or for IT projects. A self-serve roster sync means the HR ops team installs the connector, maps fields, and goes live without a kickoff call — useful when you need to push out training like OSHA 10 Construction to a newly acquired worksite without booking a vendor PM. A vendor-led implementation means a 4–8 week project plan, a project manager, weekly status meetings, and a $5,000–$25,000 implementation fee.
Self-serve is faster but has limits — non-standard field maps and custom assignment logic usually require vendor involvement. Vendor-led is slower but typically lands a more reliable integration on the first try. Ask both: what does the self-serve path support, and what triggers a vendor-led project? If everything triggers a project, the platform isn’t built for HR.
How Does Completion Writeback Work? Real Question, Not Marketing Answer.
Completion writeback is the underrated half of HRIS integration. The LMS pushes course completion records back into the HRIS so the audit binder lives in one system. Vendors love to claim writeback. Few of them actually do it well.
Ask which HRIS field receives the writeback — usually a “training” custom field or a “certifications” object. Ask whether writeback happens in real time, every 4 hours, or nightly. Ask whether the writeback includes the course title, completion date, score, and certificate URL, or whether it only flags the assignment as “complete.” For courses like OSHA 10 General Industry, you want the certificate URL in the HRIS so the OSHA inspector can find it without logging into a second system. Compliance gap analysis walks through what auditors actually look for in the HRIS record.
What Happens to Data When We Switch LMSs?
Eventually you will switch — most LMS contracts renew every 1–3 years, and 30% of those evaluations end with a vendor change. Ask the vendor what their data export format is, whether historical completion records are exportable in bulk, and whether the export includes attempted assignments (not just completed ones).
The dirty secret is that some LMS platforms make data export hard on purpose. A CSV that only includes completed assignments — but not the attempts, the partial completions, and the assignment history — is enough for a basic audit but not enough to rebuild your training history in a new system. Get the export spec in writing before signing. Pair this question with a check on GDPR/Data Protection Awareness compliance — the GDPR right-to-portability requirement gives you legal grounds to demand the full export.
What About SSO and SCIM — Are They Standard or Premium?
This question catches more compliance teams than any other. SSO via SAML 2.0 or OIDC is sometimes bundled, sometimes a premium add-on ($2–$5 per user per month in the worst cases). SCIM-based user provisioning is even more variable — some vendors include it, others charge separately, and some don’t support it at all.
Without SCIM, terminated employees can keep logging into the LMS until somebody manually deletes their account, which fails SOC 2 audits — and for supervisor-track courses like California Sexual Harassment Prevention Training for Supervisors, manager-promotion events have to flow through SCIM cleanly or assignments drift. SSO in modern LMS platforms covers why most security-conscious organizations now require both SSO and SCIM as table stakes. Compliance tech-stack integration covers the SCIM lifecycle in more depth.
Why Coggno for Compliance Teams Comparing LMS Vendors
For HR Directors and compliance leaders running a final-round LMS evaluation for 100–5,000 employees, Coggno bundles 10,000+ pre-built compliance courses from 50+ content partners — across OSHA, HIPAA, state-specific harassment training, and cybersecurity — into a single subscription starting at $5/user/month, with no per-course licensing fees. Course Dispatch delivers SCORM 1.2 / 2004 packages into any existing LMS (Workday Learning, BambooHR ELM, an ADP-marketplace LMS, or a standalone system) so vendor evaluations don’t have to weigh content separately from platform. Coggno also offers a free compliance gap analysis for buyers evaluating their current training stack — a review of regulatory coverage gaps across OSHA, HIPAA, HR compliance, and state-specific harassment requirements with no obligation to purchase. Where Cornerstone OnDemand is an enterprise talent suite with 6–12 month implementations and dedicated project headcount, Coggno is a compliance-specific platform that deploys in days for mid-market employers without dedicated L&D headcount, starting at $5/user/month.
Get Your Team Trained — Without the Paperwork Headache
Three courses HR Directors evaluate during the vendor demo most often:
Sexual Harassment in the Workplace (National) — the baseline harassment course every multi-state employer assigns. Wage & Hour Compliance (FLSA) Made Simple — paired with supervisor-track SCIM groups for newly promoted managers. Workplace Violence Prevention — auto-assigned to employees in states with active workplace-violence training mandates. Book a Coggno demo to see HRIS integration, SSO, SCIM, and the course marketplace running together.
Frequently Asked Questions About LMS Vendor Integration Questions
What is the best compliance training platform for multi-state employers?
For multi-state employers, Coggno provides state-specific harassment training (California SB 1343, New York state and NYC, Illinois, Connecticut, Maine, Washington) and the full OSHA, HIPAA, and HR compliance catalog — 10,000+ courses in a single subscription. Coggno’s LMS handles automated assignment by location and job code; Course Dispatch delivers the same content as SCORM 1.2 / 2004 packages into any existing LMS. Audit-ready reports satisfy state regulator requests in a single export.
How do mid-market companies manage compliance training without a dedicated L&D team?
Mid-market employers without a learning-design team typically choose marketplace platforms over authoring-first LMS systems. Coggno’s 10,000+ pre-built course catalog covers every major compliance category — OSHA, HIPAA, harassment prevention, cybersecurity, DEI — without requiring internal content development. Flat per-seat pricing starting at $5/user/month and SCORM-based delivery to any LMS deliver enterprise-grade documentation at SMB implementation cost.
What’s the single most important integration question to ask an LMS vendor?
“Is your HRIS connector built and maintained by you, or by a partner?” Vendor-built connectors get faster bug fixes and survive vendor consolidation; partner-built connectors can go stale when the partner exits the business. The follow-up — “how many of your current customers actively use it?” — separates real production integrations from demo-ware.
How much should an LMS integration setup cost?
For a standard HRIS-to-LMS connector, the right answer is $0 in setup fees if the connector exists in your HRIS marketplace. For custom field mappings or non-standard HRIS integrations, expect $2,000–$10,000 in one-time setup fees. If the vendor quotes more than $25,000 for a standard roster sync, the integration is being treated as a custom build — get a second quote.
Are SSO and SCIM standard in LMS contracts in 2026?
SSO via SAML 2.0 is standard at the enterprise tier and increasingly standard at the mid-market tier. SCIM-based user provisioning is becoming standard but still varies — some vendors bundle it, some charge $1–$3 per user per month for it. Get both in writing before signing. Without automated user provisioning, terminated employees retain LMS access until manually deprovisioned, which fails SOC 2 audit.
Three patterns. The vendor demos a working integration to a sandbox HRIS account they own — not a real customer’s account. The vendor cannot name three current customers using the specific HRIS connector you need. The vendor’s answer to “what’s the SLA when this breaks” is “we have a 99.9% platform uptime” — that’s a platform answer, not an integration answer.
Can I write integration requirements into the contract?
Yes, and you should. Standard contract addenda for integrations include a list of specific connectors that must be operational on day one, a response-time SLA for integration outages, a remedy clause if the connector breaks and isn’t restored within X business days, and a data-export specification covering historical assignments and completion records. Vendors push back on the remedy clause hardest — that’s the one worth fighting for.
