1. Inventory and clean the source data
Identify the systems and files holding active student, guardian, fee, transaction, marks and document records. Decide what must move, what must remain archived and who approves each dataset.
- Remove duplicates and inactive test records
- Standardise names, classes, dates and identifiers
- Reconcile fee balances before export
- Assign an owner to every source file
2. Map, import and validate
Use the destination formats supplied by the ERP team. SchoolPulse provides CSV templates so fields can be mapped consistently before import. Validate totals and representative student records before approving a full dataset.
- Prepare data in the supplied CSV formats
- Test a sample import first
- Compare student counts and financial totals
- Record exceptions and corrections
3. Prepare people and go-live controls
Train each role on the workflows they own and run both systems in parallel when the school requires it. Most schools can go live in around four weeks, but the realistic date depends on data readiness and decision speed.
- Role-based training before launch
- Parallel run when required
- Named support contacts
- Final sign-off from academic and finance owners