Before configuration
- Nominate the school implementation coordinator
- Confirm academic year, classes, sections, subjects and departments
- Document key approval and operational workflows
- List the current data sources and file formats
- Agree which historical data is genuinely required
Before migration
- Prepare current student and staff master data
- Check duplicates and missing identifiers
- Confirm fee structures and active student fee plans
- Confirm parent/guardian mappings where required
- Agree how unsupported or paper-only data will be handled
Before training
- Create the required user roles
- Assign relevant responsibilities and access
- Validate sample student, staff and fee records
- Confirm the first workflows that will go live
- Prepare role-specific training scenarios
Before go-live
- Complete management readiness review
- Verify critical totals and records
- Confirm support contacts and issue-reporting process
- Decide whether a temporary parallel run is required
- Communicate the go-live plan to staff
After go-live
- Review early user issues
- Correct configuration or data issues quickly
- Collect feedback from management and key users
- Fine-tune agreed workflows
- Confirm when legacy manual processes can be retired
See how this works in StudentsOrbit
We can demonstrate the relevant workflow using your institution's structure and discuss how implementation can be adapted around genuine operational requirements.
Request a Personalized Demo
Considering a change from Excel, registers or another system?
We can discuss migration, configuration and a phased go-live before you decide.
See implementation approach →