Reading time: 10 minutes
Technical Migration Guide: How to Move from Synthesia to Vidext Without Losing SCORM/xAPI Traceability
Moving from Synthesia to Vidext doesn't mean rebuilding your LMS from scratch: with SCORM/xAPI traceability available on all plans, the process comes down to five auditable steps.
If your team has been producing training videos in Synthesia but your L&D manager can't see who completed last month's safety module — or what score they got — you're probably on a plan without SCORM access.
This isn't a technical failure. It's a product decision: SCORM package export in Synthesia is exclusively available on the Enterprise plan. Starter and Creator export MP4 only.
If you've decided to migrate to Vidext and need to maintain (or activate for the first time) traceability in your LMS, this guide covers exactly that. We walk through which learning data you need to preserve, what needs to be reconfigured, and how to run the migration in five steps without interrupting your active courses.
When you upload an MP4 video to your LMS, the platform can register that someone opened the file. That's it. It doesn't know if they completed it, how long they were active, or whether they passed the attached assessment.
SCORM changes that. It's the protocol that turns a training video into a communicating module: the content talks to the LMS and reports exactly what happened during the session.
There are two main versions actively in use:
Then there's xAPI (also known as Tin Can API), the most modern standard. Unlike SCORM, it doesn't require the content to be inside the LMS to record data. It can capture which video sections were watched, how many times a segment was replayed, or whether someone completed the module from a mobile device outside the corporate network.
Why does this matter in practice? Because without this data you can't demonstrate compliance in a workplace safety audit (ISO 45001, ISO 9001, NOM-035 in Mexico), you can't measure the real impact of training, and you can't justify renewing your L&D budget with leadership.
Training consumption data isn't just an operational metric. It's the documentation that backs compliance decisions. If you need more context on using traceability as legal protection in safety audits, the article on traceable video for safety audits covers this in detail.
Synthesia offers three access tiers: Starter, Creator, and Enterprise. SCORM package export is available only on Enterprise.¹
Starter and Creator plans allow video export in MP4 format. For informational content, internal communications, or institutional videos where traceability isn't a requirement, that works fine. But if training needs to be tracked in an LMS, you need a SCORM package — and that only exists on Enterprise.
The most common scenario we see: teams that have spent months uploading MP4 files to their LMS in a context where the platform can only record the file opening. Without a SCORM package, completion data, scores, and session time aren't captured anywhere in the system.
If that's your situation and you're migrating specifically to activate traceability, the transition is straightforward.
Before running the migration, it's worth understanding how Vidext handles traceability so you can anticipate any configuration decisions.
From the editor, any video can be exported directly as a SCORM 1.2 or SCORM 2004 package — no intermediate steps or additional setup required. The generated package includes the video, the completion marker, and if configured, an assessment with a passing score threshold.
If your LMS supports xAPI (integrated or external LRS), it can be configured to send granular events: percentage of video watched, interactions with interactive elements, and intermediate assessment results.
The key point for migration is that you don't need to make any changes to your LMS. The SCORM packages generated are compatible with Moodle, SAP SuccessFactors, Cornerstone, Docebo, TalentLMS, and any platform implementing the ADL standard. Your LMS doesn't need to know — or care — which tool generated the content.
With that in mind, let's get to the operational part.
Before moving anything, you need to know exactly what you're working with. The goal is to document the real state of each module, because not all of them migrate the same way.
For each active video in Synthesia, record:
The result is an inventory with two categories: modules that were already SCORM packages, and modules that were MP4. The first group requires a direct swap. The second is an opportunity to activate traceability for the first time.
If your catalog has more than 30 modules, start with the highest-impact ones: onboarding, mandatory safety training, and any module with an assessment tied to certification.
With the inventory ready, the next step is to recreate the modules in Vidext while keeping the same architecture your LMS already has set up.
This matters: if you change course names or the folder structure in the LMS during migration, learning paths assigned to active users can break. The recommendation is to keep the same course identifiers and replace the content inside each one.
In Vidext, you can import the script, PDF, or PowerPoint of each existing module directly. If the content only exists as video (without a source script), you'll need to extract the text or reconstruct it.
Use this moment to review which modules are still current. Updating a module in Vidext has virtually zero cost compared to re-recording a training video — which makes migration a natural opportunity to clean up outdated content without additional budget.
A pattern we cover in the article on how to digitize training without just uploading documents to the LMS: teams that use migration as a trigger to convert procedural PDFs that have sat as static files in the LMS for years, turning them into modules with real traceability for the first time.
Once a module is ready in Vidext, the export process is straightforward:
On version choice: use SCORM 1.2 unless you have a specific reason for 2004. SCORM 1.2 has broader compatibility, especially with older versions of corporate LMS platforms. SCORM 2004 only adds real value if you need adaptive sequencing or multiple weighted learning objectives. If you don't have that specific requirement, 1.2 is the safer choice.
If your LMS supports xAPI, activate event sending before uploading the content. The configuration depends on the specific LMS, but on most modern platforms it only requires adding the LRS endpoint in the module settings.
This is the step most often skipped — and where most problems occur. Before reassigning modules to the team, run a test with a test user.
The standard validation flow:
If you want more rigorous validation before uploading to the corporate LMS, SCORM Cloud (from Rustici Software, the authors of the standard) lets you test SCORM packages in a controlled, neutral environment. It's the industry-standard tool for catching compatibility issues before they affect real users.
For xAPI validation, most LRS platforms have debug panels where you can see received events in real time during testing.
The technical migration can be flawless and still cause confusion if users suddenly find a different module in the LMS with no warning.
The recommendation is to communicate the change before executing it, focusing on the impact for the user — not the tool change. A message like "starting Monday, safety modules will display in a new format with built-in assessment and completion certificate" creates far less friction than "we've changed our video creation platform."
For larger L&D teams, it makes sense to hold a short session (30 minutes max) with managers before launch so they can answer their teams' questions without escalating to IT.
The Vidext CSM assigned to your account is part of this process on all contracts. A core part of their work is helping plan the roll-out so the migration doesn't affect completion metrics during the transition.
If you're also modernizing your LMS at the same time, the article on 7 steps to migrate from a traditional LMS to a dynamic ecosystem covers organizational change management in more detail.
| Feature | Synthesia Starter/Creator | Synthesia Enterprise | Vidext (all plans) |
|---|---|---|---|
| SCORM 1.2 export | Not included | Yes | Yes |
| SCORM 2004 export | Not included | Yes | Yes |
| xAPI integration | Not available | Not documented | Yes |
| Dedicated CSM | No | Yes | Yes |
| Languages with Spanish regional variants | No | Partial | 120+ languages, incl. Catalan, Basque, Galician, and LATAM neutral Spanish |
| Configurable completion criteria | N/A | Yes | Yes |
The data in this table reflects features published on Synthesia's pricing page and Vidext's product documentation (April 2026).¹ Plans may be updated: verify the current state of your contract before making migration decisions.
If you've been producing training on a Synthesia Starter or Creator plan, your completion records are likely incomplete or don't exist. The content was fine; the problem was in the delivery format.
Moving to Vidext resolves that from the first module. It doesn't require changing your LMS, it doesn't require infrastructure reconfiguration, and it doesn't require IT involvement beyond validating the first package in a test environment.
The five-step process described here (audit, rebuild, export, validate, roll-out) is the same one applied with training teams at industrial, retail, and logistics companies with catalogs ranging from 10 to 150 modules. The variable that most affects total migration time isn't the size of the catalog — it's the state of the documentation for existing modules.
If you want to assess whether migration makes sense for your specific situation, request a demo and the Customer Success team can run the analysis with you before you commit to anything.
It depends on the state of the original scripts. If you have the source texts or reference PDFs, a 20-module catalog can be produced in Vidext in two weeks. If the content only exists as video and scripts need to be rebuilt, the timeline extends. The technical part (SCORM export and LMS upload) tends to be the fastest: minutes per module once the content is ready.
No. A SCORM package is a standard independent of the tool that generated it. Your LMS doesn't need to know whether the content came from Vidext, Synthesia, or any other platform. The only thing that changes is the .zip file you upload — not the platform configuration or existing assignments.
In most cases, SCORM 1.2 is the right choice. It has broader compatibility with corporate LMS platforms, especially older versions of Moodle, Cornerstone, or SAP SuccessFactors. SCORM 2004 only adds real value if you need adaptive learning paths with multiple weighted objectives. If you don't have that specific requirement, 1.2 is safer.
Gradual migration is better in most cases. Start with the highest-impact modules (mandatory safety training, onboarding), validate that traceability works correctly, then scale to the rest of the catalog. Migrating everything at once increases the risk of a problem going unnoticed until it affects a large number of users.
The viewing data Synthesia holds is proprietary to their platform and isn't exportable in SCORM or xAPI-compatible format. What you can preserve are the completion records your LMS has already captured for modules that had SCORM active. When you replace the module in the LMS with the Vidext version, historical records for users who already completed the old module are retained — as long as you use the same course identifier in the LMS.
Yes. The generated SCORM packages follow the ADL standard, compatible with any LMS that implements SCORM 1.2 or 2004. This includes Moodle, SAP SuccessFactors, Cornerstone, Docebo, TalentLMS, Saba, Absorb LMS, and any other platform that supports the standard. If your LMS has a specific implementation quirk, the Customer Success team can help you verify compatibility before migration.
@ 2026 Vidext Inc.
Newsletter
Discover all news and updates from Vidext
@ 2026 Vidext Inc.
