Migrating Education & Learning Data: What Actually Transfers and What Doesn't

Switching education and learning platforms is one of those projects that sounds manageable during the vendor demo and becomes a nightmare during execution. The sales rep shows you how easy it is to import courses. What they don't mention is that your quiz data won't transfer, student progress resets to zero, and your SCORM packages throw errors on the new platform.

This guide maps out exactly what transfers between learning platforms, what doesn't, and how to handle the gaps.

The Data Migration Reality Check

Before you start migrating, understand that educational data falls into three categories:

Transfers Cleanly

• Course content (text, images, documents) — usually exportable as files or via SCORM/xAPI packages
• User accounts (names, emails, roles) — CSV export/import is universal
• Course structure (modules, sections, ordering) — transfers if both platforms support SCORM or Common Cartridge

Transfers With Effort

• Quizzes and assessments — question banks usually export, but scoring rules, randomization settings, and rubrics often need manual recreation
• Certificates and badges — the credentials themselves transfer, but the rules that trigger them need rebuilding
• Enrollment data — who's enrolled in what transfers; enrollment automations don't

Usually Doesn't Transfer

• Student progress and completion status — the most painful loss; students may need to re-complete modules
• Discussion forum history — threads, replies, and conversations are platform-specific
• Detailed analytics — granular engagement data (time on page, video watch %, interaction patterns) lives in the old platform's database
• Grading history — individual assignment grades and feedback comments
• Platform-specific features — gamification points, learning paths with conditional logic, adaptive assessments

This is the reality most teams don't discover until they're mid-migration. If student progress data matters (it usually does for compliance training), plan for this upfront.

For a broader understanding of the space, our LMS and course platforms guide covers the fundamentals.

Step-by-Step Migration Plan

Phase 1: Audit Your Current Platform (Week 1-2)

Inventory everything:

1. Courses: Total count, content types used (video, text, SCORM, interactive), active vs. archived
2. Users: Total count by role (student, instructor, admin), active vs. inactive
3. Progress data: How many students have in-progress courses? How critical is preserving completion records?
4. Integrations: What connects to your LMS? (SSO, payment processing, CRM, HR system, video hosting)
5. Custom content: Any content built using the platform's proprietary editor (not exportable as SCORM)?
6. Certificates: Active certificate programs with compliance implications?

Export everything you can:

Most platforms offer bulk export for:

• User lists (CSV)
• Course content (SCORM packages, HTML files, video downloads)
• Quiz question banks (QTI format if supported, CSV otherwise)
• Completion reports (CSV)
• Certificate records (CSV or PDF)

Don't wait until migration day to export. Start now while you still have full access.

Phase 2: Prepare the New Platform (Week 2-3)

Configuration first, content second:

1. Set up organizational structure (departments, groups, categories)
2. Configure SSO/authentication to match your current setup
3. Set up payment processing if selling courses
4. Configure email notifications and branding
5. Test the SCORM/xAPI player with a sample course

Import order matters:

1. Categories and course structure first
2. User accounts second (so enrollments can reference them)
3. Course content third
4. Enrollments and progress last

Tools like LearnWorlds offer migration assistance for course creators, which can significantly reduce the manual work involved in content transfer.

Phase 3: Content Migration (Week 3-5)

This is where the real work happens. Plan for different approaches based on content type:

SCORM/xAPI Packages:

• Export from old platform → Upload to new platform → Test thoroughly
• Common issues: SCORM version incompatibility (1.2 vs 2004), JavaScript errors in custom packages, video embedding failures
• Always test with a student account, not just admin preview

Native Content (built in the platform's editor):

• This is the hardest to migrate because it's platform-specific
• Options: Manually recreate, use the platform's export-to-HTML feature, or screenshot/record the content as reference for rebuilding
• Budget 30-60 minutes per module for manual recreation

Video Content:

• If hosted externally (YouTube, Vimeo, Wistia): Just update embed codes in the new platform
• If hosted on the platform: Download all videos, re-upload to the new platform or move to external hosting
• External hosting is generally better for migration flexibility

Quizzes and Assessments:

• Export question banks in QTI (Question and Test Interoperability) format if both platforms support it
• If QTI isn't supported: Export as CSV, reformat for the new platform's import template
• Manually recreate: Scoring rules, time limits, attempt limits, randomization settings
• Test every quiz on the new platform — formatting often breaks during import

Phase 4: User Migration (Week 4-5)

Account migration:

1. Export user list with all relevant fields (name, email, role, group/department)
2. Map user roles between platforms (they're rarely identical)
3. Import users — most platforms accept CSV
4. Verify SSO works for migrated accounts

The progress problem:

This is the most contentious part of any LMS migration. Options:

• Accept the reset: Students start fresh on the new platform. Works for elective/professional development courses. Unacceptable for compliance training.
• Manual completion entry: Export completion records from the old platform, manually mark courses as complete on the new platform. Time-consuming but preserves the record.
• Archive and grandfather: Keep the old platform in read-only mode for historical records. New courses and enrollments go to the new platform. Run both for a transition period.
• API-based transfer: If both platforms have APIs, write a script to transfer completion data. This is the cleanest approach but requires development resources.

For compliance training, the "archive and grandfather" approach is safest. You maintain auditable records on the old platform while moving forward on the new one.

Phase 5: Testing (Week 5-6)

Test everything as a student, not just as an admin:

• Can students log in via SSO?
• Does every course load correctly?
• Do SCORM packages track completion properly?
• Do quizzes score correctly?
• Do certificates generate when courses are completed?
• Do enrolled students see the right courses?
• Does the mobile experience work?
• Do video files play without buffering?
• Do conditional learning paths work as expected?

Recruit 3-5 real users for a pilot. Give them a test course that exercises every feature (video, quiz, assignment, certificate) and collect detailed feedback.

Phase 6: Cutover (Week 6-7)

Communication is everything:

1. Announce the switch 2 weeks in advance with the date and what students need to do
2. Provide a "new platform quick start" guide — login, find courses, complete assignments
3. Set up a support channel for migration questions
4. Send a final reminder 24 hours before cutover

Cutover checklist:

• All content verified on new platform
• All active enrollments transferred
• SSO tested and working
• Old platform set to read-only (don't delete yet)
• Redirect old platform URLs if possible
• Student communication sent
• Support team briefed on common questions

Presentation Content: A Special Case

If your learning content includes presentations, tools like Prezi create interactive, non-linear presentations that don't export to standard formats cleanly. Prezi presentations embedded in courses need special handling:

• If continuing with Prezi: Update embed codes in the new platform
• If abandoning Prezi: Export as PDF (loses interactivity) or re-record as video
• If switching presentation tools: Rebuild from scratch using the new tool

This applies to any platform-specific interactive content — the more proprietary the format, the harder the migration.

Platform-Specific Migration Notes

From Teachable/Thinkific to LearnWorlds

Relatively straightforward — all three use similar content structures. Export courses as SCORM where possible. Student data exports to CSV. The main work is recreating sales pages and checkout flows.

From Moodle to Any Commercial Platform

Moodle's data export is excellent (Moodle Backup format), but importing into a commercial LMS is harder. Plan for manual content recreation. The upside: Moodle stores everything, so you won't lose data — you just need to reformat it.

From Google Classroom to an LMS

Google Classroom doesn't export course structure in any standard format. You'll be rebuilding from scratch. Export assignments and materials as Google Drive files, then restructure them on the new platform.

For course platform comparisons, see the best online course platforms or course platforms for coaches.

Common Mistakes and How to Avoid Them

Mistake 1: Underestimating Content Recreation Time

Teams consistently underestimate how long it takes to recreate content that doesn't export cleanly. A course that took 20 hours to build initially takes 5-8 hours to recreate on a new platform. Multiply by your course count.

Mistake 2: Migrating Everything At Once

Don't try to move 200 courses simultaneously. Start with your most active courses (the ones students are currently taking) and migrate in batches of 10-20. Archive inactive courses on the old platform.

Mistake 3: Ignoring the Integration Layer

Your LMS connects to things. Payment processing, email marketing, CRM, HR system, certificate providers. Each integration needs to be rebuilt on the new platform. Budget 2-4 hours per integration.

Mistake 4: Not Having a Rollback Plan

Keep the old platform accessible (even in read-only mode) for at least 90 days after migration. If something critical breaks on the new platform, you need a fallback.

For the broader perspective on education tools, our education and learning tools guide covers essential tools.

Frequently Asked Questions

How long does a full LMS migration take?

For a small course catalog (under 20 courses): 3-4 weeks. For a mid-size catalog (20-100 courses): 6-8 weeks. For a large catalog (100+ courses) with compliance requirements: 3-6 months. The timeline is driven by content volume and how much needs manual recreation.

Will my students lose their progress when I switch platforms?

In most cases, yes — granular progress data (which modules they've completed, quiz scores, time spent) doesn't transfer between platforms. You can preserve completion records by exporting them and manually marking courses complete on the new platform, but in-progress work is typically lost.

Can I migrate SCORM courses between any two LMS platforms?

SCORM is a standard, so in theory yes. In practice, SCORM courses often use platform-specific features or JavaScript that breaks on the new platform. Always test imported SCORM packages thoroughly — especially completion tracking and quiz scoring.

Should I migrate during the academic year or wait for a break?

Always wait for a natural break — semester end, summer break, or a low-activity period. Migrating during active courses disrupts students and increases support burden. The exception is if your current platform is failing critically.

What's the best format for exporting course content?

SCORM 2004 packages for structured courses with quizzes and tracking. HTML/video files for content that doesn't need tracking. CSV for user data, enrollment records, and completion reports. QTI for quiz question banks. Always export in multiple formats as a safety net.

Do I need a developer for LMS migration?

For basic migrations (under 20 courses, simple content): no, a technically competent admin can handle it. For complex migrations (SCORM packages, API-based data transfer, custom integrations): yes, plan for 40-80 hours of development time.

How do I handle compliance training records during migration?

Maintain the old platform in read-only mode as the system of record for historical compliance. Export all completion records with timestamps and store them independently (CSV or database). Configure the new platform for future compliance tracking. Never delete the old records until your compliance retention period expires.