Guides6 min read

IEMIS Transfer: Moving a Student's Records Between Schools

An IEMIS transfer means moving a student's record between schools in Nepal so they are counted at the right one. Here is the process and how clean records help.

By Niraj Kumar Jha ·

IEMIS Transfer: Moving a Student's Records Between Schools

Key takeaways

  • An IEMIS transfer is about keeping data honest when a student changes schools - old school stops counting them, new school starts.
  • It combines school paperwork (a transfer certificate plus admission) with each school's IEMIS submission reflecting the change.
  • Carrying departed students inflates enrollment, a well-documented data-quality problem that distorts national planning figures.
  • Official steps vary by local level, but the part you control - clean, current records - is what makes every transfer painless.

An IEMIS transfer refers to moving a student's record between schools within Nepal's education data system when that student changes schools - so the child is counted at their new school rather than lingering on the old school's rolls in the Integrated Educational Management Information System (IEMIS) run by CEHRD. In practice it involves two connected things: the paperwork the schools handle directly (a transfer certificate and admission at the new school), and making sure each school's IEMIS submission reflects reality - the leaving school no longer reporting the student, the receiving school now including them. Getting this right keeps enrollment figures accurate on both sides, which matters because those numbers feed real budget and planning decisions.

This guide explains what an IEMIS transfer means, the general process, and why keeping clean records year-round makes it painless. Because official steps and portal mechanics change and vary by local level, treat the process below as a general picture and confirm the exact requirements with your education office.


What "IEMIS Transfer" Actually Means

When a student leaves one school and joins another, two records need to change. The first is the on-the-ground reality: the student stops attending School A and starts at School B. The second is how that reality shows up in data - both schools report their enrollment into IEMIS each year, and if the transfer is not reflected, the student ends up either counted twice (still on School A's rolls while enrolled at School B) or counted at the wrong school.

"IEMIS transfer" is the informal name for making the data catch up with reality. It is less a single button and more a consequence of two schools each keeping their records accurate:

  • The leaving school stops carrying the student as currently enrolled once they have left.
  • The receiving school adds the student to its own records and, at its next submission, reports them.

CEHRD's periodic IEMIS data-update notices do spell out transfer duties - schools are told to transfer outgoing students to their new school, to accept students transferred in from other institutions, and to obtain a transfer certificate carrying the previous school's IEMIS registration number when admitting a student into Grade 2 or above. What changes from cycle to cycle is the deadline, the portal mechanics, and exactly what your local level education office asks to see. Confirm the current cycle's requirements with your education office or CEHRD rather than assuming last year's process is unchanged.


Why Accurate Transfers Matter

It is tempting to treat a departed student as a low-priority cleanup task. It is not. Carrying students who have already left is one of the best-documented data-quality problems in Nepal's education statistics.

CEHRD is explicit about the stakes. Its IEMIS data update and verification notice warns that failing to keep records current can affect the grants a school receives and the facilities its students are entitled to, holds the principal responsible where a school or a student is denied a benefit because the data was incomplete, and notes that deliberately filing misleading information can draw action under the Corruption Prevention Act. This is not a form-filling exercise with no downside for getting it wrong.

The arithmetic is also unforgiving. Every student who has left but is still counted inflates a school's enrollment, and that inflated figure travels up into the district, province, and national totals published in CEHRD's education statistics reports and used to allocate teachers and budgets. A phantom enrollment is not a harmless rounding error - it is a claim on resources that should have gone somewhere else.

So a clean transfer is not bureaucratic tidiness. It is the difference between your school's enrollment reflecting the students actually in your classrooms and reflecting a number nobody reconciled. The full IEMIS guide for Nepal schools covers in depth how a single school's numbers become national planning inputs - and why over-reporting quietly hurts the whole system.


The General Process, Step by Step

Every local level can differ, but a student transfer in Nepal generally involves these moving parts:

  1. The parent or guardian informs the leaving school that the student is moving, and requests a transfer certificate (often called a TC or migration certificate). This document confirms the student attended and has left in good standing. For admission into Grade 2 or above, CEHRD expects that certificate to carry the previous school's IEMIS registration number, so the receiving school can tie the new admission to an existing record rather than creating a duplicate one.
  2. The leaving school issues the transfer certificate and updates its own records to mark the student as departed - no longer currently enrolled.
  3. The receiving school admits the student, using the transfer certificate and prior academic records to place them in the correct grade.
  4. Each school's records feed its IEMIS submission. At the next reporting cycle, the leaving school no longer reports the student, and the receiving school does. If the data systems on both sides are current, this step is automatic rather than a special task.
  5. Any identifiers move with the student where applicable. The IEMIS number and related record identifiers exist precisely so a student's history can be kept coherent across a move; CEHRD's guidance to schools and local levels is to reconcile these records rather than re-register the student from scratch. When in doubt about which identifier applies, ask the education office.

The single biggest determinant of how smooth this is: whether both schools kept accurate records in the first place. A leaving school that never marked the student as departed creates a phantom enrollment; a receiving school with messy admission records struggles to place the student correctly.


Where Clean Records Make This Painless

The schools that handle transfers without friction share one habit: they update a student's status the week it changes, not months later under deadline pressure. When a student leaves, that is recorded immediately; when one arrives, they are admitted into a single clean profile rather than retyped into three different sheets.

This is exactly what a proper student information system is for. Instead of an admission register, a class-teacher spreadsheet, and a fee ledger that each carry their own version of the student, there is one profile per student that every module reads from. When that student transfers out, marking them departed updates the record everywhere at once - so they do not silently persist as a phantom enrollment that inflates next year's IEMIS numbers.

The same system is what makes issuing a transfer certificate a quick task rather than a scramble. A school that already holds the student's admission details, attendance history, and academic record in one place can generate the certificate from existing data. A school reconstructing that history from scattered files spends a morning on what should take minutes.

A transfer certificate and clean internal records help your school, but they do not replace the official process your local education office runs. Confirm what the receiving school and your education office require - documentation, timing, and how the departure should be reflected - before treating a transfer as complete.


What Software Does and Does Not Do Here

Being honest about the boundary matters. No school management platform, Gurukul included, submits directly into CEHRD's IEMIS portal or performs an official transfer on the government's behalf - that upload and the official transfer process stay human tasks handled by your school and education office.

What good software does change is everything upstream. It keeps one accurate record per student, marks departures the day they happen so phantom enrollments never build up, produces transfer certificates and academic records from data you already hold, and lets you pull current, reconciled enrollment whenever you need it. When IEMIS season arrives, the transfers that happened all year are already reflected - you are reading accurate numbers, not hunting for who actually left.

If the terminology around all this still feels fuzzy, the IEMIS full form and meaning explainer covers what the system is and who runs it, which makes the transfer picture easier to place.


The Bottom Line

An IEMIS transfer is really about keeping data honest when a student changes schools - the leaving school stops counting them, the receiving school starts, and the paperwork (a transfer certificate plus admission) connects the two. Done well, it prevents the phantom enrollments that inflate Nepal's education statistics. The process varies by local level, so confirm the official steps with your education office - but the part within your control, clean and current records, is what makes every transfer painless whether it happens in Shrawan or the middle of the year.

Gurukul keeps each student on one clean profile - admissions, records, transfer certificates, and departures all in one place - so transfers stay accurate and IEMIS season stays calm. See the platform or book a free demo.

Frequently asked questions

It refers to moving a student's record between schools when they change schools, so the child is counted at their new school instead of lingering on the old school's rolls in Nepal's IEMIS data system. It involves both the transfer paperwork and each school's data reflecting the change.

Generally the parent requests a transfer certificate from the leaving school, the leaving school issues it and marks the student departed, the receiving school admits the student, and each school's next IEMIS submission reflects the change. Exact steps vary by local level, so confirm with your education office.

Carrying students who have already left inflates a school's enrollment, and that error travels up into district and national totals used to allocate teachers and budgets. A clean transfer keeps both schools' numbers honest.

Gurukul

Run your school without the spreadsheets.

Attendance, fees, exams, reports - one platform built for Nepal. Book a free 30-minute demo and see it on your school's data.

Written by

Niraj Kumar Jha

Niraj Kumar Jha

Founder, Gurukul

Building Gurukul - the school management platform built for the real world. Spent years watching Nepal's schools run on Excel and WhatsApp, then decided to do something about it. Full-stack engineer working across database architecture, AI integration, and frontend delivery, and he writes these guides from what schools actually deal with day to day.

Last updated August 16, 2026