The single biggest reason schools abandon new software isn't price or features, it's an onboarding that drags on long enough that the original champion gives up. We learned that the hard way and rebuilt our entire deployment process around a fourteen-day promise.
Here's how it works.
Days 1–2: discovery
We sit with the director, the head of administration, and one or two senior teachers. No demos yet, just a list of every tool, spreadsheet, and form they currently use. The exercise tells us what to migrate, what to retire, and what to leave alone.
Days 3–5: data import
Most of the heavy lifting happens here. Student records, family contacts, class structures, and historical fee balances are imported through templated spreadsheets we provide. Our team validates everything and shares a clean preview before any record is committed.
Days 6–8: configuration
Roles, permissions, payment cycles, communication preferences, and report cards are configured to match the school's actual workflow. We don't ask schools to change how they work to fit our software, we adjust the software.
Days 9–11: training
Two short sessions per audience: one for administrators, one for teachers, one for parents (when the parent module is in scope). Recordings stay in the school's library; the cheat-sheets stay on every desk.
Days 12–13: parallel run
The school keeps the old process running alongside EdTrust for two days. Discrepancies are logged and fixed before cutover.
Day 14: cutover
EdTrust becomes the source of truth. The old tools are archived. The first morning is staffed by our team, in person where we can, on call when we can't.
It isn't magic. It's a checklist, run hundreds of times, refined with every school. The key insight is small: trust is built in the first two weeks, or it isn't built at all.