Acadovia Start free month

Migration playbook

Switching to Acadovia from Excel, Entab or Fedena

What the dual-run actually looks like, how long migration takes, where fee-desk risk lives, and how training works — written for principals who cannot afford a chaotic April.

Updated 20 July 2026 Audience Principals, office in-charge, IT coordinators Owner Acadovia product team
Acadovia onboarding
We run migrations ourselves — not a separate SI firm. Phone/WhatsApp: +91 85281 00305. This page is the public version of what we walk through on kickoff calls.

Who this is for

We are not claiming your current vendor is “bad.” We are claiming a switch is survivable if you respect the fee calendar.

Honest timeline

Starting pointTypical time to first live weekWhat dominates the clock
Clean Excel roster + simple fee heads5–10 working daysData hygiene, not software
Messy multi-sheet Excel, many concessions2–4 weeksCleaning names, sections, fee exceptions
Export from another ERP1–3 weeksMapping fields; partial re-entry of history

Marketing lines that promise “live in 24 hours” usually mean “login exists,” not “fee desk trusts the balance.” We aim for a real working week: attendance marked, a receipt issued, principal dashboard credible.

The dual-run (non-negotiable)

Do not cut over on the morning of a major fee instalment. Run both systems briefly:

  1. Kickoff & exportYou share student master, class/section, fee heads, staff list (Excel or ERP export). We map fields and flag missing phone numbers / duplicate admissions.
  2. Sandbox weekSchool admin + fee clerk + 2 teachers click through on phones. Wrong data is free to fix. Old system remains system of record.
  3. Parallel fee cycle (recommended)One instalment or one class cluster is collected on Acadovia while Excel/old ERP stays as backup. Reconcile nightly for 3–5 days.
  4. Attendance go-liveTeachers mark only on Acadovia for selected classes; expand after a quiet week.
  5. Freeze the old ledgerOld system becomes read-only archive. Keep exports. Acadovia is system of record.

Fee-desk risk (what can go wrong)

If the fee desk is not confident, we delay parent-facing portals. Internal use can go live first. Pride is a bad migration schedule.

What we import (and what we do not pretend)

Usually importedOften re-createdOut of scope without project work
Students, guardians, classes/sectionsTimetable aestheticsCustom biometrics hardware glue
Staff roster & rolesNotice templatesOne-click clone of proprietary reports
Fee heads, structures, opening duesFine-tuned permission matricesHistorical chat/SMS archives

Price: standard data import is included — no setup fee. Custom multi-campus consolidations may need a scoped project; we say so before you start.

Training that actually sticks

We do not hide behind “raise a ticket, SLA 72 hours” during go-live week.

Coming from Entab / Fedena / similar

Expect to export CSVs (or print-to-Excel reports) rather than a magical API pull. Your exit rights with the old vendor vary — start that conversation early. We map columns together; leftover custom modules may not have a 1:1 twin, and we will tell you before you pay.

Live vs roadmap honesty matters in a switch: Acadovia’s fee path is UPI QR + UTR + cash/cheque today; gateway payment links and WhatsApp notice delivery are roadmap. If those two are must-haves this month, wait or pick another vendor. If phone-first ops, clear pricing and honest pricing matter more, we are built for you.

Exit from Acadovia (symmetry)

You can export full CSVs anytime. We think lock-in is a bad reason to keep any school software — including ours. Details in Terms and Privacy.

Book a migration walkthrough

Send a sample Excel or export. We will tell you — in writing — what imports cleanly and what needs a week of hygiene.

Related: ERP vs Excel · ERP cost India · Pricing