Things to know before you start using myschool
Key advice on learning, phased rollout, and the most common mistakes to avoid when starting with the system.
Read this before you start — it will save you time and help you avoid common mistakes.

1. Learning and training
- Learning myschool properly takes at least one to two weeks of regular use. Assign a team member to focus on this phase and read the preparation articles before going live.
- Test on the demo version before working on your live instance. You can request one through our contact page.
2. Implementation
- Roll out in phases over several weeks, not days. Start with core modules such as News and Calendar, then move to Fees and Exams.
- Appoint at least one administrator who knows the system well and can guide other users.
- Review the process flow before implementing to understand the correct order.
3. Common mistakes and questions
- The logo must be exactly 150 px wide × 110 px high to avoid blurring or cropping.
- Never delete the default admin user before creating a replacement admin account, and keep the account’s email correct for password recovery.
- SMS requires a bulk SMS API from a local provider connected to the system.
- Email depends on completing the SMTP settings from your email provider.
- Use the demo for testing; avoid testing on your live instance, where deleting data later can cause problems.
- To access the system through your own domain, add a CNAME record pointing to the myschool server.
- Import files must be saved as CSV only, with mandatory fields in the recommended format.
- Do not install third-party applications on the same server; host them separately and integrate them.
4. Hosting, support and customisation
- We recommend myschool cloud hosting for the best performance and support.
- Self-hosting requires solid server administration knowledge.
- Support cannot be provided if the source code or database has been altered without coordinating with the myschool team.
- New feature requests are reviewed before being added — send your suggestions to our support team.
- Custom changes beyond the standard features may involve additional hosting and maintenance costs.
- When asking for support, include a clear description of the problem and screenshots to speed things up.
Was this article helpful?
Thanks for your feedback!