Migration plan for exams, gradebooks, and report cards

1. Define migration scope

List subjects, cohorts, campuses, grading periods, assessments, components, attempts, submissions, marks, grades, comments, moderation, reports, users, integrations, archive, and family or learner views.

State why each record moves, the authoritative source, target owner, retention need, correction route, acceptance test, cutover date, rollback, and what will be redesigned, archived, exported, or retired.

2. Inventory and classify sources

Record each file, platform, report, paper record, export, backup, private copy, owner, purpose, version, update frequency, sharing, dependencies, and consequence of error.

Classify assessment, learner, subject, cohort, component, attempt, mark, grade, calculation, report, moderation, comment, permission, and history as migrate, transform, validate, archive, or retire.

3. Clean meaning and identity

Approve definitions for assessment, mark, grade, scale, weighting, rounding, missing, absent, late, exempt, pending, moderated, approved, published, and corrected before mapping values.

Resolve duplicate learners, transfers, withdrawals, changed classes, subject changes, resits, special consideration, duplicate marks, stale grading periods, and unsupported formulas. Keep rejected values and owners.

4. Map and transform

Create source-to-target mappings for learner, teacher, subject, class, cohort, campus, assessment, component, attempt, submission, mark, grade, report, moderation, and history.

Document transformation, calculation, rounding, missing value, duplicate, version, date, permission, comment, attachment, and report treatment. The U.S. Department of Education data-quality guidance links reliable information with definitions, rules, validation, infrastructure, and learning.

5. Validate in stages

Run sample, rehearsal, parallel, and final reconciliation. Compare counts, identities, marks, grades, calculations, reports, moderation, permissions, correction history, and archive.

Test missing submission, late work, absent learner, amended mark, moderation change, report correction, access failure, integration delay, outage, resit, withdrawal, and transfer. Record expected and observed results.

6. Prepare cutover

Set freeze window, final extract, approval, communication, training, support coverage, calendar, rollback, continuity, backup, restoration, retention, privacy, safeguarding, records, accessibility, and security checks.

The U.S. Department of Education governance checklist covers quality, access, security, lifecycle, sharing, disposal, and monitoring. GOV.UK guidance emphasises accountable handling of school data.

7. Retire safely

After acceptance, restrict or retire old gradebooks and spreadsheets according to the approved records schedule. Review private copies, exports, email, backups, supplier copies, links, and support folders.

Do not destroy necessary history before the approval and retention decision. Keep evidence that the target record, reports, corrections, permissions, and archive were reconciled.

8. Review after migration

At 30, 60, and 90 days, review completeness, calculation differences, moderation, corrections, report confidence, staff effort, support demand, access exceptions, continuity, and outcome.

Record what passed, what remains manual, unresolved risks, owner, due date, evidence, and next test. Expand, repair, consolidate, narrow, or hold through an explicit decision.

Turn the guidance into an accountable decision

Apply this guidance to one bounded part of migration plan for school exam and gradebook software. Define the assessment or reporting decision, authoritative record, accountable owner, permitted users, correction route, evidence, and review date.

Test an ordinary assessment and meaningful exceptions such as a missing submission, late work, absent learner, moderation change, amended result, withdrawn learner, duplicate mark, grading-period change, report correction, access failure, or outage.

Keep supplier capability, school responsibility, professional judgement, local policy, legal advice, and measured outcome separate. If evidence is incomplete, narrow the claim and pilot the smallest safe change.

Review at 30, 60, and 90 days. Check completeness, timeliness, consistency, moderation, corrections, access exceptions, staff effort, support demand, reporting confidence, and the original outcome. Decide whether to expand, repair, consolidate, narrow, or hold.

Before approval, ask a reviewer who was not involved in the design to challenge the strongest assumption. Replace broad language with the exact evidence, population, date, and limitation the school can verify.

Document what was tested and what was not. A successful demonstration with a simple gradebook does not establish readiness for moderation, resits, special consideration, changed grading periods, multiple campuses, or a changed assessment policy.

Keep evidence beside the decision record so a later reviewer can distinguish observed behaviour from an assumption, estimate, or supplier statement. Name the next test where evidence remains incomplete.

Revisit the boundary when the school adds a subject, year group, campus, grading scale, role, integration, reporting period, or policy. A small change can alter permissions, definitions, calculation, timing, retention, or support demand.

Set the next review date and owner. A dependable exams and gradebook operation is maintained through clear definitions, controlled change, professional judgement, and visible accountability rather than a one-time setup.

Make the handoff readable to a teacher, administrator, leader, learner, and reviewer. State what passed, what remains manual, which records are authoritative, who owns unresolved conflicts, and how a correction is communicated without creating an uncontrolled copy.

Keep approved definitions beside calculation rules, moderation notes, training, support routes, and change history. New subjects, scales, integrations, or reporting windows can change the risk even when field names stay the same.