Legacy Content Conversion Services

Pricing is fixed and transparent, so you know the cost before you commit. Straight republish and record conversions start at $1,500 per course. Full rebuilds start at $2,999, instructional redesigns at $4,500, and simulation-level enterprise builds at $7,500. Bundles of 10 or more courses bring the per-course cost down further. The exact figure depends on volume, source format, target format, and whether the content is republished or rebuilt. After a short audit you get a fixed quote with no scope creep.

Do not price the whole library at one rate. The cheapest approach is a triage that assigns each course the least expensive path that still preserves the learning: record and republish for the long tail at $1,500 per course, rebuild at $2,999 only where the software is obsolete, and redesign at $4,500 reserved for the handful of courses that actually change behaviour. That mix is what pulls the blended per-course cost down, and per-course rates reduce again at 10, 25 and 50 courses. For enterprise libraries we also produce a retirement list, because the cheapest course to convert is the one you decide not to convert. Send up to 10 files for a free triage and you get a path and a fixed price for each before committing to anything.

Most projects are delivered in 5 to 7 weeks, and republish or record conversions turn around in as little as 3 to 5 weeks. Timeline scales with the size of your library and the complexity of the content. One healthcare client had six compliance courses stuck as PowerPoint files for eight months, and all six were converted in under six weeks.

Yes, and the date is agreed before the project starts rather than discovered halfway through. During planning we identify which courses carry the deadline, put them in batch one, and commit to the delivery date in the written proposal. Large libraries run as fixed-cadence batches so the deadline-critical content is live while the rest of the migration is still in progress. If the deadline is not achievable at the quality level you need, we say so at proposal stage instead of accepting the work and missing it.

The market splits into four groups. Authoring tool vendors such as Articulate, Adobe, iSpring and Lectora sell software, so the conversion work stays with your team. Full-service L&D agencies handle strategy and bespoke builds alongside conversion, which suits flagship programmes but is rarely the cheapest route for a backlog. High-volume production shops quote the lowest headline rate, so check what is excluded, because accessibility remediation, instructional review, LMS validation and revisions are often billed separately. Conversion specialists, including eLearning Solutions Lab, price per course with those items included. The practical differences to compare are source-file ownership, whether WCAG 2.1 AA is included or an add-on, who validates the package in your live LMS, how many revision rounds the price covers, what happens if a course breaks after launch, and whether you get one named contact for the whole engagement. We publish our own market comparisons at top eLearning vendors and top eLearning content providers.

Convert in-house when your source files are current, your team already owns Storyline 360, Rise 360, Captivate or iSpring licences, and you have designer capacity this quarter. Republishing a handful of current-format courses yourself is cheaper than paying anyone. Hire a conversion service when the backlog is large, the source files are missing, the source format is obsolete such as Flash or SWF, accessibility remediation is required, documents and technical manuals are in scope alongside courses, or a compliance deadline is fixed and your team is already committed elsewhere. Most organisations do both: they keep their authoring licences for new builds and outsource the legacy backlog, because the backlog is the work that never reaches the top of an internal queue. We build in the tool your team already maintains and hand over the editable source files, so everything stays editable in-house afterwards.

Every engagement gets one named project manager and one named lead instructional designer from kickoff to final handoff, not a rotating support queue. You receive a written weekly status update showing what shipped, what is in QA and what is blocked. Enquiries get a human reply within three business hours. Two consolidated revision rounds per course are included in the fixed price, and any change outside the agreed scope is quoted and approved before it is built. A course is only counted as delivered once it uploads, launches and reports correctly in your live LMS. After handoff there is a 30-day window in which any defect traced to the conversion, including tracking faults, broken media and accessibility regressions, is fixed at no cost. If the project manager is not resolving something, you escalate to the account lead and get a response within one business day. Beyond the support window you hold the editable source files, so your own team can make changes without paying us at all.

Seven things are your decision on every project: the authoring tool the output is built in, the tracking standard it is packaged to, the brand system applied, the depth of interactivity course by course, the languages and locales, the accessibility standard the QA is run against, and the destination platform. Depth in particular is set per course rather than library-wide, so a policy refresher can be a straight republish while a flagship safety module gets branching scenarios. You can also ask us to build a reusable branded course template from the first batch, so later conversions and any new in-house builds share one visual system. If a vendor cannot tell you which of those seven are configurable in their process, the practical answer is usually none of them.

Yes, and we prove it before the batch ships. Content is packaged for the platform you actually run, whether that is Cornerstone, SAP SuccessFactors, Workday Learning, Docebo, Moodle, Totara, Canvas, Absorb, TalentLMS, Litmos or any other standards-compliant LMS or LRS. Every package is validated in SCORM Cloud first, then a pilot course is uploaded to your live tenant and checked for completion and score write-back, resume and suspend data, grade-book or learning-record mapping, and mobile playback. Only after that pilot is signed off does the rest of the batch ship. If you are mid-migration between platforms we package for the destination system, and where both run in parallel we can ship packages that work in each. See LMS integration for the platform-side work.

There are four paths. Record applies when source files are gone and interactivity is low. Republish applies when source files exist in an older version of a tool that is still supported. Rebuild applies when the software is obsolete but the content and media are still valid. Redesign applies when the content itself needs updating, shortening or restructuring into microlearning. The audit assigns a path to every item in your library, with a fixed price attached, before any work starts.

Yes. Flash to HTML5 is one of the most common conversions we handle. Since Adobe ended Flash support, SWF-based courses go blank in modern browsers, and we rebuild them as responsive HTML5 that works across desktop, tablet and mobile, preserving the original interactions, assessments and instructional design.

That is a common situation, and it is not a dealbreaker. Simple courses can be recorded to MP4 and wrapped in a SCORM player so completion tracking still works. Courses worth keeping interactive are rebuilt from the published output. Either way the path is flagged upfront during the audit, so scope and price are known before work begins. Lost source files do not mean lost content.

Both options are available. A straight conversion republishes existing content in a modern format with minimal changes, which is faster and cheaper. A rebuild or redesign re-engineers the instructional design, improving interactions, accessibility and structure. During planning we recommend the right approach for each piece so you only pay for the depth you need.

Converted courses are delivered in Articulate Storyline 360, Articulate Rise 360, Adobe Captivate, Lectora, iSpring, dominKnow or Elucidat. If your team maintains courses in a specific tool, the output is built in that tool so your people can edit it later, and the editable source files are handed over at delivery.

Output is packaged for any standards-compliant LMS, including Moodle, Cornerstone, Docebo, SAP SuccessFactors, Workday Learning, Absorb, TalentLMS, Litmos and Canvas. Every package is validated in SCORM Cloud before handoff, then confirmed in your live environment after upload.

Yes. We convert SCORM 1.2 to SCORM 2004 and migrate SCORM content to xAPI or cmi5 where you need statement-level data in an LRS rather than a single completion and score. This is especially useful when moving to a new LMS. Every package is tested to confirm it tracks correctly in your target platform.

Yes. A 60-minute legacy course is often better reused as a set of short, single-objective modules with their own tracking. During the redesign path we restructure long courses into microlearning, and job aids can be produced from the same approved source content.

Converted content is validated against WCAG 2.1 AA and Section 508, and can be aligned to ADA and EN 301 549 requirements. Checks cover screen-reader compatibility, keyboard navigation, colour contrast, captions, transcripts and alt text. A documented accessibility report ships with delivery, so you have evidence ready for auditors.

Yes. Large libraries run in phased batches rather than one long project. The audit prioritises by compliance deadline, usage and technical risk, batches are delivered on a fixed cadence so value lands early, and a version-controlled repository keeps naming conventions, module IDs and LMS metadata in sync across the whole migration.

A mutual NDA is signed before any file moves. Transfers are encrypted, files are held in access-controlled storage for the duration of the project, and your content is never reused outside the engagement.

You do. After delivery you receive the finished content, the editable source files and the documentation, so future updates stay entirely in your hands. We do not lock your content to our tools or hold source files for paid edits down the line.