Moving your learning centre off Excel and onto a CRM

Almost every learning centre starts in Excel, and for 30 students a spreadsheet is plenty. Trouble comes later. More students, more groups, one file becomes two, then three. One evening the director retypes the debtors list for the third time — and still misses someone. That is the point where you need a CRM for a learning centre.

When Excel stops coping and a learning centre needs a CRM

There is no exact threshold, but there are signs you can check against your own centre in five minutes. No report is needed — you feel them at the end of every month.

• More than 100 active students, and at least two people editing the same file.
• You build the debtors list by hand, and it costs over two hours a month.
• Asked “has this student paid this month?”, you cannot answer at once — you open the file and search.
• Attendance in a paper notebook, payments in Excel — reconciling the two is a job of its own.
• You learned a student had left a month after they stopped coming.
• Teacher pay is worked out on a calculator, then rechecked every month.

If three of those apply, the problem is not Excel — it is the method. Excel is a good tool, just never built for several people working at once on a calculation that repeats every month. The next step is student database software: one place for the records, with the totals adding themselves up.

Clean the list before you migrate

The most common mistake is migrating a dirty database. Duplicate rows, students who left six months ago, empty phone fields, the same group written three different ways — A1, a-1 and A 1. All of it travels with your data and costs you twice the time later. Clean before the migration, not during it.

1. Collapse every file and tab into a single sheet. One rule: one student, one row — even if they attend two groups.
2. Fix the columns: name, date of birth, student’s phone, parent’s phone, group, start date, monthly fee, discount, status.
3. Put every number in the same format — +998 XX XXX XX XX. Keep the parent’s number in its own column, because that is where messages will go later.
4. Give every row a status. No payment and no attendance in the last 60 days — mark it as left. The active list usually shrinks more than you expect.
5. Write one canonical list of group names. Each name once: subject, level, time slot. Something like “English A1 / 18:00”.
6. Add one final column — outstanding fees as at your cut-off date. This is the single most important number in the migration.

Migration order: students, groups, payments, attendance

The order matters because each stage rests on the one before. No groups, no timetable. No students, nowhere to record a payment. No timetable, nothing to mark attendance against. Work through it in sequence, not in one long day.

Stage one — students and groups

Enter the active students only. Leavers stay in the archived spreadsheet and can be added later if needed. Then create the groups and attach a teacher, a room and a lesson time to each. Check one thing here: every active student belongs to at least one group. A student with no group later drops out of attendance and out of your reports.

Stage two — payments

This is where most centres sink: they try to move the whole payment history. You do not need to. Pick a cut-off date — the first of the month works well. Outstanding fees at the cut-off date stay in the last column of your list — how they get into the system is settled during the demo and setup. Every payment after the cut-off goes into the new system only. The old history stays as an archive and you leave it alone. That one decision shortens the migration noticeably.

Stage three — attendance

Do not backfill attendance. Start on the first day of a new week: it is a daily habit, not a record to be reconstructed. In that first week, check the parents’ phone numbers specifically. In MUDARRIS, for example, marking attendance sends the parent a Telegram message at that same moment — a mistyped number reaches the wrong person, and you want to know on day one.

Payroll, exams and reports belong to the second month. Four things working in month one is enough: the student list, the groups, payments and attendance. The rest is easy to add on top.

Run both systems for one month

Do not delete the spreadsheet on day one. Keep it a month, on one strict condition: nobody writes in it. It is there to be read and reconciled against.

• After the cut-off date, new data goes into the CRM only. No exceptions.
• Once a week, 30 minutes: compare three numbers — active students, fees collected since the first of the month, and debtor count.
• Write down every difference with its cause. It is nearly always the same one: someone carried on the old way.
• By the second week the gap should be shrinking. If it is not, the problem is not the data — it is the people.
• If all three numbers match at the end of the month, close the file and archive it.

Parallel running should never stretch past two months. Beyond that both databases end up incomplete and nobody trusts either. Announce the date in advance: “from the first of the month, no notebook and no spreadsheet”.

Getting teachers to actually mark attendance

Technically the system works from day one, but without marks it is empty. The hard part is people, and what works is one short, exact rule, not long training.

1. Name one person in charge, usually the administrator. Questions go to them, not to the director.
2. Give every member of staff their own login and their own role, so each sees only their own work.
3. Keep the first training under 20 minutes and about one action: mark attendance within 10 minutes of the lesson starting.
4. Set a deadline. The notebook goes away in two weeks — and that date must be said out loud.
5. Do not allow two methods at once. While the notebook is on the desk, teachers will use the notebook.
6. For the first week, have the administrator check daily that every lesson has been marked. Not a telling-off — help. Usually it is the phone or connection.

The strongest incentive is pay. When the lesson and the pay live in the same system, marking becomes a habit. For planning, allow three weeks and check that against your own centre. Explain it as order rather than surveillance: the lesson is recorded in one place, so the pay is worked out there too.

Three questions at the end of the first month

Whether the move worked is not a feeling. It is three questions.

1. How many minutes does it take to produce the debtors list? The right answer is one.
2. Can you tell in the morning who missed yesterday’s lesson? If not, the habit has not settled yet.
3. Do collections and outstanding fees match your own spreadsheet? If not, there is a difference nobody has explained.

Three yeses mean the migration is finished. From there you add reports, payroll and exam results — they land on a database already in order.

The next step is choosing a system. In Mudarris CRM the four stages above are separate modules; the plan depends on your centre’s size and the modules you need, and the exact price is agreed during the demo and setup. Put your centre in order starting today — press “Get started”, leave your name and phone number, and we will call you within one working day. Or use “Request a demo” to write to us directly on Telegram.