Duplicates
Same child enrolled twice with different spellings.
Clean master data — before reports lie to you
Data Management gives registrars and IT a control room for validating, deduplicating, and repairing campus records so every module trusts the same truth.
Validate
on create and import
Dedupe
student & guardian matches
Repair
tools with audit trail
The problem
Why dirty data multiplies across modules
One misspelled student becomes three fee ledgers, two transport routes, and a failed exam hall ticket.
Broken links
Guardian phone missing when SMS fires.
Silent corruption
Imports overwrite fields nobody notices.
No ownership
Nobody owns “who fixes master data”.
Capabilities
What this module actually does
Operational depth your team will use every cycle — not a shallow feature list.
Validation rules
Required fields, formats, and board-specific checks.
Duplicate finder
Match students by name, DOB, and guardian mobile.
Merge & repair
Safe merge with preview before commit.
Field stewardship
Mark owners for SIS, fees, and HR fields.
Bulk cleanup
Fix empty sections, invalid emails, and orphan rows.
Import health
Score CSV loads before they go live.
Change history
See who edited critical master fields.
Cross-module impact
Preview which modules a merge will touch.
Operating loop
How it works end to end
A clear path your staff and parents can follow without training manuals.
-
01
Scan
Run quality checks on a campus dataset.
-
02
Flag
Review duplicate and invalid queues.
-
03
Repair
Merge or correct with approval.
-
04
Monitor
Watch quality scores by term.
Who uses it
Role-aware access for every stakeholder
The right people see the right slice of the pipeline.
Registrar
Owns student identity cleanup.
Fee office
Keeps payer identities consistent.
IT Admin
Configures validations and imports.
Auditor
Reviews merge history.
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.
Fewer
duplicate identities
Cleaner
SMS/WhatsApp delivery
Trustworthy
reports for leadership
“Duplicate cleanup alone recovered dozens of “ghost” fee accounts before audit.”
FAQ
Questions teams ask before buying
Straight answers for setup, integrations, and day-two operations.
Is this the same as Custom Import?
Custom Import loads files. Data Management governs quality after data is inside ScholarERP.
Can merges be undone?
Merges are logged; restore paths depend on backup policy and the merge type.
Do teachers see this module?
Usually no — it is an admin/registrar tool.
Does it work multi-campus?
Yes. Run scans per campus or across the trust with scoped permissions.
Run a sample duplicate scan
See match confidence, merge preview, and audit trail on demo data.