Column chaos
Boards and trusts each use different headers.
Migrate without the midnight spreadsheet panic
Custom Import maps your Excel/CSV columns into ScholarERP entities, validates rows, and lets you dry-run before anything touches production.
Map
any column layout
Dry-run
before commit
Errors
row-level feedback
The problem
Why “just upload the Excel” fails
Every school’s sheet is different — and one bad column silently corrupts an entire grade.
Partial loads
Half the file imports; nobody knows which rows failed.
No rehearsal
Teams discover errors only after parents see wrong fees.
Re-entry
Staff retype what the import broke.
Capabilities
What this module actually does
Operational depth your team will use every cycle — not a shallow feature list.
Template library
Student, guardian, fees, staff, and attendance starters.
Column mapper
Drag source columns to ScholarERP fields.
Validation engine
Type, required, and referential checks.
Dry-run mode
Preview creates/updates without writing.
Error export
Download failed rows with reasons.
Incremental loads
Update existing IDs safely.
Role gates
Only authorized importers can commit.
Job history
See who imported what and when.
Operating loop
How it works end to end
A clear path your staff and parents can follow without training manuals.
-
01
Choose
Pick an import template.
-
02
Map
Align columns and defaults.
-
03
Validate
Dry-run and fix errors.
-
04
Commit
Write to live modules with a log.
Who uses it
Role-aware access for every stakeholder
The right people see the right slice of the pipeline.
Migration lead
Runs onboarding loads.
Registrar
Loads student/guardian sheets.
Fee office
Imports structures and balances.
IT Admin
Maintains maps and permissions.
Connected stack
Works with the modules you already need
Each module is an edge in the campus operating graph — not a silo.
Outcomes
What changes after go-live
Measurable ops wins institutions report once this module runs inside ScholarERP.
Faster
go-lives
Fewer
re-keying hours
Safer
commits via dry-run
“Dry-run caught 140 bad mobile numbers before SMS ever fired.”
FAQ
Questions teams ask before buying
Straight answers for setup, integrations, and day-two operations.
Which formats are supported?
CSV and Excel workbooks are the primary paths; encoding guidance is provided for Indian sheets.
Can we import only updates?
Yes. Match on GR/roll/admission IDs and update changed fields.
What if a row fails?
Failed rows export with reasons; successful rows can still commit depending on job settings.
Is Custom Import included in migration services?
Yes — onboarding teams typically use these templates during free data migration.
Dry-run a sample student import
Map columns, see validation errors, and review the commit log.