Never skip the pilot
A small, representative cohort reveals mapping and permission problems while recovery is still simple.
Implementation guide
School data migration and deduplication
Move student, guardian, class, fee, and staff data into a clean operating model before inviting the whole school. See the workflow, ownership, rollout sequence, and boundaries before choosing a school management platform.
At a glance
A useful page should answer the next operational question
Move student, guardian, class, fee, and staff data into a clean operating model before inviting the whole school.
Who this is for
- Registrars
- IT coordinators
- Finance teams
Start with the evidence
Use the linked product and documentation pages to validate the workflow against your school’s data, roles, policies, and deployment.
Read the supporting materialHow it works
Follow the handoffs, not just the feature list
A clear sequence makes ownership, exceptions, and the next system action visible.
- 01
Inventory
List every source, owner, export format, date range, and sensitive field.
- 02
Define identity
Choose the authoritative student, guardian, staff, and vendor identifiers before mapping columns.
- 03
Clean
Resolve duplicates, inactive records, missing class placement, and contradictory contact details.
- 04
Reconcile
Import a pilot cohort and compare counts, balances, links, and reports with the source.
Practical artifact
Leave with something your team can use
Copy these checkpoints into a kickoff, vendor demo, or readiness review.
- Source-system inventory
- Student identity rules
- Guardian-link review
- Reconciliation sign-off
Product truth
What to verify before rollout
Good school software copy should answer who owns the work, what the handoff produces, and which parts still depend on deployment decisions.
Available now
Capability status
This page describes the supported workflow boundary. Confirm configuration, integrations, data, and policy requirements in a representative pilot before committing to production.
Teams in the workflow
- Registrars
- IT coordinators
- Finance teams
Deep dive
Decisions, handoffs, and boundaries
Use these details to turn a product page into an implementation conversation.
Success measure
The migrated record should support one complete workflow without a second manual identity lookup.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Questions, answered
Straightforward answers for visitors evaluating the product.
Can we import everything at once?+
A staged import is safer. Start with foundation records, reconcile, then add dependent modules.
Who approves the data?+
Assign an owner for each domain; registrars, finance, HR, and IT should sign off their own records.
Continue exploring
Related planning and product pages
Follow the next link based on the question your team needs to answer.
Admissions to enrollment
Move an applicant from public application through review, offer acceptance, and live student enrollment without retyping the record.
Read the pageSchool data migration checklist generator
Generate a migration checklist for student, guardian, staff, class, fee, and vendor data with reconciliation owners.
Read the page
Turn the page into a rollout conversation
We can walk through the workflow with your school’s roles, calendar, data, and first-term priorities.
Already using Schoolyi? Sign in