Moving your madrassa to new software: a practical transition guide

A new system should make the teaching day easier. Getting there takes more than importing a student list. Teachers need a routine they can follow, families need clear information, and management needs to know which record everyone should use.

Whether your madrassa is moving from paper registers, spreadsheets or another platform, start with a small, agreed plan. This guide suggests a rollout you can adapt to your teaching week, staff capacity and existing arrangements.

Start with the problem you want to solve

Write down the two or three things that create the most avoidable work. Perhaps attendance reaches the office late, parents cannot find learning updates, or fee balances depend on one person's spreadsheet.

Choose an initial scope that addresses those problems. One madrassa might begin with attendance and family access, then add progress tracking. Another might need a carefully checked fee migration first. You do not need to introduce every available feature on the same day.

Describe success in everyday terms: each class completes its register, families can see the right learner records, and staff know where to ask for help.

Give each part of the change an owner

Name one person to coordinate the rollout. Agree who will prepare records, check access, train staff, communicate with families and decide whether the launch is ready. In a small maktab, one person may cover several responsibilities, but each task still needs time allocated to it.

Keep a short decision log. Record what is changing, who agreed it, when it takes effect and what still needs resolving. This helps cover teachers and volunteers follow the same arrangements.

Prepare the records you actually need

Before moving information, check student names, class lists, current contact details and authorised family access. Resolve duplicates and unexplained balances while someone familiar with the existing records can help.

Decide which information belongs in the new system and what will remain in a controlled historical archive. Keep sensitive case records within the arrangements agreed by the responsible lead; do not treat an ordinary notes field as a destination for every document.

If you are moving from another supplier, confirm export access and the exit timetable before cancelling. Check a sample of transferred records against the originals. For fees, reconcile opening balances and payment history rather than assuming a successful upload means the figures are correct.

Review your information-handling arrangements before using real records. Our policy review guide explains the questions to resolve and links to official guidance.

Rehearse a normal teaching session

Give teachers a practical introduction using fictional demonstration records. Let them practise finding a class, taking attendance, recording the learning information you expect and asking for help.

Agree realistic recording deadlines. A teacher supervising a busy class may need a different routine from an administrator working at a desk. Check whether devices, connectivity, text size or shared equipment make the proposed workflow difficult.

A pilot with one class can reveal these problems before a wider launch. Include the people who will actually use the system, including someone who is less confident with technology. Agree what you will check before expanding the pilot.

Tell families before invitations arrive

Use an existing, familiar contact route to explain the change. Tell families what will be available, when access will arrive and what they need to do. Offer help and an alternative way to receive essential information.

Avoid announcing features your madrassa has not prepared. If you are introducing attendance first, explain that progress or fees will follow separately. Keep urgent contact arrangements clear throughout the change.

See how to introduce a new madrassa app to parents for a suggested communication sequence.

Choose a timetable your team can support

The following is an example, not a deadline every madrassa should meet.

Postpone or narrow the launch if essential access is wrong, records are unreliable or support is unavailable. A revised date is easier to manage than an unclear process used across the whole madrassa.

End the previous process deliberately

Name the primary record for new entries and agree when the previous routine ends. If a short overlap is necessary, give it a specific purpose, an owner and an end date. Two complete registers maintained indefinitely create more work and invite disagreement about which is correct.

Stopping new entries in an old system is a separate decision from deleting historical information. Have the responsible person confirm retention arrangements before disposal.

Prepare for an outage too. Staff should know where to find a temporary register, how to keep it secure and who will reconcile entries when access returns.

Review the first month

Ask whether registers are being completed, whether learner access is correct and whether staff are still duplicating work. Follow up privately with families who need help; an unused account does not explain why someone has not signed in.

Choose a few improvements with named owners. Repeat training where needed and adjust routines that do not fit the teaching day. Add further features when the first stage is working consistently.

Support for Makatib.App administrators

Makatib.App includes a private transition starter pack for management accounts. In Admin → Resources → Transition pack, administrators can find editable rollout, staff preparation, family communication and working-practice materials to adapt and approve locally.

For product setup instructions, read Getting started. If you are considering Makatib.App for your madrassa, tell us about your setting.