Sign In
Migration

Bring your items. Walk out with QTI 3 and an audit trail.

QFlowLearn refuses to silently rewrite your assessment content. Every imported item is reviewed for fidelity, and the original source XML stays attached for audit and rollback.

Supported imports

Import the formats your item banks already use.

Migration is one of the first questions in an assessment RFP. QFlowLearn imports QTI 1.2, QTI 2.x, QTI 3.0, IMS Common Cartridge, Moodle XML, GIFT, and Aiken, then shows what imported cleanly, what changed, and what needs review.

QTI 1.2

Supported

Legacy IMS QTI items, response processing patterns, classic packaging.

QTI 2.x

Supported

QTI 2.1 / 2.2 packages with manifest, items, tests, and metadata.

QTI 3.0

Supported

Native QTI 3 packages. Fidelity is preserved for editing, review, and export in QFlowLearn.

IMSCC

Supported

Common Cartridge bundles. Item content extracted, metadata mapped where present.

Moodle XML

Supported

Question-bank export. Maps stems, distractors, feedback, and scoring.

GIFT

Supported

Plain-text question format. Ambiguities are flagged for human review before approval.

Aiken

Supported

Simple multiple-choice exchange. Clean conversion path, surfaced explicitly in the report.

Fidelity review

Four review steps before imported content is approved.

  1. Step 1

    Detect and parse

    QFlowLearn detects the package type from manifests, file shapes, and content signatures, then converts items into the QFlowLearn item model.

  2. Step 2

    Separate fidelity tiers

    Each item is reported as semantic preservation, normalized transformation, or review warning. Nothing is silently rewritten.

  3. Step 3

    Reviewer signoff

    Reviewers see item-level status, warnings, notes, source XML, and rendered previews. Nothing becomes approved content until a reviewer accepts it.

  4. Step 4

    Source preservation + QA report

    Original XML stays attached to the item. A QA report exports package readiness, fidelity counts, compatibility rows, and correction state.

QA report

Every migration leaves an exportable trail.

The QA report covers package readiness, fidelity counts, compatibility rows, and correction state. That gives procurement RFP-grade evidence that a migration was reviewed, not just executed.

See sample report (when published) Authoring →

Bring an existing item bank for a fidelity review.

We will run your package through the importer and return the QA report. No sales commitment required.

Request migration review Evidence library