SCHOOL MANAGEMENT · DATA TRANSITION
How Much School Data Should You Migrate to a New ERP?
Decide which school records merit migration by balancing operational need, data quality, history, privacy and provider-supported scope.
Conceptual product view · no customer records or performance figures
THE SHORT ANSWER
Migrate the information needed for current operations, continuity and approved reporting—not every file the school has ever collected. Assess each data set by purpose, accuracy, age, sensitivity and cost to clean. Confirm provider-supported fields and formats, then reconcile a representative sample and document what remains in an authorised archive.
01 / OPERATIONAL NEED
Start with the work the school must perform after go-live.
List the active records staff need to support admissions, current learners, fees, attendance and other in-scope workflows. Ask what information is needed to make a correct decision or maintain continuity in the next academic period.
Do not migrate a field only because it exists in an old spreadsheet. If no role can explain its current purpose, pause and determine whether it belongs in the new system at all.
02 / HISTORICAL CONTEXT
Choose a useful look-back period and preserve older evidence appropriately.
Some history supports current operations or a defined review; older data may be needed only for reference. Determine the period each record owner needs and whether a controlled archive is more suitable than loading every past year into the new workflow.
Confirm how staff will retrieve archived information and who is permitted to access it. An archive still needs ownership, security and retention rules.
03 / QUALITY & COST
Balance usefulness against the effort required to make data reliable.
Older records may have inconsistent identifiers, missing values or duplicate rows. Estimate the time needed to correct and verify them, and compare that effort with the operational value of bringing them forward.
Do not let a large quantity of uncertain data weaken a clean launch. Keep unresolved records in a controlled exception process and agree whether they should be corrected, archived or excluded.
04 / SENSITIVITY & RETENTION
Treat migration as a data-governance decision, not just a technical task.
Identify sensitive learner, family, staff and financial fields. Confirm that the school has an appropriate purpose and authority to move each category, that access is limited and that the retention period is understood.
Do not copy personal notes or documents into the new system by default. Seek institutional privacy guidance for uncertain or sensitive categories and document exclusions.
05 / PROVIDER BOUNDARY
Verify which fields, relationships and formats the new product accepts.
Ask the provider about supported import formats, mapping, file size or volume limits, linked records, attachments, validation and any charges. Clarify which work the provider performs and which cleanup remains the school’s responsibility.
A spreadsheet upload does not necessarily preserve formulas, history, document links or relationships between records. Get a sample migration and its limitations in writing.
06 / APPROVE THE BOUNDARY
Sign off the scope and test that staff can use the resulting records.
Review the proposed set with data owners and representative users. Reconcile counts and sampled values after transfer, then test the workflows that depend on those records before authorising the cut-over.
Maintain an exclusions list and a source-retention decision. This gives the school a clear account of what was moved, why it was selected and where other approved information remains.
A FIELD GUIDE FOR YOUR TEAM
A migration-scope decision
Use this to decide what should move, what should remain accessible elsewhere and what may no longer need to be retained.
| Lens | Question to ask | What to record |
|---|---|---|
| OPERATIONAL NEED | Start with the work the school must perform after go-live. | A record list tied to an identified post-launch task. |
| HISTORICAL CONTEXT | Choose a useful look-back period and preserve older evidence appropriately. | A migration period and an access-controlled archive plan. |
| QUALITY & COST | Balance usefulness against the effort required to make data reliable. | A quality rating and cleanup estimate for each candidate data set. |
| SENSITIVITY & RETENTION | Treat migration as a data-governance decision, not just a technical task. | A sensitivity review and an approved purpose for every migrated category. |
| PROVIDER BOUNDARY | Verify which fields, relationships and formats the new product accepts. | A provider-confirmed field map and migration scope. |
| APPROVE THE BOUNDARY | Sign off the scope and test that staff can use the resulting records. | A signed migration boundary, reconciliation and source disposition. |
CODEPEX IN CONTEXT
Useful guidance begins with clear scope.
Migration fields, historic depth, attachments, formats and provider services must be confirmed for the specific School ERP implementation. The school owns retention decisions, source accuracy and approval to migrate sensitive records.
Product-specific statements are based on the current owner-controlled capability declaration. Ask CodePex to confirm any institution-specific configuration or unlisted requirement.