Data & Reporting

Before migrating student records: agree what to convert, retain and reconcile

By Altioras Global6 min read
Cover illustration for Before migrating student records: agree what to convert, retain and reconcile

Suppose a rehearsal produces the right number of student records, but the Registrar cannot reproduce a former student’s transcript. Student Accounts can see a balance, yet cannot explain which charges and credits make it up. Before approving the load, agree which records staff need in the new system and how they will find the rest.

Decide what each office will need after cutover

Start with the institution’s actual scope. If the target is Ellucian Student powered by Banner, ask the implementation lead to confirm the source environment, target deployment, record sets and load method in the agreed scope. A Banner upgrade or hosting move may call for different work. Confirm the actual conversion and archive options with the team responsible for delivering them.

Have the Registrar start with the tasks staff must carry out: register an active student, issue a transcript, review transfer credit or answer a question from a returning student. Ask Student Accounts and Financial Aid which balances and supporting detail they must be able to explain. For each task, record what must be in the target on day one and what can stay in an approved archive or other system.

Tennessee State University’s February 2026 board materials identify completeness of historical records as a migration risk. Solano Community College’s Student modernization project lists validated results from three migration iterations among its success criteria. Those are examples of what institutions planned to check. Set the checks and number of rehearsals for your own project.

References: [1], [3], [2]

Give retained history a retrieval test

Have the records owner and records management staff check the institution’s retention schedule, any holds and who may see the record. A decision to leave something out of the load does not approve disposal. Document the official copy, retrieval location, responsible office and how staff will handle a request after legacy access ends.

The University of Denver’s schedule illustrates why the record type matters: its official transcript and a transcript order form are listed separately. Use your own schedule. For an archive test, ask an authorized Registrar employee to find a sample record by the identifiers staff actually use and complete the request. Check whether someone outside the permitted role can see the record.

Record setWhat staff checkReviewer
Active registrationsCompare student, term, section and status for the approved population. Follow a changed registration through the next load.Registrar
Academic historyRetrieve a sample transcript and compare credits, grades, transfer credit and award details with the official record.Registrar
Open student balancesCompare balances by account and term. Trace selected charges, credits and payments to the approved source detail.Student Accounts and Finance
History kept outside StudentRetrieve an older record using the approved role. Check that staff can complete the request after the legacy system is retired.Records owner and IT
Rejected or excluded recordsMatch each item to an approved exclusion or a correction with an owner and retest date.Conversion lead and records owner
Decisions and checks to agree before a rehearsal

References: [4]

Compare the same population at the same cutoff

Record the extract time, inclusion rules and term ranges with the source report. Have the conversion lead record what loaded, what was deliberately left out and what was rejected. Reconcile these groups at the agreed record level and account for approved merges or splits. Compare by term, status or record type so an extra row in one group does not hide a missing one in another.

For balances, have Student Accounts agree how the source and target reports treat timing, credits and opening balances. Use approved calculations and trace differences to individual accounts. Record how changes after the extract will be captured, including late adds, drops or payments. Before cutover, repeat the check for the final load and any approved follow-up load.

Check the load and the retained history
  1. Step 01
    Agree the scope

    Record the source cutoff and where each record set belongs.

  2. Step 02
    Compare the load

    Check counts and values by the agreed group.

  3. Step 03
    Retrieve the history

    Have authorized staff complete a real task with a test record.

  4. Step 04
    Resolve and retest

    Give each difference an owner and repeat the affected check.

Keep each comparison and retrieval test with the load it belongs to so staff can repeat it after a correction.

References: [2]

Give each unresolved difference an owner

If the team uses an approved AI tool, give it the approved inventory of record types and field descriptions without student records. Ask it to flag unclear mappings and draft questions. Have the conversion lead check the questions against the mapping sheet and the Registrar or Student Accounts confirm the decisions for their records. Use the approved rules and reports for the reconciliation.

Give the sponsor the accepted comparisons, archive retrieval results and open items that could affect launch. Ask each office to say what it has checked and which differences still need a decision. Keep that approval with the specific load. If the team needs help comparing source and target reports or preparing the next rehearsal, bring the scope sheet and the unresolved items to a data and reporting review.

Sources

  1. Building a Strategic Path to SaaS — Ellucian (accessed )
  2. Student - Modernization — Solano Community College (accessed )
  3. Board Materials February 2026 — Banner SaaS Upgrade, p. 136 — Tennessee State University (accessed )
  4. Records Retention Schedule — University of Denver (accessed )