Import existing school spreadsheets without treating every row as automatically correct.

Excel migration is fastest when the school first cleans identifiers and class names, then uses preview and validation to catch problems before they become database records.

Choose the right import path

Use the official School Master template when the school can prepare data in the recommended structure. Use Flexible Excel Mapping when the existing workbook already has useful data but uses different header names.

Map meaning, not just similar words

A header such as “GR No”, “Student No” or “Admission No” may mean different things in different schools. The operator should understand what the source column represents before mapping it to the School Master field. Similar-looking text is not enough.

Standardize class and division values

Before import, normalize repeated values such as “Std 1”, “1”, “Class 1” or “First”. The ERP can store what the school chooses, but inconsistent labels make reporting and class permissions harder.

Preview before writing

The preview stage is where the school should inspect detected sheets, mapped headers, sample rows and validation messages. It is better to stop here and correct the workbook than to import thousands of rows and clean them later.

Duplicate protection is a feature, not an inconvenience

If a GR or another authoritative identifier already exists, the import should not blindly create a second student. Review duplicates and decide whether the source row is old, incorrect or genuinely represents another record.

Import in controlled batches

For a large migration, split work into logical batches such as students first, then fee-related historical data after the student identities are stable. Keep the original source file and note the import date or case reference so later questions can be traced back to the source.

Take a backup checkpoint

Before a large import into an active workspace, create a verified backup. A safe import pipeline reduces risk, but a rollback checkpoint is still good operational discipline.

Post-import verification

• open a sample of students from different classes;
• compare total imported row count with the expected valid-row count;
• check duplicate/error rows separately;
• verify class/division filters and teacher scopes;
• check one or two downstream workflows such as fees or attendance.