Guides

How to Migrate Nursery Data to New Software: A 7-Step Plan

You are convinced you need a system, but one worry holds you back: how will I move all this data? It can be organised into clear steps, and most problems are prevented before they start. A practical plan with checklists, for Egypt and Saudi Arabia.

By The Takwen team9 min read
How to Migrate Nursery Data to New Software: A 7-Step Plan

You are convinced your nursery needs a system, but something holds you back: how will I move all this data? The worry is understandable. Children's, parents' and fee data are the nursery's memory, and a mistake in moving them can mean a wrong invoice, a missing phone number or a child with no allergy recorded. The good news is that you can organise the move to migrate nursery data to new software into clear steps, and that most problems are prevented before they start. This guide gives a practical plan with checklists and examples from nurseries in Egypt and Saudi Arabia.

What do we mean by migrating nursery data?

It is the process of gathering information scattered across registers, Excel files and staff phones and entering it, organised, into a new system, while checking that it is correct and complete. It usually covers children's files, details of parents and authorised pick-up persons, health information, classes, fee schedules and balances, and staff records. It does not mean moving every record you own; some of it is archived outside the system.

What are the seven steps to move data without loss?

1. List your data sources

Write down every place you keep information: the enrolment register, the fees file, WhatsApp lists, the staff file, paper child files, even photos of receipts on phones. Any source you forget will return later as a surprise.

2. Decide what to move and what to archive

Do not move everything. Use this table:

Type of data

Decision

Reason

Current children

Move

The basis of operations

Graduated children

Archive, or move with a "former" status

Depends on your need for contact or statistics

Parents and authorised persons

Move

Essential for safety and contact

Allergies and medication

Move and confirm with parents

The most important safety data

Current fee balances

Move

The basis of accounting

Old payment history

Archive

Usually no operational value

Current staff

Move

For permissions and payroll

Signed papers

Scan and attach

A legal reference

3. Clean the data

This is the longest stage and the most valuable. Do the following:

  • Unify how names are written (remove repeated titles and extra spaces).

  • Correct phone numbers and add the country code (+20 for Egypt, +966 for Saudi Arabia), because many systems use the mobile number as the identity.

  • Look for duplicates: a child entered twice, or two siblings under separate accounts for one parent.

  • Fix the date format and check dates of birth.

  • Fill in the gaps: an authorised person, blood type, allergy, an emergency contact.

4. Prepare the import file

Systems usually ask for an Excel or CSV file with specific columns. Ask the vendor for the template and map your columns to it. Give each child a unique ID, and link siblings to one parent. Keep an untouched original and work on a copy.

5. Test with a small batch

Import one class or ten children first. Open their records in the system and compare them with the original: names, phones, fees, allergies. Any error you find here saves you correcting hundreds of records later.

6. Verify before rolling out

After importing all the children, check using totals: the number of children in each class, the total of fees due, the number of late payers. Compare them with the old system. If they match, the data has moved safely. If they differ, find the gap at once.

7. Run in parallel, then stop the old one

Work with both systems for two weeks: attendance is recorded in the new and the old, and invoices are issued from the new one and compared with the old. After that, set an announced date to stop the old one. Keeping both for months doubles the work and distracts the team.

How long does it take, and what timetable works?

The table below is an example for a medium nursery (the weeks are approximate and change with the size of your data):

Week

Task

Output

1

List sources and clean the data

A clean children and parents file

2

Prepare the import template and test one class

A correct trial class

3

Import everyone, verify and train teachers

A ready system with matching totals

4

Run in parallel with the old register

Errors logged and fixed

5

Stop the old one and tell parents

The system is the only reference

You do not need to follow this literally. A small nursery may finish in two weeks, and a branch network may move one branch at a time over months. What matters is that you have an announced end date.

Which fields must a migrated child record have?

Before importing, make sure every child has at least the following, or the record will be incomplete just when you need it in a critical moment:

  • Full name, date of birth and class.

  • At least one parent with a correct mobile number that is active on WhatsApp.

  • At least two people authorised to collect, with names and numbers.

  • An emergency contact other than the parent.

  • Food and medication allergies and any chronic health condition, even if "none" is confirmed by the parents.

  • The fee amount, the payment method and any agreed discounts.

If some data is missing, treat that as a reason for organised contact with parents: a message asking them to update the details, then follow-up for those who do not reply. It is a chance to improve your records, not only an obstacle. For the record structure itself, see our guide to child records in nursery.

How do you handle local details in Egypt and Saudi Arabia?

  • Phone numbers: use the international format (+20 or +966) so WhatsApp notices reach the right number.

  • Arabic names: record the full four-part name as on the birth certificate if regulators' files require it.

  • Fees: in Egypt, move the monthly or termly instalment schedule and what has been paid; in Saudi Arabia, move tuition and extra fees, noting VAT if it applies to your nursery according to its status.

  • Carried-forward balances: record them as an opening balance on the go-live date instead of re-entering a whole year of payments.

  • Nationalities and residence: in Saudi Arabia you may need fields for an ID or residence number depending on your establishment's requirements; check that the system supports them.

What mistakes ruin a migration?

  1. Moving before cleaning: importing messy data carries the mess into the new system faster.

  2. No unique ID: relying on names alone causes wrong merges or duplicates.

  3. Forgetting health and authorised-person data: the most important safety data may be missing because it sits on a separate sheet.

  4. No backup: editing the original file directly, then finding a mistake with no way back.

  5. Bad timing: moving during enrolment week, exams or the start of the year confuses the team. A quiet start of month is better.

  6. Ignoring the team: introducing the system without training or explanation creates resistance.

  7. Not telling parents: they are surprised by new notices and take them for nuisance messages.

Who does what on your team?

Assign roles clearly so the process does not become a vague responsibility:

  • Project lead (manager or owner): sets the date, takes decisions and follows progress.

  • Data owner (office staff or accountant): cleans the files, prepares the import template and checks the figures.

  • An ambassador teacher: tries the system early, helps colleagues and passes on their comments.

  • Vendor support: answers import questions and helps with faults.

Give the project fixed hours each week instead of "when we find time"; projects with no schedule drag on for months.

How does Takwen help with the process?

Takwen lets you import children and parents, and your team too, from an Excel or CSV file in three steps: you upload the file, match its columns to the fields (many are recognised automatically), then review errors and warnings before saving, so rows with problems are not imported until you correct them. A template is available to download, the system accepts mobile numbers in any format and birth dates in different formats, links siblings to the same parent number, and can create classes that do not exist yet. You can choose to skip children already in the system or update their details. After the import, the system reports the number of new children, updates and rows not imported. Our team answers on WhatsApp to help in your first week. See the getting started page for the details, and if you are just starting, try Takwen's nursery management software on one class first.

How do you protect privacy while data moves?

During cleaning and import, files containing children's names, parents' numbers and health data travel by email, WhatsApp and personal devices, and that is a fragile moment. Follow simple rules: work on one copy kept in a password-protected place, do not send it into WhatsApp groups, give access only to those who need it, delete temporary copies from phones and the recycle bin once the process ends, and archive the original somewhere safe. If you use an outsider for cleaning, agree in writing on confidentiality and how long they may keep the data. Children's information is a trust, and protecting it is part of parents' confidence in your nursery. For the policy side, see our guide to children's photo consent in nursery.

What do you do after the migration ends?

The process does not end with the import. In the first week, review attendance and invoice reports daily with the team, and note repeated questions to build a short internal guide. In the first month, compare your actual income with what the system shows. After three months, review what the team uses and what it does not, and switch on only one new feature at a time. For a gradual move and the wider plan, read our nursery digital transformation plan, and if you are starting from a spreadsheet, read about the limits of a nursery Excel spreadsheet.

Frequently asked questions

How long does moving nursery data take?

A small nursery can finish in about two weeks, a medium one in four to five, and a branch network may move one branch at a time over months. The longest part is cleaning the data, not importing it. Whatever the size, set an announced date on which the old system stops, otherwise double entry drags on and doubles the work.

Do I need to move all my old records?

No. Move what you operate with: current children, parents and authorised pick-up persons, allergies and medicines, current instalment balances and current staff. Archive old payment histories and graduated children, or bring them in with a past status if you need contact or statistics. Scan signed papers and attach them to the child's record.

What is the safest way to test an import?

Import one class or about ten children first and open their records in the new system. Compare names, phone numbers, fees and allergies with the original file. Any error found at this stage saves correcting hundreds of records later. Only after a clean test should you import everyone and check totals against the old system.

How do I protect privacy while moving the data?

Work on one copy kept in a password-protected place, do not send it through WhatsApp groups, give access only to those who need it, delete temporary copies from phones afterwards, and archive the original safely. If an outside person helps with cleaning, agree in writing on confidentiality and how long they may keep the data.

Import your own Excel file in the trial

Upload children and families from Excel in Takwen, review any errors before saving, and see your data in place during the 14-day free trial.

Start the free trial

Share

About the author

The Takwen team

We write from what we learn working with nurseries every day.

Read next