SCORM and xAPI Conversion
Pubrica converts existing courses and learning content into SCORM 1.2, SCORM 2004 or xAPI packages for publishers, training providers and institutions that deliver content through a learning management system. The three specifications differ in what they can track, and content built for one and delivered through another can lose its reporting. Our e-learning engineers package your content to the specification your platform accepts, test it on that platform before handover and deliver the editable source files.
- The right specification: SCORM 1.2, SCORM 2004 or xAPI, selected according to what your platform accepts and what you need to report
- Tested on your platform for launch, bookmarking, completion, scoring and resume, so that reporting problems are found before learners use the course
- Completion and scoring rules made explicit, because “completed” means different things in each specification and platforms interpret it differently
- Accessibility preserved through conversion, including captions, alt text and keyboard operation, which are often lost during conversion
- Source handed over, so that your team can republish the content independently
Packaging to SCORM or xAPIIncluded
Completion and scoring rulesIncluded
Testing on your platformIncluded
Accessibility preservedIncluded
LMS hosting and administrationYour platform
Content → specified → packaged → tested → deployed
- Specification selected on evidence
- Tested on your platform before handover
- Completion rules stated explicitly
- Accessibility preserved through conversion
- Editable source handed over
Deliverables
Four Components of Every SCORM and xAPI Package
Every package covers four components. The specifications your LMS accepts determine how the package is built.
From the specification decisionThe choice depends on what your platform accepts and what you need to report. Defaulting to SCORM 1.2 because it is widely compatible can mean losing reporting you need.
From the testPackage validated against the SCORM specification.Tested in your LMS: the package launches, bookmarks at slide 7, resumes correctly, reports completion at 80% and passes the score back. Specification validity and platform behaviour are tested separately.
From the rulesThe most common support request after launch concerns learners marked incomplete despite finishing the course. The cause is usually an unstated completion rule.
From the post-conversion checkContent that was accessible before packaging but not afterwards is a common failure, and post-conversion checking prevents it.
The samples shown are illustrative and anonymised. Hover over a sample to replay it.
Compliance and Standards
SCORM and xAPI Specifications
The specifications your platform accepts take precedence. The following are the specifications we work to.
Sharable Content Object Reference Model (still the most widely supported)
Packaging, launch, tracking and sequencing. SCORM 1.2 is widely used but limited, and SCORM 2004 adds sequencing and more detailed status reporting.
Experience API (with a learning record store)
Tracks learning activity beyond the LMS, including offline and non-course experiences, and requires a learning record store.
Web Content Accessibility Guidelines (level AA)
Captions, contrast, keyboard operation and reading order, which most institutional and public-sector buyers require in procurement.
Quality management (cert. H3CR9TCU20251212INDQM10N)
Our certified system for briefing, performing, reviewing and releasing project work.
Responsible Use of AI
Our Approach to AI Use and Disclosure
AI tools support specific, checkable tasks. Editorial judgement, final wording and sign-off remain with Pubrica subject specialists.
Why We Do Not Publish an AI Accuracy Figure
Accuracy figures for AI tools are usually reported by the companies that sell them.
Pubrica therefore does not quote a self-generated accuracy figure, because it would carry the same conflict of interest. Instead, we tell you which tool was used on your project, at which stage, and what a specialist changed afterwards.
Our Process
How Our SCORM and xAPI Conversion Process Works
We confirm your platform requirements before choosing a specification, because choosing the specification first is a common cause of lost tracking.
Platform and reporting requirements
We confirm what your LMS accepts, what you need to report and whether any activity must be tracked outside the course.
Structure and completion rules
We agree the module structure, completion and scoring rules, and navigation behaviour before packaging begins.
Packaging
We package the content to the selected specification and carry accessibility features through the conversion.
Testing and handover
We test the package on your platform for launch, resume, completion and score pass-back, then deliver it with the editable source files.
Our Experts
Your SCORM and xAPI Conversion Team
A named team of subject specialists stays with your project from scoping to delivery. Your project coordinator introduces each team member by name before work begins.
Reviews the scientific content for accuracy and confirms that each conclusion is supported by the evidence. Each expert is matched to your field.
Reviews content for accuracy, pedagogy and conformance with the applicable curriculum, assessment or accessibility standard.
Checks the finished work independently against the agreed scope and the applicable checklist. Findings are logged and resolved before delivery.
Manages the timeline, keeps you informed at each stage and coordinates the team so that questions are answered and deadlines are met.
Packages
SCORM and xAPI Conversion Packages
Pricing depends on module count, interaction complexity and how much source material must be rebuilt.
Single course
For content that needs to run in an LMS
Quoted per projectBased on module count and complexity
Delivery By scope
- ✓Specification chosen on platform and reporting needs
- ✓Packaged to SCORM 1.2, 2004 or xAPI
- ✓Completion and scoring rules stated explicitly
- ✓Tested in your platform
- ✓Accessibility checked after conversion
- ✓Editable source handed over
Please tell us which platform you use first, because it determines the specification and approach.
Deliverables Request a quoteCatalogue conversion
For libraries of existing content moving to a new platform
Quoted per projectBased on volume, quoted from a sample
Delivery By arrangement
- ✓Sample conversion to establish effort
- ✓Consistent structure and rules across the catalogue
- ✓Batch packaging and testing
- ✓Accessibility checked across the set
- ✓Conventions documented for future content
Documented conventions prevent the same problems from recurring in later batches.
Deliverables Request a quoteSend one module and your platform details and we will package and test it free of charge. The test also shows whether your LMS behaves as its documentation describes.
SCORM and xAPI FAQs
SCORM and xAPI FAQs
If your question is not listed here, ask an expert. No quote is required.
Use a specification your platform accepts that reports what you need. SCORM 1.2 is almost universally supported but limited in what it reports, and SCORM 2004 adds sequencing and more detailed status reporting.
xAPI is appropriate when you need to track activity outside the course, but it requires a learning record store, which is a platform decision rather than a packaging decision.
Specification validity and platform behaviour are different. Platforms interpret completion, suspend data and score reporting differently, and some behave inconsistently.
Testing on your LMS identifies packages that validate but do not report, before the first cohort completes the course.
The most common problems are unstated completion rules, which cause learners to be marked incomplete despite finishing, and loss of accessibility features such as captions and alt text during conversion.
Both problems can be avoided, and both are identified by platform testing rather than by specification validation.
No. Hosting, administration and learner management remain with your LMS. We package, test and hand over the content.
Platform hosting is outside the scope of this service.
Related Services
Related eLearning and Content Services
Packaging is the final step before content reaches learners.
1CONTENT DEVELOPMENTbefore packaging
Educational content developmentContent developed to defined learning objectives. Learning design and pedagogyCourse structure and assessment strategy.2ACCESSIBILITYthrough conversion
Accessibility complianceWCAG 2.2 conformance across content. Digital production QAQuality checks before publication.3ASSESSMENTwhere a course includes one
Assessment and exam reviewReview of item quality and alignment. Psychometric servicesItem analysis, standard setting and equating.Request a Free Test Conversion of One Module
We will package and test one module free of charge. The test also shows whether your LMS behaves as its documentation describes.