Moving from Excel and paper registers to a school ERP: a cut-over plan that works.

When should a school move from Excel to an ERP?

Move when the records have outgrown the people who keep them, and do it at the start of an academic session. Then there are no half-collected terms to split, and the old sheets can stop on one day and the new system start on the next. If a mid-session switch cannot be avoided, use the first day of a month and import each student's unpaid balance as an opening balance.

Excel's size limits are not the reason. A worksheet holds 1,048,576 rows and 16,384 columns, and one cell holds 32,767 characters,^[1] far more than any school's student list needs. The trouble is elsewhere. A school management system in Excel usually grows one sheet at a time: a student list, then a school fee management system in Excel with a column for every month, then a student management system in Excel for marks. Each file works for the person who built it. Then copies drift apart, the same student is spelt three ways, and nobody can say which total is right.

Our ProEMS vs Excel comparison sets out what an ERP adds and what Excel still does well, and our school ERP cost guide covers what it costs. This guide is about the move itself.

What are the steps to move from Excel to a school ERP?

There are eight steps: fix the cut-over date, list every sheet and register, clean the data, decide what to migrate, import a test batch and check the totals, train staff, run old and new in parallel, and switch over. The sections below take each in turn.

1. 1

   Fix the cut-over date

   The day the new system becomes the record. Work backwards from it: cleaning takes longest, so start there. Tell staff, parents and your fee clerk the date early.
2. 2

   List every sheet and register

   Every workbook, paper register and receipt book, who keeps it, and which copy people trust.
3. 3

   Clean the data on a copy

   One row per student, admission numbers as unique IDs, consistent class and section names, real dates, clean phone numbers.
4. 4

   Decide what to migrate and what to archive

   Current students, parents, staff, the fee structure, opening balances and dues, and this year's receipts move. Everything older is archived.
5. 5

   Import a test batch and check the totals

   Start with one class, then the whole school. Compare counts and amounts with the sheets before you go on.
6. 6

   Train staff

   Each person learns the few tasks they do every day, on the school's own data.
7. 7

   Run old and new in parallel

   For a set period, with one named person comparing the two every day and a fixed end date.
8. 8

   Switch over and archive

   Make the old sheets read-only, keep one archive copy under access control, and delete loose copies.

How do you list every sheet and register a school uses?

Walk through the office and write down every file, register and receipt book, who keeps it and what it feeds. Do this before you look at any software, because the list decides what you import and what you retire.

Ask for the private copies too: the accountant's own workbook, the clerk's phone list, the class teacher's sheet. If two files disagree, settle which one is true now and write it on the list. That conversation is much cheaper before the import than after it.

How do you clean school data before importing it?

Work on a copy and fix six things: duplicate rows, admission numbers, class and section names, dates, phone numbers and long ID numbers. Whatever is wrong in the sheet will be wrong in the ERP, only harder to see.

Fill every blank you can from the paper file. Where a value is truly unknown, use one agreed marker instead of a mix of blanks, “NA” and dashes, so you can find them all later.

Which student details should the sheet carry for APAAR and UDISE+?

If you will generate APAAR IDs, carry the fields the Ministry's FAQ lists as mandatory: PEN, student name, date of birth, gender, mobile number, mother's name, father's name, name as per Aadhaar and Aadhaar number.^[5] Cleaning them once now saves fixing them later in several systems.

Names are where schools stumble. The FAQ says the student's name in UDISE+ must match the name on Aadhaar, and that generation fails when the demographic details don't match.^[5] It also says the school verifies the details and takes parental consent for minors, and that students, parents, the school administration and class teachers are all responsible for accurate data.^[5]

Parental consent is a live question, so don't make Aadhaar a required column for every child. Collect it where you will use it. Our UDISE+ and APAAR guide covers the consent position, and the glossary has short entries for APAAR ID and UDISE+.

What should you migrate and what should you archive?

Migrate what you need to run the school from the cut-over date, and archive the rest as read-only files. Importing years of history multiplies the cleaning work and rarely changes a decision.

Archive means keep, not forget. We found no single national retention period for school records, so ask your board, your state education department and your CA how long each type must be kept before you discard any paper. The DPDP Act also says a data fiduciary must erase personal data once its purpose is no longer served, unless a law requires it to keep the data (section 8(7)).^[6] Write a retention date on every archive.

How do you check the import and run both systems in parallel?

Check the totals after every import by comparing them with the old sheets, then run both systems side by side for a fixed period with one person comparing them daily. Never trust an import that merely looks right.

1. Students per class and section

   Count rows by class and section in the sheet and in the new system. They must agree before you check anything else.

2. Total outstanding dues

   The sum of opening balances equals the dues total in your sheet at the cut-over date. If it doesn't, find the student, not the total.

3. Total collected this year

   Totals by fee head and by month equal the receipt books or the collection register.

4. Ten students checked by hand

   Pick students from different classes, including a sibling pair, a concession student and one with a part-paid fee. Compare name, class, contact, fee structure and dues with the paper file.

5. IDs and phone numbers

   No admission number or phone number has lost its leading zeros or turned into scientific notation, and no admission number appears twice.

6. Staff list

   The count and roles match the register.

7. Sign-off

   The accountant and the principal each sign the comparison. File it with the archive.

For the parallel run, we suggest at least one full fee cycle or a month of attendance, whichever is longer. That is our suggestion, not a rule. Decide which system is the record each day. Have one person compare the day's collection in both every evening, and settle any difference that day. Set the end date before you start, because a parallel run with no end date means the migration never finishes.

How do you train staff for the new system?

Train each person on the few tasks they do every day, using the school's own students, before the parallel run begins. Training on demo names teaches the screens but not the school's real cases.

• Front office: admissions, student details, certificates and parent queries.
• Fee desk: raising fees, taking payments, issuing receipts and the end-of-day totals.
• Class teachers: daily attendance and entering marks.
• Principal and management: the reports they will ask for every week.

Name one confident user in each group as the go-to person for the first fortnight, and give everyone a one-page sheet of their five tasks. Give each person their own login and agree who can only view and who can edit. Shared logins make errors untraceable, and that matters most at the fee desk.

Does digitising paper registers bring the DPDP Act into play?

Yes. The DPDP Act applies to personal data collected in non-digital form and digitised afterwards (section 3(a)(ii)), so typing the admission register into Excel or an ERP brings those records under it.^[6] Most students are children, and the Act treats anyone under 18 as a child (section 2(f)). Section 9(1) requires verifiable parental consent before processing a child's data. The Rules exempt educational institutions only for tracking and behavioural monitoring in limited cases, and how this applies to ordinary records is a question for your lawyer.^{[6, 7]}

Migration is a good moment to build three habits.

• Collect only what you need. Consent is limited to the personal data necessary for the specified purpose (section 6(1)), so don't import columns nobody uses.^[6]
• Secure what you keep. Section 8(5) requires reasonable security safeguards, and rule 6 lists the minimum: encryption or masking, controlled access, logs and monitoring, measures for continued processing after a loss, and keeping logs for one year.^{[6, 7]} A workbook on a teacher's laptop or a shared pen drive has no access log. The Rules' main duties start eighteen months after publication, which we count as 13 May 2027.
• Retire the loose copies. After the import is signed off, delete the working copies and keep one archive under access control, with a retention date.

Our DPDP Act guide for schools sets out the duties in full. This is a summary, not legal advice.

How does ProEMS handle a move from Excel?

ProEMS has Import Excel and migration templates in Settings. You copy your cleaned data into the template's columns and import it. Ask in the demo which of your sheets have a template, in particular the fee structure and opening balances, because the templates differ from sheet to sheet.

If your records are on paper, type them into Excel first and apply the cleaning above. Migration from sources other than Excel is not part of the standard offer, so talk to us before you plan one.

There is no setup fee, no lock-in and a one-month free trial. Use the trial for the test import: bring one class's real data, check the totals as above, then decide. Your data sits on Amazon Web Services in Mumbai (ap-south-1), with backups kept for 7 days. On the Gold plan the day's collection report makes the evening comparison during the parallel run quick. On every plan, each role can be given read-only or full edit rights for each module. See pricing for the plans.

Sources

Every fact on this page about rules, prices or other products comes from one of these. We read each one on the date shown and will update this page when they change.

1. Microsoft Support. Excel specifications and limits (support.microsoft.com). Read 21 October 2026.
2. Microsoft Support. Filter for unique values or remove duplicate values (support.microsoft.com). Read 21 October 2026.
3. Microsoft Support. Apply data validation to cells (support.microsoft.com). Read 21 October 2026.
4. Microsoft Support. Format numbers to keep leading zeros in Excel for the web (support.microsoft.com). Read 21 October 2026.
5. Ministry of Education (copy hosted on a school website). FAQs for APAAR (dpsgurgaon.org). Read 21 October 2026.The Ministry's own site was not reachable when we read it, so this is a school-hosted copy of the Ministry document. It is undated.
6. Gazette of India (Ministry of Law and Justice), copy hosted by the Ministry of Electronics and Information Technology. The Digital Personal Data Protection Act, 2023 (No. 22 of 2023) (meity.gov.in). 11 August 2023. Read 21 October 2026.
7. Ministry of Electronics and Information Technology, Gazette of India. Digital Personal Data Protection Rules, 2025, G.S.R. 846(E) (meity.gov.in). 13 November 2025. Read 21 October 2026.