School ERP Data Migration Checklist for Bursars and Admin Teams

Data migration is one of the most critical parts of school ERP implementation. If data is inaccurate at go-live, confidence in the new system drops immediately.

Use this checklist to prepare your migration correctly.

Phase 1: Data preparation

• List all data sources (spreadsheets, accounting files, legacy apps)
• Define data owners per department
• Freeze a migration cut-off date

Phase 2: Data cleanup

• Remove duplicates (students, guardians, accounts)
• Standardize naming conventions
• Validate opening balances and fee records

Phase 3: Mapping and templates

• Map old fields to new ERP fields
• Prepare import templates per module
• Validate required vs optional fields

If you are deploying CatVision, align your templates to the expected module structure from the CatVision ERP page .

Phase 4: Test imports

• Run imports in staging first
• Verify sample records with bursars and admins
• Check summary totals against source data

Phase 5: Go-live checks

• Confirm user permissions
• Validate top 20 critical reports
• Confirm statement and portal visibility if enabled

For schools enabling parent/student access, ensure migration also supports required portal views from the School Portal solution .

Post-go-live quality control

• Track data issues daily for first 30 days
• Assign owners and SLA for fixes
• Keep a migration audit log

Final advice

Treat migration as a managed project, not a one-day import task. Strong preparation saves months of rework.

Need support for migration planning and validation? Radical Systems can guide your bursar and admin teams through a safe rollout. Contact us .