Implementation
Most schools are live in 30 days. We handle the migration.
The question we get most: "What happens to our existing records?" The answer: we bring them with us.
Four phases. One implementation contact throughout.
Data audit
Week 1We review your existing records — student files, fee history, academic history, staff records. We tell you exactly what we can migrate and in what format.
Configuration
Week 1–2We set up your school in Msingi — curriculum, classes, fee structures, academic year calendar, user roles, and permissions. You review and approve.
Parallel run
Week 2–3Your team uses Msingi alongside your existing system for 1–2 weeks. We verify that every record matches, every workflow is configured correctly, and every user is trained.
Go live
Week 3–4Switch. Old systems are archived, not deleted. Msingi is now your system of record. Your implementation contact remains available for the first 90 days.
What we migrate.
Every record. Verified. No data left behind.
Things schools always ask before switching.
"We have 10 years of student records in spreadsheets."
We have migrated records in every format — Excel, CSV, Google Sheets, old ERP exports, and paper scans. No record is left behind. Every migration is verified before go-live.
"Our staff are not technical."
Msingi was designed so that a teacher who has never used school software before can mark attendance correctly on day one. We train every user role separately, and training videos remain available forever.
"We are mid-term. We cannot switch right now."
We recommend starting implementation at the beginning of a term, but it is not a hard requirement. Many schools have switched mid-term without disruption. The parallel run period ensures continuity.
Start with a discovery session.
We audit your current records and tell you exactly what implementation looks like for your school — before any commitment.