Migrating from Fedena or Teachmint — A Step-by-Step Guide for Schools

ERP migration is the single biggest reason schools delay switching to a better system. The fear of losing data, mid-year disruption or parent confusion keeps schools on platforms they have already outgrown. This guide demystifies the process — based on the 60+ migrations EduGradUP has run from Fedena, Teachmint, MyClassboard, PowerSchool and Excel.

Phase 1 — Pre-migration audit (week 1). Export everything from your existing system to CSV. List every module: students, staff, classes, fees, attendance, gradebook, transport, hostel, library. For each, count rows and note any custom fields. This list is your migration scope; nothing surprises you later if it isn't on this list now.

Phase 2 — Data cleansing (week 1–2). Run three passes through the exported data: (1) duplicate students (same name + different IDs because of typos), (2) orphaned records (fee receipts without a student), (3) ambiguous fields (free-text class names that should be standardised). 80% of migration pain comes from skipping this step.

Phase 3 — Trial migration (week 2). Load all data into a sandbox tenant of the new ERP. Pick 10 random students and walk through their full record end-to-end — admission, fees, attendance, grades. If anything is wrong, fix the migration mapping, not the data. Repeat until 10 random students look clean.

Phase 4 — Stakeholder validation (week 3). Show the migrated sandbox to your bursar, two teachers and your principal. Ask each one specific questions: 'Can you find Anjali Khatun's January fee receipt?' 'Can you generate Class 8B's mid-term report card?' Their feedback is more valuable than any automated test.

Phase 5 — Cutover (week 4). Pick a quiet weekend — usually a Friday afternoon between terms. Freeze data entry in the old system at 5pm Friday. Run final delta migration. Open the new system Saturday morning. Critically, keep the old system live in read-only mode for 90 days as a fallback.

Phase 6 — Parent and teacher onboarding. Send a one-page parent guide in the local language. Run a 30-minute Zoom for teachers, recorded. Keep a hotline open for the first two weeks with a named CSM responding within 4 hours. Most questions are about logging in and finding the dashboard; document the answers and pin them to the help centre.

Common failure modes to avoid: do not migrate during result week or admission season; do not skip the sandbox phase to save time; do not delete the old system until 90 days have passed; do not assume the migration is over until your bursar has closed one full month-end on the new system.

EduGradUP includes the full migration in our standard onboarding, with a named onboarding manager owning all 6 phases. If you are mid-evaluation and worried about migration risk, ask any vendor to send you their written migration playbook. The detail (or absence) of that playbook tells you everything about whether their migration team is real.