School Software Data Migration: The Complete Checklist (2026)

Data migration is where most school software rollouts go wrong. Here is a checklist that gets your records moved accurately, with nothing lost.

Quick answer: To migrate school data safely: export students, parent contacts, staff, classes, subjects, fee structures and dues, and academic history; clean the files (remove duplicates, standardise class names, verify phone numbers); have the vendor import them; then verify counts, spot-check records, and confirm fee balances before going live. Keep your original exports as a permanent backup. AcadLynk does the import for you, free.

Why migration decides whether the software works

Schools rarely abandon new software because of missing features. They abandon it because their data never fully arrived, so staff keep one foot in the old registers. Half-migrated data means duplicate work, mistrust in the numbers, and eventually a return to spreadsheets. Getting migration right is therefore the single most important step of any rollout - and it is mostly about preparation rather than technology.

Step 1: Export everything you have

Pull your data out of wherever it lives - old software, spreadsheets, or registers typed up. Aim for one clean file per category. If your current vendor makes export difficult, ask them directly for your data; it belongs to your school.

  • Students: name, date of birth, gender, class, section, roll number, admission date
  • Parents/guardians: name, relationship, phone number, email, address
  • Staff: name, role, subjects, contact details
  • Academic structure: classes, sections, subjects, teacher assignments
  • Fees: fee heads, amounts per class, discounts, paid history and outstanding dues
  • Academic history: past results or report cards you want retained

Step 2: Clean the data before it moves

This is the highest-value hour of the whole project. Migrating messy data just relocates the mess and destroys staff confidence on day one. Work through each file methodically - most problems are simple inconsistencies rather than missing information.

  • Remove duplicate student records
  • Standardise class and section naming (e.g. 'Class 5 A' everywhere, not '5A'/'V-A')
  • Verify parent phone numbers - at least one valid mobile per student
  • Fix date formats so all dates of birth are consistent
  • Confirm fee amounts and outstanding balances against your ledger
  • Flag students who have left so they are not imported as active

Step 3: Hand it to the vendor to import

Insist that the vendor does the import. 'Done-for-you onboarding' is the difference between going live in a week and struggling for months, and it should be free. If a vendor expects your office to hand-enter hundreds of records during term time, factor that cost into your decision - or pick a vendor who does it for you.

Step 4: Verify before you trust it

Never go live on unverified data. Run these checks first - they take under an hour and catch almost every migration problem while it is still easy to fix.

Check counts

Does the total number of students, staff and classes in the new system match your export exactly?

Spot-check records

Pick 10 students at random across different classes and compare every field against the source.

Verify fees

Confirm fee structures per class and, critically, that outstanding dues match your ledger. Fee errors erode trust fastest.

Test a workflow

Mark attendance for one class, record a payment, and generate one report card end to end.

Step 5: Keep a permanent backup

Archive your original export files somewhere safe and do not delete them. Also keep your old system accessible in read-only mode until you have completed one full fee cycle and one full exam cycle on the new platform. This safety net removes fear from the transition - staff know nothing can be lost - and in practice you will stop referring to it within a couple of cycles.

Common mistakes to avoid

A few patterns cause most migration pain, and all are avoidable with a little planning.

  • Migrating in the middle of exams or a fee deadline
  • Importing dirty data and fixing it afterwards inside the new system
  • Skipping verification and discovering fee errors from a parent complaint
  • Not importing outstanding dues, so collection history is lost
  • Deleting the old export files once it 'looks fine'

Migration with AcadLynk

AcadLynk includes free done-for-you migration: you send your cleaned export files, and the team imports students, parents, staff, classes, subjects, fee structures and outstanding dues, then walks you through verification. Bulk CSV import is also available if you prefer to do it yourself. Most schools are live in about seven days, and because the 14-day free trial lets you validate one class end to end first, you can confirm your data is right before committing to anything.

Frequently asked questions

What data should a school migrate to new software?

Students with parent contacts, staff, classes/sections/subjects, fee structures with outstanding dues, and any academic history you want retained.

Should we clean data before or after migration?

Before. Importing messy data just relocates the problem and undermines staff confidence in the new system from day one.

How do we verify a migration worked?

Match record counts against your export, spot-check ten students field by field, confirm fee structures and outstanding dues against your ledger, and test one full workflow end to end.

Does AcadLynk migrate our data for us?

Yes. Done-for-you migration is included free - you send cleaned exports and the team imports students, staff, classes, fees and dues, with most schools live in about seven days.

Related guides & pages