Updating EduPrime & release notes
EduPrime improves over time with new features and fixes. Upgrades should be planned, tested and verified — never applied blind to a live system during school hours. This page explains how upgrades work and what to check afterwards.
How upgrades work
An upgrade updates the EduPrime apps to a newer version. The platform applies any data changes the new version needs (new fields, adjusted views) automatically when the apps are updated. Your data is preserved; the apps' code and structures are what change.
| Step | What happens |
|---|---|
| New version deployed | The updated app code is placed on the server |
| Apps updated | EduPrime applies schema and data migrations for the new version |
| Verification | You confirm the system still works as expected |
Before you upgrade
- Take a fresh full backup and confirm it downloaded.
- Restore that backup as a test database.
- Apply the upgrade to the test database first.
- Walk the key workflows there (below) before touching live.
- Schedule the live upgrade for a low-traffic window (evening/weekend) and tell staff.
What to check after an upgrade
Do not assume success because the upgrade finished without an error. Click the real workflows:
- Login — staff, a parent portal user and a student all sign in.
- Academic — open a student, take attendance, enter a grade.
- Fees — raise an invoice and run a test payment end to end.
- Admissions — move an application through a stage.
- Reports — print a report card and a fee statement; confirm branding is intact.
- Integrations — send a test email and SMS; confirm a payment callback works.
Where release notes live
Each EduPrime release is described in its release notes — what changed, what is new, and anything that needs an administrator's attention after upgrading. Read them before upgrading so you know what to test and whether any new configuration is required. The version of each installed app is visible in the App drawer under Apps, which tells you whether an update is available.