Evaluate a new LMS with one representative course restore that exposes broken activities, missing access and the real effort of conversion.
On a migration demo, a vendor imports an orientation course in five minutes. The files appear in the destination, and everyone can open the welcome page. A teacher later imports an assessment-heavy course. The quiz opens but omits its feedback, a video points back to the old site and a grader cannot find the assignment submissions. The demo and the day-to-day work turned out to be different exercises.
If you are choosing an LMS that makes a migration checklist easier to fulfill, ask vendors to perform a trial restore of one representative course under conditions your team can repeat. Measure what staff must repair and which learner actions still work. Those observations tell you more about migration effort than a list of supported file extensions.
Choose a course that represents actual work
Look for a course with three behaviors that matter to your instructors. It could include a quiz with feedback for each response, a submission graded against a rubric and a video stored outside the platform. Add one activity that relies on an external tool or a manual approval. Ask a course owner to name a behavior they would notice immediately if it disappeared. An instructor might care about when feedback becomes visible, while an administrator might care whether a completion date remains attributable to the right person.
Use a copy with fictional learner data in a test tenant. Keep a reference of what learners see and what instructors do beyond opening the course. Capture the source settings and the version of the course package. Instructure’s Canvas content migration reference documents a selective import mode that lets a team list package contents and choose what to import. Include the selected items and destination context in your notes so another person can repeat the trial.
Test the important paths as the correct role
Ask someone other than the person who imported the package to run the checks. They should use the instructor and learner roles separately. A video that works for administrators may require additional permission for a learner. A grader could see the rubric but lack a place to submit scores. Test the end of each action, including where the score or completion status appears after saving. Keep the screenshot or a short observation tied to the activity and role.
| Trial activity | Evidence to capture | Decision if it fails |
|---|---|---|
| Quiz with targeted feedback | Sample learner sees the expected feedback at the intended time | Estimate quiz rebuild and test a second quiz |
| Rubric-graded assignment | Instructor submits scores and learner sees the correct feedback | Ask who remaps the rubric and how long it takes |
| Externally hosted video | Learner opens the video from the destination tenant | Fix media permissions or plan to rehost |
| External learning activity | Launch works from the destination with the expected instructor and learner roles | Schedule a connector retest with the tool owner |
| Course completion | Sample learner completes the required steps and a staff member finds the result | Verify the completion rule before accepting the restored course |
The same action can produce a partial success. For example, a quiz may keep questions and scores but lose per-answer hints. Ask whether those hints are central to the course. A compliance test might never expose them, whereas a practice course depends on them. Record the course owner’s decision beside the finding so the migration estimate reflects what the team will actually repair.
Measure instructor effort separately
Track elapsed import time, administrator clicks and instructor repair time separately. A ten-minute automated import can still create two hours of review work. Measure time spent deciding where a field belongs as well as time spent editing it. If the trial required a vendor to intervene, ask how often that intervention is expected and whether your agreement covers it. Request another run led by your team when the intervention was central to getting the package to open.
Sort the catalog by the activities that failed. If 12 of 60 courses have quiz feedback configured this way, estimate the repair effort for those 12 and sample a second one before committing. Avoid multiplying the trial’s total by 60. Common features may convert cleanly and tricky ones can cluster in a handful of departments. Also look for shared assets, such as a video used by six courses. Fixing its access once could remove six apparent repair tasks.
Keep the decision attached to the evidence
Give each supplier the same starting material and acceptance checks. Let them document a manual workaround, with its steps, owner and estimated time. A workaround may be acceptable for a low-use course and a problem for a course that staff refresh weekly. When a vendor reports a future feature, record the date and ask for a current alternative so the migration decision can be made today.
Before signing off, import the representative course one more time into a clean destination. Ask the instructor to follow the previous reviewer’s notes without help. Check whether they can identify the destination course, run the learner actions, and explain how to close any remaining issue. That final repeat tells you whether the vendor’s strengths can be turned into a routine that your staff can sustain once the first migration week is over.
Emerging Stacks can help evaluate import paths and integrations through full-stack development for education teams. Contact Emerging Stacks with the course features that must survive your first restore.
Ready to work with us?
Get in Touch


