1. What record classes exist in each platform?
Enrollments, completions, scores, certifications, course versions, attempts, attachments. List them per system before assuming the new platform can hold them all.
2. Who owns each dataset?
A migration without named owners stalls at every decision. Assign an owner per record class per source.
3. How far back does history need to go?
Compliance obligations often require records for many years. Decide what moves into the new platform and what is preserved in a governed layer.
4. How will identities be reconciled?
Different usernames, employee IDs and email addresses across platforms create duplicate learners. Plan the match rules and the review process.
5. What does the vendor export actually contain?
Request a full export early. Wizards often omit archived courses, inactive users and attachments.
6. How will you validate?
Agree counts and sample checks per record class, with sign-off before cut-over.
7. What happens to the old platform?
Contract end dates drive everything. Capture history before access is lost.
8. Which downstream systems depend on learning data?
HRIS, BI dashboards, compliance tools. Each needs a plan for the transition.
9. What are the data protection obligations?
Processing agreements, residency and retention rules should be settled before data moves.
10. Who runs the layer afterwards?
Document lineage and access, and train administrators so the organization is not dependent on any one person or vendor.
Ready to see your learning data in one place?
Tell us which systems you run and we will show how the platform connects, normalizes and preserves their records.