Start with a representative Canvas export
Export content through the institution's supported Canvas workflow and keep the output ZIP unchanged. Include a small course or bank with representative item types, media, scoring rules, feedback, outcomes, and metadata. A package made only of simple multiple-choice questions will not reveal the migration risks in the wider bank.
Identify what the package contains
Canvas exports can differ by source area and product generation. Record the Canvas context, export date, package type, detected QTI version, manifest resources, assessment files, item files, and local assets. Do not assume that two ZIP files with the same extension have the same internal contract.
- Count assessments, items, stimuli, and media before import.
- Identify external URLs and assets that the package does not contain.
- Record question-bank or item-bank relationships that matter after migration.
- Flag platform extensions separately from standard QTI structures.
Map common migration risks
| Risk | Review question | Evidence |
|---|---|---|
| Media references | Were images, audio, video, captions, and alternate text packaged and relinked? | Asset inventory and rendered item preview. |
| Scoring | Did correct responses, mappings, tolerances, and partial credit survive? | Declaration comparison and scoring fixtures. |
| Question types | Does the target support the complete source interaction? | Item-type matrix and transformation warning. |
| Metadata | Were outcomes, standards, bank identity, and source information retained? | Field-level migration report. |
| Accessibility | Did alternate resources and presentation intent remain available? | Accessibility field review and delivery preview. |
Use a fidelity review before approval
The importer should create a reviewable draft, not silently publish converted content. Authors need the original source, detected format, conversion warnings, target preview, metadata, and scoring details in one review flow. Items that cannot preserve required behavior should remain blocked until a person chooses a remediation.
Validate the target QTI package
After review, export the approved items and assessments from the target platform. Validate the new manifest, resource graph, XML, identifiers, and assets. Re-import a sample package to a clean target environment and run representative items through delivery. That final round trip proves more than a successful first import.
Plan cutover around content identity
Preserve a mapping between the Canvas source identity and the target item or assessment identity. This supports remediation, audit, and duplicate detection across migration waves. Keep one source export for each approved wave. Record reviewer approval. Put later Canvas edits in a new migration record.
How QFlowLearn handles the boundary
QFlowLearn imports QTI and IMS Common Cartridge packages. It keeps source material and records warnings. A reviewer approves converted content before QTI 3 export. Send a representative Canvas package for a migration review.