Skip to content
mimiao
Docs

Students & groups

Import rollback & Migration Center

What to do when a student import goes wrong: a safe one-click rollback, plus the step-by-step Migration Center for a full school move.

Updated:

Imports in Mimiao are designed to make wrecking your base hard: before anything is written you always see a preview — who will be created, who will merge with existing students, what will be skipped. But if you realise after an import that it was the wrong file or the columns got mixed up — the import can be rolled back.

How import rollback works

Rollback is available to the school owner only and follows the principle “delete exactly what this import created — and only where it’s safe”:

  1. Open the import history and pick the run in question.
  2. Click “Roll back” — the system first shows a preview: how many students the import created, how many still exist, how many can be deleted safely, and how many are blocked.
  3. Confirm — and the system deletes only the “safe” students.

Blocked from deletion are students who have accumulated related data since the import: payments or invoices, scheduled lessons, group membership, courses, rewards and so on. Such profiles are never deleted silently — they are honestly listed in the rollback report, and you decide about them manually.

The rollback is idempotent: running it again is safe — what’s already deleted can’t be harmed twice.

Migration Center: the full school move

For moving from another CRM or spreadsheets there’s the Migration Center (Settings → “School” group → Migration) — a step-by-step plan of six stages in the right order:

  1. Teachers — the team’s profiles.
  2. Products and prices — the lesson packages that balances and payroll are computed from.
  3. Students — with product assignments and opening lesson balances, so the school knows from day one who has how many prepaid lessons.
  4. Groups — rosters and schedules.
  5. Lesson history — past lessons for reporting (they never charge balances).
  6. Payment history — past payments into the immutable ledger, with payer matching.

Each stage shows whether it’s already done, and the final callout spells out the safe cutover sequence: freeze the old system → export the data → run the final import with opening balances → reconcile the numbers → spot-check one student, the next lesson and financial analytics.

Tips

  • Don’t tidy your files in advance — the wizard flags duplicates, broken phone numbers and empty fields before the import.
  • Enter opening balances once, in the final import — after that, Mimiao keeps the books.
  • Running both systems in parallel for the first week is perfectly fine.