Start with the operating process
Moving from separate school apps into a connected ERP can improve handovers, but importing inconsistent records will carry old problems into a new interface. Start by defining the authoritative records, responsible employees and reports the institution must preserve.
Inventory active tools, contracts, export formats and dependencies. Identify the data that is still needed, the records that must remain accessible for historical purposes and the information that should not be copied without a clear purpose. Do not begin with a bulk upload of live family or payroll files.
Prepare a staged migration
| Stage | What to do | Acceptance evidence |
|---|---|---|
| Map | Match old fields to the new record model | Reviewed mapping and correction list |
| Trial import | Use synthetic or appropriately authorised test data | Counts and relationships reconcile |
| Permission test | Try staff, branch and parent roles | Unauthorised direct access fails |
| Pilot | Run one agreed workflow with a small group | Exceptions have an owner and resolution |
| Cut-over | Approve timing, backups and rollback | A documented go/no-go decision |
| Review | Compare source and destination reports | Signed-off differences and follow-up actions |
Protect documents and browser storage
Review support access too. A vendor should explain how troubleshooting access is authorised, recorded and removed. Avoid shared administrator accounts that make it impossible to identify who changed a record.
- Use private access controls for student documents and payslips.
- Limit document links by permission and supported expiry controls.
- Confirm what an installed PWA stores on the device.
- Do not cache private records or salary documents in a general offline cache.
- Remove access promptly when staff responsibilities change.
Prove recovery with both records and files
A database backup may not include uploaded documents. Ask which data and storage objects are backed up, how often, where copies are held and who can restore them. Run a restore into an isolated test environment and verify that linked documents still open for the correct authorised users.
Agree recovery objectives with the institution’s operational needs. Keep the rollback plan practical: identify who can pause the rollout, how transactions created during the pilot will be reconciled and what staff should do during an outage.
Roll out released workflows, then expand
Pilot admissions-to-enrolment or a fee-reconciliation cycle before adding more modules. Train staff around the real task and its exception path. A one-off presentation is not enough if employees cannot explain how to correct a mistake safely.
Confirm the release status, supported limits, export options and support terms for every purchased module. Tedusan HR & Payroll and Operations remain coming soon until functional; this migration guide does not imply those modules are available for subscription. A measured rollout protects continuity while the institution improves its processes.
Questions institutions ask
Should a school migrate every record at once?
Usually a staged, reviewed approach is easier to validate. The right sequence depends on data quality, essential workflows, reporting needs and a tested rollback plan.
Is a backup successful if the file exists?
A file alone is not enough evidence. Test restoration of the database and uploaded documents in an isolated environment and verify record relationships and access.
Editorial note: This is a practical workflow guide. Examples are illustrative, not customer results. Product availability and institution-specific requirements must be confirmed separately.
← Back to all articles