Migrate from Cornerstone to Open edX

Migrate from Cornerstone to Open edX: what the move involves

If you are weighing a Cornerstone renewal against a move to self-hosted Open edX, the course content is the easy part: most of it can usually be reloaded as standard SCORM, AICC or xAPI packages, while completion records, certification history and the talent features around learning need separate work. Cornerstone's own learning platform page says it supports internally built content in these formats, so start by inventorying every package, its authoring tool and its version. Packages that run in the LMS you move to will need a test pass in Open edX before you rely on them, because the courses that give trouble are usually the ones with custom scripts, external calls or unusual completion rules. Expect the effort to concentrate in three places: courses, records and integrations.

Plan for internal platform and learning and development teams to own the work, usually with an implementation partner for hosting, integrations and cutover. Open edX is licensed under the GNU Affero General Public License version 3 and has no licensing fees, but that does not make it free to run. The hosting, operations, upgrades and support are your responsibility or your contractor's, and the maintainers recommend running it in production through a service provider or with Tutor, since bare-metal installation is complex. Ask any partner for a fixed-scope written proposal that lists courses in scope, record migration, identity federation, backups and the upgrade path, and confirm which Open edX release they will deploy, since Open edX supports only its latest named release.

Before you commit, confirm the gaps. Open edX does not replace Cornerstone's talent suite, so succession planning, performance and career features, and the content library subscriptions Cornerstone resells will need other systems or a decision to drop them. Attestations and certification tracking are not something Open edX provides as a compliance product, so you will build those controls and their evidence yourselves and check them with your auditors. Ask your HRIS team how user feeds will be rebuilt, and request a sample transcript export from Cornerstone early, because the quality of those records determines how much manual reconciliation the cutover will require.

Which Cornerstone capabilities map to Open edX, and which need rework

This table maps Cornerstone learning capabilities to their Open edX equivalents and marks each as clean, needs rework or gap. Read the status column first, then the notes, since most rework sits in transcript import, certification rules and identity setup rather than in package delivery. Talent suite features such as performance, succession and recruiting are outside Open edX and need a separate decision.

Cornerstone capability	Open edX equivalent	Status and notes
SCORM, AICC and xAPI package delivery	LMS player with Studio-authored or uploaded packages	Needs rework: original packages can usually be reloaded, but each one must be tested in the Open edX LMS before cutover.
Internally built training content	Open edX Studio authoring tool	Needs rework: courses are rebuilt in Studio rather than exported from Cornerstone, so plan authoring time per course.
Third-party content library integrations (LinkedIn Learning, Coursera, Skillsoft)	LTI tool launches	Gap: confirm with each library vendor whether its LTI integration is available and licensed for a self-hosted Open edX.
Transcripts and completion history	LMS gradebook and learner records, populated by import	Needs rework: export through Cornerstone's Data Exporter API and map records into Open edX. No direct migration path is supplied.
Certifications and recertification rules	Course-level completion and custom logic via Studio and plugins	Gap: recurring certification expiry and renewal rules typically need custom development. Confirm the scope before committing.
Reporting and analytics	Aspects analytics with ClickHouse and Superset dashboards	Needs rework: Aspects collects xAPI-based tracking logs, so compliance reports must be rebuilt and validated against Cornerstone outputs.
Single sign-on and user authentication	Third-party auth via SAML 2.0, Shibboleth, OAuth2 and LTI	Needs rework: connect your identity provider and test provisioning. Older CAS and SSL client certificate support is provisional.
Talent suite (performance, succession, recruiting)	Not covered by Open edX	Gap: these modules have no Open edX equivalent and need a separate system or a decision to retire them.

What moves cleanly from Cornerstone to Open edX and what does not

Standard SCORM, AICC and xAPI packages can be reloaded into Open edX, but learner records cannot follow them automatically. Packages exported from authoring tools are usually self-contained, so the same ZIP files can be uploaded to a new Open edX course and launched there. Completion history, scores, attempt counts and enrollment dates sit in Cornerstone's database, not inside the package, so they must be exported through the Data Exporter API and mapped to Open edX records separately. Before you commit to a cutover date, run a test package through a sandbox course and confirm that completion and score data is reported back as you expect. The format documentation from Cornerstone and the packages themselves do not guarantee that behavior on every content type, so verify it with your own content set.

Some content will not move as files. Where a course exists only as a Cornerstone course object, built from its internal lessons, quizzes, prerequisites or assembled modules, there is no package to reload, and someone must rebuild it in Open edX Studio. Inventory this content early, because it tends to be the largest share of rework and often includes compliance courses with embedded branching or attestation steps. Open edX also does not replace the talent suite. Succession planning, performance and goal management, compensation-linked development plans and HRIS-driven user lifecycle tooling need separate systems or custom integration. Any attestations or certifications Cornerstone holds for your organization, including its security and compliance reports, are Cornerstone's documents and do not transfer. Your own evidence of training completion must come from the self-hosted environment you operate.

Which data and integrations to move, and through which export path

Four workstreams run in parallel: course content, learner records, people data and integrations. Each one has a different owner, a different export path and a different failure mode, so plan them separately. The Data Exporter API is the documented route for transcripts and certification history, but its exact fields and access terms must be confirmed with Cornerstone before you scope the work.

Content packages

SCORM, AICC and xAPI packages from your authoring tools can usually be reloaded into Open edX, which is the cheapest part of the move. Open edX is built around Studio for authoring, so rebuild courses that need interactive structure or assessment logic in Studio rather than forcing legacy packages to behave identically. Inventory every package, its version and whether the original source files still exist, because packages without source are hard to edit later. Confirm which packages Cornerstone hosts for you and which must be re-uploaded from your own repository.

Transcripts and certification history

Completion records, scores, attempts and certification expiry dates are the evidence your compliance team relies on, so they move as a controlled dataset, not as a side export. Pull them through the Cornerstone Data Exporter API, reconcile record counts against the source, and store the raw export unchanged for retention. Open edX does not provide a built-in equivalent of Cornerstone's recertification rules, so decide which expiry logic is rebuilt, reported or kept in an archive. Confirm the exact fields and access scope with Cornerstone before planning.

Users and organization data from HRIS feeds

Learner accounts, manager relationships, job codes and org units determine who sees which course and who must complete it. Map these from your HRIS feed rather than from a one-time export from Cornerstone, so accounts stay current after cutover. Decide early which identifier becomes the stable key, because changing it later breaks enrollment and reporting. Ask Cornerstone which user attributes its export exposes and whether deactivated users keep their history.

Identity via SAML or OAuth2

Single sign-on determines whether learners can reach Open edX without a second password. Open edX third-party authentication supports OAuth2 providers, SAML 2.0 and Shibboleth, so confirm which protocol your identity provider already exposes for Cornerstone. Test attribute mapping for name, email and group claims before cutover, because a wrong claim can silently create duplicate accounts. Plan a fallback for contractors and external partners who may not appear in the corporate directory.

LTI tools and third-party content libraries

Cornerstone connects to external libraries such as LinkedIn Learning, Coursera and Skillsoft. Open edX supports LTI for connecting external tools, but each library vendor has its own licensing and connection terms, so confirm whether your subscription can be used from a self-hosted Open edX before you rebuild the links. Inventory which catalog items learners open most, since those drive the rebuild priority. Budget for the license cost of each library separately from the platform work.

The migration sequence from inventory to decommission

This sequence moves Cornerstone training into a self-hosted Open edX instance in controlled stages, so each course, record set and identity change is verified before Cornerstone is switched off. The end state is a working Open edX estate and an archive of the Cornerstone history your compliance obligations still require.

Inventory courses, packages, certifications and integrations
List every active and retired course, its SCORM, AICC or xAPI package, the completion and certification rules attached to it, and each feed in and out of Cornerstone, including HRIS user sync and third-party library connections. Your learning or compliance owner signs off the list, and your Cornerstone administrator confirms which packages are the authoritative versions. Done when every course has an owner, a package location, a recertification rule and a decision to migrate, retire or rebuild.
Build a pilot course set on Open edX
Stand up a non-production Open edX instance using Tutor or a managed Open edX provider, following the maintainers' recommendation to avoid bare-metal installs for production. Load a small set of representative courses, including at least one SCORM package and one course rebuilt in Studio, and test enrollment, grading, completion and certificate output with pilot learners. Done when a sample of learners can complete each pilot course and the results match what the same course produces in Cornerstone.
Run new enrollments in parallel
Route new enrollments for the pilot courses to Open edX while Cornerstone keeps the historical transcripts, open assignments and in-progress records for everyone. Compare completion events and certificate issuance across both systems each reporting cycle, and log every discrepancy with its root cause. Done when discrepancies are either fixed or documented as accepted, and your compliance owner agrees the evidence trail is complete for the migrated courses.
Cut over records and switch identity
Import transcripts and certification history exported through the Cornerstone Data Exporter API into Open edX, mapping each record to the matching course and learner identifier. Connect Open edX to your identity provider using the supported third-party authentication options, then move learners from Cornerstone sign-in to the new login path. Done when a reconciliation report shows every exported record accounted for, and spot checks of named learners show the same status in both systems.
Decommission Cornerstone with archived records
Once the parallel run and reconciliation close, disable Cornerstone user access, retire its integrations and export a final archive of transcripts, certification history, audit logs and the original content packages. Store the archive under the retention rules your legal and compliance teams set, in storage you control. Done when the archive has been restored or sampled successfully and the decommission is approved in writing by the record owner.

How the migration changes by organization size and starting point

A customer or partner academy usually has a modest catalog, a public or semi-public audience and a training program that is closer to product education than to regulated compliance. That profile fits Open edX well, because Studio is designed for authoring courses and the LMS is designed for learners. The inventory is short enough to review course by course, and many items may be better rebuilt natively in Studio than carried over as legacy packages. The main planning question is who will own the course design work after cutover, since authoring in Studio is a skill your content team will need.

Inventory: List every course, its audience, and whether it is still current. Retire stale content before you move anything.
Studio rebuild: Rebuild interactive or frequently updated courses in Studio, and reload SCORM packages only where the original authoring source is gone.
Learner identity: Confirm how partner and customer accounts sign in, and whether Open edX third-party authentication covers those identity providers.
Certificates and completions: Decide whether academy completions drive commercial decisions, since those records need the same export discipline as internal training.
Operations: Ask whether a managed Open edX provider or a Tutor-based deployment fits your team better than a bare-metal install.

Before committing, confirm the Studio skills available internally and the expected course refresh cycle with your content owner.

What drives cost and duration in a Cornerstone to Open edX move

This table lists the main factors that change the effort of moving training from Cornerstone to self-hosted Open edX, with why each one matters and how to keep it contained. Use it to scope your own move before asking for a written quote, since the right answer depends on your package inventory, integrations and hosting choice.

Driver	Why it moves cost or effort	How to keep it down
Number and age of SCORM, AICC and xAPI packages	Each package must be tested for launch, completion reporting and bookmarking in Open edX, and older SCORM 1.2 or AICC packages often need more checking than newer xAPI content.	Inventory every package with its owner, version and last use, retire courses nobody assigns, and test a sample of each format before committing to a full reload.
Number of courses to rebuild in Studio	Content that was authored as Cornerstone-native modules, or that depends on Cornerstone features, has no direct import path and must be recreated in Open edX Studio by hand.	Separate courses that can stay as packaged content from those that need rebuilding, and rebuild only the ones with active enrollments or regulatory use.
Transcript and certification volume	Completion history, certificate records and recertification dates come out of Cornerstone through its Data Exporter API output and must be mapped to Open edX records, which adds field mapping and validation work.	Agree a retention scope with compliance owners first, migrate only active and in-retention records, and keep the exported source archive read-only for audits.
Identity and HRIS integration complexity	Open edX supports OAuth2 providers, SAML 2.0, Shibboleth and LTI for third-party authentication, so the effort depends on how your directory and HRIS feeds map to Open edX accounts and enrollments.	Confirm which identity provider is the source of truth, map user attributes early, and limit the first release to the feeds that drive enrollment and access.
Hosting choice (Tutor, Kubernetes or managed provider)	Tutor is the official Docker-based distribution and supports Kubernetes, but operating it yourself means you own upgrades, backups, scaling and on-call work. The maintainers recommend a service provider or Tutor for production, since bare-metal installs are complex.	Ask for a written hosting option comparison, decide who runs upgrades and backups before build starts, and price the run cost against your team's existing platform skills.
Open edX release currency	Open edX supports only the latest named release, so an install that falls behind must be upgraded before it can receive fixes, and Verawood is the current named release in the supplied release notes.	Start on the current release, plan a recurring upgrade window into the scope, and confirm with your provider which release they will support during the engagement.

What usually goes wrong in this migration and how to prevent it

Most failed Cornerstone to Open edX moves do not fail on content loading. They fail on records, rules and operations that Cornerstone handled for the buyer and that the new platform leaves to the team. The cards below cover the risks we see most often and a check to run before each one turns into a problem.

Assuming packages carry completion history

SCORM, AICC and xAPI packages carry course content and, at most, session-level tracking. They do not carry the transcript of who completed what and when. Completion history must be exported from Cornerstone through the Data Exporter API output and loaded into the new platform as a separate step. Before cutover, ask a sample of learners to confirm that their completions appear in the target system, not only that the course launches.

Losing certification expiry rules

Recertification depends on rules such as expiry intervals, renewal windows and which course counts toward which certificate. Those rules often live in Cornerstone's configuration, not in the course files, so a reload can keep the courses and drop the logic that flags an employee as overdue. Inventory every certificate, its validity period and its renewal trigger before the build starts, then test one expired and one current record end to end in the new environment.

Underestimating the Studio rebuild

Open edX Studio is the authoring tool for courses, and it does not import Cornerstone course structures. Reloaded SCORM packages keep their content, but the surrounding course outline, assessments, prerequisites and branching must be rebuilt by hand in Studio. Plan this work by course count and complexity, and ask the implementation partner to scope it in writing so the rebuild is not treated as a side task during cutover.

Bare-metal installation complexity

The edx-platform maintainers recommend running Open edX in production through a service provider or with Tutor, and they note that bare-metal installation is complex and receives limited community support. Teams that build from source without a container-based path often lose months to dependency work before any learner logs in. Decide the deployment method first, confirm which parts your own team will operate, and confirm who supports the platform after go-live.

Unplanned upgrades on a single release

Open edX supports only the latest named release and cannot support more than one at a time. A deployment that stays on an older release will eventually fall outside support, which forces an upgrade under deadline pressure. Budget upgrade work as a recurring activity, schedule it against the published release dates, and test each upgrade in a staging copy that holds real course and learner data before it reaches production.

Identity mapping errors

Learners in Cornerstone are matched to HRIS records, and transcripts follow that identity. Open edX supports OAuth2, SAML 2.0, Shibboleth and LTI for third-party authentication, but a mismatch in usernames, email addresses or external IDs will split one employee into two accounts or attach records to the wrong person. Build a mapping table from the HRIS key, test matching on a pilot group, and confirm that duplicate and orphaned accounts are reported before the import runs.

Questions buyers ask before moving from Cornerstone to Open edX

What drives the cost of moving from Cornerstone to Open edX?

The main cost is the work of standing up and operating Open edX, not a license fee, because Open edX has no licensing fees. Cost components include your own infrastructure, a hosting or service provider if you choose one, the labor to rebuild courses in Studio, the work to reload and test SCORM, AICC and xAPI packages, and the effort to move learner records and integrate with your HR system. Costs rise with the number of courses that need rebuilding, the number of integrations, and the compliance evidence you must produce yourself. Ask any quote to split one-time migration work from recurring hosting, support and upgrade costs, and to state which of them are your responsibility.

How long does a migration from Cornerstone to Open edX take?

The timeline depends on scope more than on the platform itself. The largest variables are how many courses you must rebuild in Studio versus reload as packages, how many learner records and certification rules must be mapped, how many identity and HR feeds need reconnecting, and how much testing your compliance owners require before cutover. Open edX deployment choices also affect the schedule, since the maintainers recommend a service provider or Tutor for production over a bare-metal install. Ask for a written scope with milestones and a parallel-run period before accepting any date.

What does the work need from our internal team?

Expect to need platform operations skills, identity and integration skills, and content owners who can check course behavior. Open edX development uses Python 3.12, Node.js, MySQL 8.0, MongoDB 7.x and Memcached, and multi-node deployments need a shared Django cache such as Redis or Memcached, so your infrastructure team must be comfortable with that stack or with a managed distribution. Compliance and training owners must verify certification rules and evidence. Confirm with your engineers which of these skills they hold today and which must be contracted.

Can our own team run this migration without outside help?

A capable team can do it alone, but the question is whether it can carry the full set of operational duties after go-live. Open edX states that only the latest named release is supported, so you must plan a regular upgrade path, and the edx-platform maintainers recommend running production through a service provider or with Tutor. Tutor is the official Docker-based distribution and supports Kubernetes, which can reduce some build work. Decide early whether you will staff upgrades, backups and security patching in-house, or buy them as a retainer. DeployOpen plans, implements, hardens, backs up, upgrades and documents self-hosted platforms in your own environment, and it offers ongoing support and upgrades as retainers under a written scope.

Will our SCORM, AICC and xAPI packages load into Open edX unchanged?

Often they load without rebuilding, but you must test each package in the target environment. Cornerstone supports SCORM, AICC and xAPI for internally built content, and the same standard packages can be reloaded into an open-source LMS. The points to check are the SCORM version each package declares, any calls to external services or content hosts that will not resolve after the move, and completion logic that depends on the old platform. Packages that are fragile or tied to Cornerstone-specific behavior may need rework in Studio. Build a test matrix from your full catalog and sign off each package before cutover.

How do transcripts and completion history move to Open edX?

Completion history and learner records are not carried in the course packages, so they must be exported from Cornerstone and mapped into a separate import process. Plan this as its own workstream: export transcripts, certification dates and user records, confirm which fields your audit trail requires, and decide how historical records will be stored and queried after the move. Open edX Aspects can capture tracking logs as xAPI statements and present them in dashboards, which helps with new activity, but it does not by itself reconstruct historical Cornerstone transcripts. Confirm the import method, the record format and the retention period with your compliance owner before the project starts.

What does Open edX not replace from Cornerstone's talent suite?

Open edX is a learning platform, so it does not replace Cornerstone's broader talent management functions. Confirm in writing whether you need performance and goal management, succession planning, recruiting, onboarding workflows or compensation tools, since those must be covered by another system or by process changes. Cornerstone also holds attestations such as ISO/IEC 27001, SOC 2 Type II and FedRAMP Moderate authorization for its cloud service; in a self-hosted Open edX, those controls and evidence move to your organization or your assessor, and independent auditors and certification bodies issue the reports. Map every Cornerstone module you use against a named replacement before you commit.

What to confirm with Cornerstone and your own team before committing

Start by confirming what the Data Exporter API will actually give you. Ask Cornerstone, in writing, which fields are exposed for transcripts, certification status, due and expiry dates, completion timestamps and user records, and whether your account has the access and OData skills needed to pull them. Then sample an export from a test org and compare it against a known learner's history. Gaps found here shape the migration plan far more than anything in the open-source platform, so treat this as a go or no-go input rather than a formality.

Next, separate the content you own from the content you rent. Internally built packages in SCORM, AICC or xAPI form are usually yours to reload into Open edX, but confirm that the source files still exist and that no embedded player or vendor script ties them to Cornerstone. Third-party libraries such as LinkedIn Learning, Coursera and Skillsoft are different: their licenses typically govern access to the provider's catalog, and access ends with the subscription. Ask each provider what happens to completions and certificates earned through their content, and budget for replacements where the license does not allow you to keep them.

Finally, decide who holds the records obligations after cutover. Your organization keeps its retention duties for training evidence even when the system changes, so confirm with legal, compliance and your auditors which records, retention periods and export formats they require, and whether migrated history must remain readable in its original form. Also confirm which controls Cornerstone's own attestations currently cover for you, such as ISO/IEC 27001, SOC 2 Type II and FedRAMP Moderate, and who will own those controls in your self-hosted environment. Independent auditors and certification bodies, not DeployOpen, decide what evidence is acceptable.

How DeployOpen scopes, runs and supports the Open edX migration

DeployOpen plans, implements, integrates, hardens, backs up and documents self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For a move from Cornerstone to Open edX, we start with a written scope that separates content reloads, course rebuilds, transcript imports and the Cornerstone talent features you will rebuild or drop.

How we scope

Written, fixed-scope agreement listing the SCORM, AICC and xAPI packages to reload and the courses to rebuild in Studio
Inventory of transcript and completion fields from the Data Exporter API output, with the import mapping agreed up front
Explicit list of Cornerstone talent suite functions that Open edX will not cover, so gaps are accepted in writing

How we build

Deploy the edx-platform stack with Tutor in your environment, sized for your learner volumes and identity setup
Connect third-party authentication to your identity provider using the supported OAuth2, SAML 2.0 or LTI options
Test package playback, completion tracking and transcript imports in a staging environment before any cutover

How we hand over

Runbooks covering deployment, backups, Open edX upgrades and content import steps, written for your own operations team
Documentation of the controls and evidence your compliance team will need, prepared for review by independent auditors
Knowledge transfer sessions for administrators and course authors who will run the platform after handover

How we support

Ongoing support, upgrades and continuous testing are available as a retainer after handover
Upgrade planning that follows the Open edX release cycle, since only the latest named release is supported
Confirm during scoping whether support covers Tutor, your identity provider integration and your analytics stack

Migrate from Cornerstone to Open edX