How to Migrate Your Student Database to Femlify

The single question that stops more schools from switching to a better management system than any other is not about price, features, or support. It is this: "What happens to all our data?"

It is a fair question. A school that has been operating for ten years has registration records for hundreds of students, contact information for every parent, historical results from multiple sessions, and staff records built up over time. The thought of losing any of it — or spending weeks re-entering it — is enough to make any administrator decide that the current system, however frustrating, is at least known.

The good news is that migrating your student database to Femlify does not require throwing away what you have or starting over from scratch. It requires a structured process: understanding which data to move, preparing it in the right format, importing it correctly, and verifying that everything landed accurately. Done properly, a school with 300 students can complete a full migration in a working day — and most of that time is in preparation, not in the actual import.

This guide walks you through every step.

What Data Needs to Be Migrated

Before touching a spreadsheet or opening Femlify, sit down and make a list of what your school actually needs to carry forward. Not everything from your old system is worth migrating — and trying to migrate everything at once makes the process harder than it needs to be.

Priority 1 — Active student records. These are the students currently enrolled in your school. They need to exist in Femlify before you can do anything else — take attendance, enter scores, generate invoices, or produce report cards. This is the data migration that must happen before the first day of using the new system operationally.

For each active student, the essential fields are:

• Full name (first, middle, last)
• Registration ID
• Gender
• Date of birth
• Email address (if they have one)
• Guardian / parent contact information

Femlify also supports additional fields — nationality, residential address, state and LGA of origin — but these can be filled in over time if they are not immediately available in your existing records.

Priority 2 — Parent and guardian records. If your school has parent contact information in your current system, migrate it alongside or immediately after student records. Femlify supports "Import Students with Parents" in a single operation, linking each student to their guardian record automatically.

Priority 3 — Staff records. Your teaching and administrative staff need accounts in Femlify before term operations can begin. Staff records are simpler than student records — the required fields are name, email address, and role.

Priority 4 — Historical results (optional). Previous terms' scores and report cards are useful for reference but are not operationally required for the current term. They can be migrated after the core system is running, or kept in your old system as an archive. Many schools choose to store historical PDFs of old report cards rather than re-entering raw scores.

A successful migration is not about moving everything at once — it is about identifying what you need for day one operations and getting that right before worrying about historical data.

How to Export Data from Your Current System

Your current student records are probably in one of three places: a spreadsheet, an older local school management software, or physical registers.

If your data is in a spreadsheet (most common) Open your master student spreadsheet and identify the columns you need. Most Nigerian school spreadsheets have columns for student name, class, gender, and parent contact at minimum. Some also have registration IDs, dates of birth, and addresses. Make a note of exactly which columns exist and which are empty or inconsistently filled — you will need to fill gaps before importing.

Export the spreadsheet as a CSV file (File → Save As → CSV) or keep it as XLSX. Both formats are supported by Femlify's bulk import.

If your data is in an older school management application Look for an Export or Download function in your current software. Most school management applications — even older local ones — have some form of data export, usually to Excel or CSV. If the application does not have an export function, check whether data can be copied from the reports module. As a last resort, you can manually copy visible records into a spreadsheet.

If your data is in paper registers This is the most time-consuming scenario. You will need to manually enter student records into a spreadsheet before importing. Focus on the essential fields first — name, registration ID, gender — and do not let the incompleteness of some records block you from migrating what you do have. Incomplete records can be updated in Femlify after import; they do not need to be perfect before import.

No matter where your current data lives, the preparation step is always the same: get it into a clean spreadsheet with consistent columns before touching the import tool.

How to Format Data for Femlify Import

Femlify's bulk import is designed to be straightforward, but the data must be in the expected format before uploading. The most reliable way to get this right is to use the official import template.

Download the template first. In Femlify, go to Users → Students, click the Bulk Import dropdown, and select either "Import Students Only" or "Import Students with Parents." In the import modal, click Download Template. This gives you a CSV or Excel file with the exact column headers Femlify expects — in the correct order, with the correct names.

Map your existing data to the template columns. Open both your existing spreadsheet and the downloaded template side by side. Copy your data column by column into the template, matching your column names to the template's headers. Common mappings:

• "Student Name" or "Full Name" → split into first_name, middle_name, last_name
• "Reg No" or "Admission No" → registration_id
• "M/F" or "Sex" → gender (use "male" / "female" / "other" as values)
• "DOB" → date_of_birth (use YYYY-MM-DD format: 2015-03-22)
• "Parent Phone" → map to the guardian phone field in the template

Clean the data as you map. This is the most important preparation step. Look for:

• Name inconsistencies — "Adewale" in one row, "adewale" in another
• Gender values that are not "male," "female," or "other"
• Date of birth formats that are inconsistent (some as DD/MM/YYYY, others as text like "March 22, 2015")
• Registration IDs with leading zeros that Excel may have stripped
• Blank rows in the middle of the sheet

None of these will cause a catastrophic import failure, but they will create records that need manual correction after import. Cleaning them before uploading saves time on the back end.

For "Import Students with Parents," the template includes additional columns for guardian name, email, phone, and gender. Fill these in the same rows as the student data — each row represents one student and their linked guardian.

The quality of your import is determined entirely by the quality of your spreadsheet — spend one extra hour cleaning your data before uploading and you will save three hours of post-import corrections.

The Step-by-Step Import Process in Femlify

Once your data is in the template and cleaned, the import itself is quick.

Step 1. Go to Users → Students in Femlify.

Step 2. Click the Bulk Import dropdown in the top-right corner. Select Import Students Only if you are importing students without parent records, or Import Students with Parents if your template includes guardian information.

Step 3. In the import modal, click the file upload area or drag your filled template file into it. Femlify accepts .CSV, .XLSX, and .XLS formats.

Step 4. Click Start Import. Femlify processes your file and creates student records for every row. Depending on the number of rows, this typically completes within seconds to a few minutes for large datasets.

Step 5. Review any import errors. If rows failed — for example, a registration ID that duplicates an existing record, or a required field left blank — Femlify will flag them. Note the errors, correct them in your spreadsheet, and re-import only the failed rows.

Step 6. Repeat for staff records using Users → Staff → Bulk Import, and for guardian records separately if you did not use the combined import.

How to Verify Data After Migration

Once the import is complete, do not assume everything is correct. Set aside time — an hour at minimum, more for larger schools — to verify the imported data before going live.

Check record counts first. Your old system should show a total student count. Femlify's student list shows Total Students, Male Students, Female Students, and New (30 days). If the total in Femlify does not match your source, find the gap — either rows failed silently, there are duplicates, or your source count was itself inaccurate.

Spot-check individual records. Select ten to fifteen students at random — distribute them across class levels and both genders — and open each profile in Femlify. Compare name spelling, registration ID, date of birth, and gender against your source. If you find errors in your sample, the error rate across the full dataset is likely similar and worth a systematic review.

Check for duplicates. If your old system had inconsistent registration IDs, or if staff ran the import twice accidentally, duplicate records may have been created. Search for students with common names and verify that each appears only once.

Verify guardian links. If you used "Import Students with Parents," check that guardian records have been created and linked correctly. Open a sample of student profiles and confirm that the linked guardian name and phone number match your source data.

Fill in missing fields. For records where non-essential fields were blank in your source — addresses, nationalities, alternate phone numbers — assign a staff member to complete these over the first few weeks of the new term rather than delaying the migration for perfect data.

Verification is not optional — it is the step that converts a data migration from a hope into a confirmed fact.

What to Do with Historical Results and Records

Historical results — scores and report cards from previous terms and sessions — require a separate decision from active student records.

Option 1 — Keep them in your old system as a read-only archive. Many schools take this approach. The old system is kept running but no new data is entered into it. Staff who need to reference old results log into the legacy system. Femlify handles all current and future operations. This is the lowest-risk approach and requires no additional migration work.

Option 2 — Store historical report cards as PDFs. If your old system can export report cards as PDF files, generate and save a PDF for every student's previous results before decommissioning the old system. Store these in a cloud folder organised by session and term. When a parent asks for a historical result, you can retrieve the PDF in seconds.

Option 3 — Re-enter historical scores in Femlify. This is the most complete approach but also the most time-consuming. If historical scores are available in a structured format (a spreadsheet per subject per term), they can be entered into Femlify's score entry interface for historical terms. This gives you a fully unified academic history in one system. It is worth considering for schools that want to produce cumulative session reports from Femlify in the future.

For most Nigerian schools switching from spreadsheets or basic local software, Option 2 is the most practical: PDF-archive the old results, import active student records into Femlify, and start the current session cleanly in the new system.

Conclusion

Migrating your student database to Femlify is not a technical project — it is a data preparation project. The import tools are simple and built for school administrators, not IT professionals. What determines success is the quality of the data you bring to the import: consistent columns, clean values, correct formats, and a complete record of every active student.

Give yourself a week before the new term begins. Spend the first three days exporting and cleaning your data. Spend the fourth day running the import and verifying the results. Spend the fifth day enrolling students into the current term and confirming that teachers can see their class lists. By the first day of resumption, your school is running on Femlify — with every active student record intact and every staff member set up with the right access.

The data you have built over years is an asset. A structured migration makes sure it moves with you.

Frequently Asked Questions

Will I lose my student data when I switch to Femlify?

No. Switching to Femlify does not delete or overwrite any data from your existing system. Your old system remains intact while you run the import in Femlify. Student records are created fresh in Femlify from your import file. Only when you have verified the migrated data and confirmed it is complete should you consider decommissioning or archiving your old system.

What file format does Femlify accept for student import?

Femlify's bulk import accepts CSV, XLSX, and XLS files. The most reliable approach is to download the official import template from the bulk import modal, fill it in with your student data, and upload the completed template. The template uses the exact column headers Femlify expects — removing guesswork about field names, data types, and required vs optional fields.

What happens if some students are missing from the import?

Check the import results screen for error rows — Femlify flags records that failed due to missing required fields, duplicate registration IDs, or invalid data formats. Correct the failed rows in your spreadsheet and re-run the import for only those rows. You can also add missing students individually using the New Student form, which is useful for small numbers of records that need manual attention.