Agree the migration scope before asking for files
Separate current student and staff records from historical transactions, documents and archived academic years. Decide which data must be usable in the new system and which can remain in an accessible archive. Ask the provider to confirm supported import formats and any work that requires a supervised migration. One spreadsheet template rarely explains the whole project.
Write an acceptance checklist with the school owners. Reception might check active students and guardian numbers; finance might check opening balances and outstanding dues; the academic coordinator might check classes and subjects. Keep original exports unchanged in a controlled location. Cleaning copies can be revised, but the school should still be able to trace them back to what the previous system supplied.
Clean identifiers and relationships before importing
Use stable student identifiers to distinguish children who share a name. Standardise class and section labels, academic years, date formats and phone fields. Do not remove leading zeros from identifiers simply because a spreadsheet interprets them as numbers. Resolve duplicate records with the relevant school owner, since similar names are not enough evidence to merge two children.
Map how guardian contacts, siblings and class placement relate to each student. A household contact may legitimately appear on more than one record. Test whether the destination expects one value or several and whether the import keeps those relationships. SkoolMatic includes student import and profile workflows; demonstrate the actual template with a small representative sample before preparing the full file.
Treat opening balances as a finance review
Decide the date at which the new system becomes responsible for fee records. List outstanding amounts with the categories and periods needed to explain them. A carried balance and a newly raised fee demand should not accidentally charge the same amount twice. Finance staff should approve the mapping before a message or new receipt is produced.
For an illustrative check, suppose the agreed outstanding balance for one class is ₹45,000 across 18 students. The imported student balances should add to the same total, and a sample of individual records should match the approved breakdown. That arithmetic is a reconciliation example, not a prescribed accounting treatment. Keep disputed balances on a separate review list rather than making unexplained adjustments.
Pilot a small batch that contains awkward cases
Choose records that test the file format: a long name, a changed section, two siblings, an inactive student and a parent number needing correction. Import into the approved test or setup environment and inspect the resulting profiles. A successful upload count does not prove that the right fields reached the right students. Ask staff to find records through the screens they will actually use.
Record rejected rows and the reason for each correction. Confirm whether rerunning an import updates existing records or creates new ones, and use only the supported process. Avoid repeatedly uploading the full file while experimenting. Keep the pilot small enough that a reviewer can inspect every result, then obtain approval before the remaining data is moved.
Choose an editing cutover and a rollback decision
Agree a time after which the previous workspace stops accepting routine changes. Capture any final transactions entered after the first export and decide how they will be brought across. Tell staff which system to use on the next working day. Parallel editing without a reconciliation owner can make two plausible records disagree within a few hours.
Keep the previous data accessible under the agreed permissions and retention process until the school has completed acceptance. Define the conditions that would pause the move, such as unresolved financial totals or missing student links. A rollback is a planned operational decision, not simply an instruction to reopen the old software while staff continue creating records in both places.
Approve the result with the people who own the work
Check counts and totals, but also complete a real workflow with a sample record: find the student, inspect the guardian contact, review a fee balance and confirm class placement. Document unresolved exceptions with an owner and a date. The school decision-maker should know exactly what is complete and which historical material remains in the old archive.
SkoolMatic storage changes should follow the supported transfer process and compatibility checks; they should not be described as an automatic merge of databases. Before live use, confirm a usable recovery copy and named support contact. The school data backup and recovery guide provides a separate checklist for that protection. Finish the move with staff training on the records they will encounter first.
What schools should check
Scope
List live data, history and archives separately.
Identity
Resolve duplicates using stable identifiers and school review.
Finance
Reconcile agreed balances and supporting detail.
Cutover
Name one active workspace and approve the handover.
Related questions
Should a school import every historical record at once?
Only after confirming the operational need and supported migration path. Some history may remain in a controlled archive. Define what must be searchable or editable in the new system and test representative records first.
How can the school check that a student import worked?
Compare accepted and rejected row counts, inspect representative profiles and verify guardian, class and identifier fields. Then perform ordinary school tasks with the sample records rather than relying on a success message alone.
Can staff keep editing both systems during migration?
Only with an explicit reconciliation process. A safer planned cutover identifies when the previous workspace stops taking changes, who handles final transactions and which workspace becomes authoritative.
Explore the school software behind these workflows
Review the product workflow with your school team, then bring your current records and questions to a live demo.
Explore SkoolMatic featuresBook a Demo