School Management · Planning
Prepare school data for a digital management system
Do not upload or send sensitive school data until the deployment, data-handling process and current product scope are approved. This guide covers preparation only.
Updated
Identify authoritative sources
Decide which admission, fee, class and academic records are the official source. Avoid merging uncontrolled copies without review.
Clean identity and relationships
Standardize learner names, admission numbers, status, class placement and parent or guardian relationships. Resolve duplicates through an approved process.
Define academic and fee structures
Prepare academic years, terms, classes, streams, subjects, fee items and opening balances only after their owners confirm them.
Minimize sensitive migration data
Include only data needed for the agreed implementation. Keep discipline, health or other sensitive records out unless the approved scope and permissions require them.
Wait for a verified import process
Use only the ZidiCore-approved template or administrative operation after current School Management availability is confirmed.
Before you finish
- The school approved the source and scope.
- Duplicates and invalid identifiers are resolved.
- Sensitive data is minimized.
- No data has been sent to an unverified destination.
Still need help?
Account-specific problems should be handled through an authenticated support ticket so the team can identify the correct organization and application.