Moving to a new school ERP: a data migration checklist

Changing school software is mostly a data job. What to export from the old system, how to check it, the best time of year to switch, and what to keep afterwards.

On this page
  1. What data needs to move?
  2. How do you migrate, step by step?
  3. When is the best time to switch?
  4. What does a fee check look like?
  5. What's the hard case in a migration?
  6. Frequently asked questions

Moving to a new school ERP is mostly a data job: export student, parent, fee and marks records from the old system, clean them, import them into the new one, check them against the old system, and switch over at a quiet point in the year, ideally between academic years. Keep a full export of the old system afterwards. Schools that skip the checking step spend the first term fixing fee balances and wrong sections.

Who this is for: schools switching from one school software to another, or from spreadsheets to an ERP. Who it isn't for: schools adding a single standalone app.

Cloudgramam makes Classveda, a school ERP, so we have an interest here. The checks below work for any product you compare.

What data needs to move?

DataWhy it mattersWatch out for
StudentsEverything hangs off the student recordDuplicate admission numbers, spelling variants
Parents and contactsAlerts and the parent app depend on themOld phone numbers, siblings linked to the wrong parent
Classes and sectionsAttendance, timetable and report cards use themSection names that differ between systems
Fee balancesParents will check them firstPart payments, concessions and carried-over dues
Marks historyReport cards and transfer certificatesOlder years in a different grading scale
StaffLogins, classes and subjectsTeachers who left but still hold classes

How do you migrate, step by step?

  1. Export everything from the old system, in a standard format such as CSV or Excel, before anything else. Keep this copy for good.
  2. Clean the student list: remove duplicates, fix admission numbers, confirm current class and section.
  3. Clean parent contacts and confirm siblings are linked to the right parent account.
  4. Agree the fee position for every student on a cut-off date: paid, due, concessions.
  5. Import into the new system and set up classes, subjects and fee structures first.
  6. Check samples: pick twenty students across classes and compare every field with the old system.
  7. Check totals: student count per class and total fees due should match exactly.
  8. Run both systems for a short overlap if you can, then switch.
  9. Tell parents what's changing and how to log in, a week before.
  10. Keep the old export for audits and old transfer certificates.

When is the best time to switch?

Between academic years, after report cards are issued and before new admissions start, so there's no half-finished term to reconcile. Mid-year switches are possible but mean moving part-term marks and part-paid fees, which is where most errors happen.

What does a fee check look like?

This example is made up. After import, the new system shows ₹18.4 lakh due across the school; the old system shows ₹18.9 lakh. Checking class by class finds the gap in Class 9: ₹50,000 of concessions recorded in the old system as notes rather than as concessions. They're entered properly, the totals match, and only then does the school switch.

What's the hard case in a migration?

The same child recorded twice, with money attached to both records. A realistic scenario: a student left in Class 5, came back in Class 7, and was given a new admission number. The old system now holds two records for one child. One has an unpaid ₹3,000 from Class 5; the other has an advance payment of ₹5,000 from this year. Their younger sibling is linked to the first record's parent account, not the second.

Import both as they are and the new system shows two children, two parent accounts and a fee position nobody can explain. Merge them carelessly and you lose the history.

How to handle it:

  • Find likely duplicates before import by matching name, date of birth and parent phone, then confirm each one by hand.
  • Keep one student record, with both old admission numbers stored on it so old receipts and certificates still match.
  • Bring the money across as one balance: the ₹3,000 due offset against the ₹5,000 advance leaves a ₹2,000 credit, with a note explaining it.
  • Link both siblings to the same parent account, and check the parent sees both children.

Do this check for every family with more than one child; sibling links are where duplicates hide.

Frequently asked questions

Can we import data from our current school software?

Usually, if it can export to CSV or Excel. Ask your current vendor how before you sign with a new one.

Should we move old years' marks?

Move what you need for report cards and certificates. Keep the full old export for everything else.

How long does migration take?

It depends on how clean the data is. Cleaning and checking take longer than the import itself.

Who should do the checking?

Someone from the school office who knows the records, working with the vendor. The vendor can import; only the school can confirm it's right.

For choosing the new system, see school ERP software in India and school ERP vs separate apps. Planning a move? See Classveda.

school erpschool erp migrationschool data migrationswitch school softwareschool management software migration

Gowtham D

Full Stack Digital Marketer and Full Stack Developer

Gowtham D is a full stack digital marketer and full stack developer, a Microsoft Power Platform developer, content writer and data analyst with 15 years of experience.

Gowtham D on LinkedIn

School ERP with an AI tutor

Classveda runs attendance, fees, timetables and report cards, with a parent app and an AI tutor for CBSE, ICSE and state boards.