SCORM, xAPI, AICC & Tin Can Explained: Which LMS Standard Should You Use?

If you're evaluating a Learning Management System (LMS), migrating to a new platform, or working with third-party course content, you've likely come across terms like SCORM, xAPI, AICC, and Tin Can API. These are eLearning standards that determine whether your online courses can communicate learner progress, completion status, quiz scores, and certifications with your LMS.

Understanding these standards isn't just a technical exercise—it can save weeks of migration effort and prevent costly compatibility issues. A course that launches successfully doesn't always track learner progress correctly, issue certificates, or preserve historical compliance records after migration.

Imagine this: procurement has approved a new LMS, the implementation timeline is set, and someone asks, "Will all our existing courses still work?" You open your content library and discover hundreds of ZIP files—some published in Articulate Storyline years ago, others supplied by compliance vendors using legacy AICC standards. Nobody is certain which packages support bookmarking, which record detailed learner progress, or which contain mandatory compliance training with audit trails that simply cannot be lost.

This guide is written for LMS administrators, IT teams, training managers, and compliance leaders who need clear, practical answers—not technical jargon. You'll learn what each eLearning standard does, how SCORM, xAPI, AICC, and Tin Can differ, when each should be used, and how to avoid the most common content migration mistakes.

What are AICC, SCORM, xAPI?

E-learning standards solve one problem: letting a course built in one tool run and report inside a different vendor's system.

Standard	Released	What it Does	Where You'll Meet it
AICC	Early 1990s	Content reports to the LMS over HTTP form posts (HACP)	Legacy aviation, defence, insurance libraries
SCORM 1.2	October 2001	ZIP package + JavaScript runtime; single completion status	Most authoring tools' default export; most widely supported
SCORM 2004	2004–2009, four editions	Adds sequencing, split completion/success statuses, more storage	Complex branching or multi-module courses
xAPI (Tin Can)	2013	Sends activity statements to a Learning Record Store	Mobile, offline, simulations, in-product tutorials

Four names, three actual things: Tin Can and xAPI are the same specification. "Tin Can" was the project name used while Rustici Software built it under an ADL contract; on publication it became the Experience API. A vendor listing both as separate capabilities tells you something about the vendor.

What is SCORM and How Does It Work?

SCORM Sharable Content Object Reference Model — is less a technology than a packaging agreement. A SCORM course is a ZIP containing HTML, JavaScript and media, plus an imsmanifest.xml at the root; that SCORM manifest file tells the LMS what's inside and what launches first. Once running, the course reads and writes a fixed set of fields through a JavaScript object the LMS exposes score, completion, bookmark, time spent.

That fixed set explains both SCORM's reach and its ceiling: it works nearly everywhere, and cannot tell you what a learner did after closing the tab.

SCORM 1.2 vs SCORM 2004: the Differences That Break Things

Most teams treat this as a version-number question. In a migration, it's a data question.

1. Progress storage. SCORM 1.2 caps suspend_data at 4,096 characters; SCORM 2004 (3rd edition onward) raises it to 64,000. A branching scenario stores its state visited slides, variables, answers in that field. Exceed the 1.2 ceiling and the write fails silently: the learner resumes at slide one, and nothing in the admin console flags it.

2. Status reporting. SCORM 1.2 uses one field, cmi.core.lesson_status, for both "did they finish" and "did they pass." SCORM 2004 splits these into completion_status and success_status. If your certificates fire on "passed" but the content only writes "completed," the certificate never issues a common post-migration ticket, and almost always a mapping problem, not a platform fault.

3. Sequencing. SCORM 2004 added a Sequencing and Navigation model built on IMS Simple Sequencing, powerful, hard to implement, and unevenly supported. A package that enforces prerequisites on one system may let learners skip ahead on another.

SCORM 1.2 remains the most compatible option and a sensible default for straightforward completion tracking. ADL closed SCORM 2004 to revision in 2011, which is why the version list has been stable for a decade.

What This Means When Evaluating an LMS

If your organization relies on SCORM content, your LMS should do more than simply launch courses. It should preserve bookmarking, completion tracking, quiz scores, certificates, and reporting without requiring course modifications. Platforms like CXcherry are designed to support existing SCORM libraries so organizations can migrate with minimal disruption.

What is AICC? Why Do Some Organizations Still Use It?

AICC: the Aviation Industry Computer-Based Training Committee, formed in 1988 by Boeing, Airbus and McDonnell Douglas produced the first widely adopted e-learning interoperability standard. Its HTTP-based protocol let content report to an LMS on a different server, which SCORM handles poorly.

The committee dissolved in December 2014 and handed its archive to ADL. The standard is unmaintained but still in production: regulated industries bought large libraries in the 2000s and many were never repackaged. The practical question isn't whether AICC is modern; it's whether your target platform can launch it while you plan a replacement. AICC standard LMS support is a bridge, not a destination.

Many organizations in insurance, healthcare, aviation, manufacturing, and financial services still maintain AICC libraries created years ago. During LMS selection, verify whether the platform can continue running these legacy courses while you modernize your content library. CXcherry supports both SCORM and AICC packages, helping organizations migrate gradually rather than rebuilding everything at once. 

What is xAPI (Tin Can)  and How It Is Different From SCORM?

Where SCORM asks "did they finish the course," xAPI asks "what did they do." It sends xAPI statements in an actor–verb–object structure: Priya · completed · AML Module 3  to a Learning Record Store. Because statements travel over standard web requests, the activity needn't happen inside an LMS course window: mobile apps, simulations, in-product walkthroughs and offline learning tracking can all report to the same LRS. xAPI became an IEEE standard in October 2023 as IEEE 9274.1.1-2023, moving it from a vendor-run project to governed infrastructure.

The trade-off: xAPI defines the pipe, not the packaging. Two vendors can describe the same event with different verbs, and your reports quietly diverge. cmi5, an xAPI profile now in IEEE standardisation, adds back the launch and completion rules SCORM always had.

xAPI vs SCORM isn't a replacement decision. Most organisations run both: SCORM for structured, auditable courseware, xAPI for everything outside it.

Which LMS Standard You Should Choose: LMS Standard Comparison

Although SCORM, xAPI, and AICC all help learning content communicate with an LMS, they were designed for different purposes. SCORM remains the industry standard for structured online courses, xAPI extends tracking beyond the LMS to capture richer learning experiences, while AICC primarily exists to support legacy course libraries. Understanding these differences helps organizations choose the right LMS and plan future content migrations. 

Feature	SCORM	xAPI	AICC
Tracks completion	✓	✓	✓
Offline learning	✗	✓	✗
Support Mobile App	Limited	Excellent	Poor
Standard status	Active	Active	Legacy
Learning Record Store	No	Yes	No
Best for	LMS courses	Modern learning	Legacy content
Widely Supported by LMS Vendors	Excellent	Growing	Limited
Recommended for New Implementations	Yes	Yes	No

The Four-Layer Portability Check

Migrations fail in predictable places. Test each layer separately; "yes, we support SCORM" only answers the first.

1. Package. Will the system accept the file as-is? Upload a real course, not a vendor sample.

2. Launch. Does it open cleanly? Watch for mixed-content and cross-domain errors, which surface when content that once sat on the LMS server moves elsewhere.

3. Runtime. Does it write and read back? Complete one course, exit another halfway, resume. Truncation and status-mapping errors surface here.

4. Record. Does historic completion data come across? The layer teams discover too late.

During LMS implementations, CXcherry follows the same structured validation process:

• Upload existing SCORM and AICC packages

• Verify launch behavior

• Test bookmarking and learner progress

• Validate completion and certification

• Confirm reporting before production rollout

What Actually Happens to Your Tracking Data?

SCORM runtime data lives in the LMS, not in the course package. Moving the ZIP moves the content. It moves no completion records at all.

Historic completions must be exported from the old system and imported into the new one a separate migration, usually requiring field mapping between two schemas. Enrolment history, certificate issue and expiry dates sit in that second job. In a compliance-heavy environment that's the whole risk: a 900-person regional insurer switching platforms mid-year doesn't just need its AML course to launch, it needs three years of dated completion evidence intact for the audit.

Pre-Migration Checklist

Task	Why It Matters
Inventory all learning packages	Identify supported standards
Verify SCORM version	Avoid runtime issues
Identify AICC courses	Plan legacy migration
Export learner records	Preserve compliance history
Test bookmarking	Prevent learner frustration
Validate certificates	Ensure regulatory compliance
Test reporting	Confirm accurate tracking

Choosing an LMS for SCORM, xAPI, and AICC

To conclude ,selecting an LMS isn't just about checking whether it supports SCORM or xAPI. The right platform should protect your existing learning investment while giving you the flexibility to scale future training initiatives. Whether you're migrating thousands of compliance courses or launching a new employee or customer education program, evaluating an LMS against the right criteria can save significant time, cost, and implementation risk. 

• Standards support

• Migration process

• Reporting

• Compliance

• Certification

• APIs

• Scalability

• Future readiness

CXcherry was built to help organizations migrate existing learning content while supporting modern compliance, customer education, and employee training use cases.

Frequently Asked Questions

Q1: Which platforms and LMS integrations work best with SCORM Cloud for seamless delivery?

Ans: SCORM Cloud is a hosting and dispatch service, so it pairs best with platforms that can consume an externally hosted package and still record results centrally via dispatch links, LTI, or an API connection. If you push the same course to multiple client systems, that removes real duplication; if your content lives in one platform, hosting it natively is simpler and removes a dependency. Platforms with open APIs, including CXcherry, support either arrangement.

Q2: Can SCORM courses work in any LMS?

Ans: Yes. Most modern LMS platforms support SCORM 1.2. Support for SCORM 2004, AICC, and xAPI varies by vendor. Always test bookmarking, completion status and reporting before migrating.

Q3: Can a cloud-based LMS support SCORM, AICC, and xAPI content standards?

Ans: Yes, and most enterprise-grade cloud platforms do, but they're doing different jobs. SCORM and AICC are packaging and runtime standards for courseware you upload; xAPI is a data specification for activity anywhere, and using it meaningfully requires a Learning Record Store. Ask vendors which of the three they support natively, which through integration, and what reporting looks like for each a distinction that matters most for compliance training, where the audit trail has to be defensible.

Q4: Does xAPI replace SCORM?

Ans: Not necessarily. Most organizations use both standards together. SCORM is ideal for structured online courses that require completion tracking and certification, while xAPI captures learning activities beyond traditional LMS courses. They complement each other rather than compete.

Q5: Can I convert AICC courses to SCORM?

Ans: Yes, provided you have access to the original source files. If only the published AICC package is available, conversion may require rebuilding or republishing the course using an authoring tool such as Articulate Storyline or iSpring. Organizations with large legacy libraries often migrate courses gradually while maintaining temporary AICC support.

Q6: What should I check before migrating courses to a new LMS?

Ans: Before migrating, inventory every course, identify whether it uses SCORM 1.2, SCORM 2004, AICC, or xAPI, verify bookmarking and completion tracking, export learner history and certificates, and test several representative courses in the new LMS before completing the migration.

Q7: Which LMS is best for SCORM and compliance training?

Ans: The best LMS should support SCORM 1.2, SCORM 2004, and legacy AICC packages while providing reliable reporting, certification management, audit trails, learner progress tracking, and straightforward migration tools. Organizations with compliance requirements should also evaluate reporting depth, data retention, and ease of validating existing course libraries. Some of the best LMS providers that supports all these formats to track and drive compliance training are TalentLMS, Docebo, LearnUpon, CXcherry. 

Q8: Can CXcherry run SCORM, AICC, and modern learning content?

Ans: CXcherry supports SCORM and AICC packages, video, audio and podcasts, documents and presentations, in-platform HTML pages, assessments, assignments and instructor-led sessions. There's no built-in authoring tool; courses made in Articulate Storyline, iSpring or similar are uploaded as published packages and structured inside the platform. Most teams run a mix: SCORM for regulated material, native formats for employee training and customer education, where update speed matters more than portability.