Switching from SchoolMessenger: module by module
SchoolMessenger is rarely one product in a district. It is four or five modules bought at different times, sometimes on different terms, often inside a wider PowerSchool relationship. That means the first task is not choosing a replacement. It is establishing what you actually license, when each part renews, and which of it you are genuinely able to leave this year.
| Module | What districts license it for | What typically exports | What typically has no export path | Replaceable by a comms platform? |
|---|---|---|---|---|
| Broadcast notification | Mass SMS, email and voice to households | Contact lists, message history, delivery outcomes | Recorded voice audio; some report views | Yes, for routine sends |
| Emergency notification | Alerting with escalation and priority routing | Templates and contact groups | Escalation configuration and any priority routing logic | Not by Kastr — see below |
| Attendance calling | Automated same-day absence calls | Call logs and outcomes | The rule configuration that triggers the calls | Only if you accept manual sends |
| Teacher and classroom messaging | Staff-to-family threads | Message history where district-governed | Threads created under personal accounts | Yes |
| Website CMS | District and school sites | Content as files, usually messy | Templates, layouts, embedded components | No — different product category |
| Forms and permission slips | Digital forms, sometimes with signature | Submitted responses as CSV | Form definitions and conditional logic | Depends on your requirement |
| Custom voice recordings | Recorded scripts for recurring calls | Sometimes downloadable | Frequently not retrievable in usable audio | Re-record rather than migrate |
| Reporting and analytics | Delivery and engagement reporting | Exported report files | Saved report definitions and historical dashboards | Different reporting model entirely |
The column that decides your project plan is the fourth. Configuration — escalation rules, calling rules, form logic, report definitions — is almost never exportable anywhere in this category, from any vendor. Budget to rebuild it, and take screenshots of every configuration screen while you still have access, because those screenshots are the only specification you will have.
Find the notice date before anything else
Multi-year terms with auto-renewal are normal here, and the notice window frequently closes long before a district's budget conversation begins. Three checks, in this order:
- Which agreement governs each module? Modules bought in different years may sit on different terms with different end dates, or may have been consolidated into a master agreement at some point. Get every executed document, not just the most recent order form.
- What is the notice period, and when does the window open and close? Write both dates down. Add a decision date sixty days before the window opens, because that is when you need alternatives in hand rather than opinions.
- Is there a vendor obligation to notify you? Frequently not. Assume the calendar is entirely your responsibility.
If the window has closed for this cycle, that is not a failure — it is a planning input. Use the extra year properly: run the evaluation without deadline pressure, negotiate the next agreement with alternatives already priced, and fix the notice-window clause when you sign, so the same thing does not happen again.
Partial replacement, which is usually the right answer
You do not have to replace all of it. Districts routinely retain one module and replace the rest, and where the retained module is emergency notification, that is often the correct architecture rather than a compromise.
- Keep emergency, replace routine. The most common split, and the most defensible. Emergency notification has requirements — escalation, priority routing, tested delivery at scale — that routine communications platforms do not meet.
- Keep the website, replace comms. Web platforms have long capital cycles and moving one mid-cycle wastes the last redesign. Let the website reach its natural replacement point.
- Replace everything. Cleanest, and the right answer where the bundle is the problem, but be honest that you are running three migrations at once and staff will feel all three.
Two costs of a partial split that should be planned rather than absorbed: two systems maintaining contact data, which must be resolved by making one authoritative and the other downstream; and two answers to a records request, with retention rules that may not match.
Emergency notification: the honest recommendation
If your district relies on SchoolMessenger for emergency notification, read this before you shortlist us.
Kastr does not replace an emergency notification module. There is no emergency console. There is no two-person authorisation. We publish no delivery-time figure for a full-district send, no load-test result and no uptime history, because we are pre-launch and have no production operating history to compute any of them from. What exists is an emergency flag on a broadcast that genuinely bypasses per-family channel preferences and quiet hours, gated on a capability, and that is a smaller thing than a purpose-built alerting product.
The recommendation that follows is inconvenient for us and correct for you: keep a dedicated emergency notification capability, either by retaining that SchoolMessenger module or by procuring a specialist, and replace routine communications separately. A district that consolidates emergency alerting into a general-purpose messaging platform to save a line item is making a trade that is invisible until the day it is not.
What we would replace well. Routine district and school communication: broadcasts across SMS, email and voice with SMS-to-voice failover on terminal failure, quiet hours defaulting to 21:00–07:00, two-way messaging, DeepL-powered translation you can preview before sending, a cost-and-reach estimate before you send, send-test-to-me, scheduling with the audience resolved at send time rather than schedule time, a 28-endpoint REST API with signed webhooks and an MIT-licensed CLI and MCP server, and a SHA-256 hash-chained append-only audit log for every send. At $3.50, $3.25 or $3.00 per student per year by enrolment band, one tier, everything included, fixed 36 months. And the gaps, again: no SSO, no attachments, no push notifications, no native SIS connectors, no SOC 2, no grade or school audience targeting, and no district references.
Questions people actually ask
Can we export historical message logs from SchoolMessenger?
Message history and delivery outcomes generally export, sometimes self-serve and sometimes by support request. What tends not to come out is configuration — escalation rules, calling rules, saved report definitions — and recorded voice audio in a usable format. Request everything in writing while the contract is live, and screenshot every configuration screen before access ends.
When do we have to give notice to avoid auto-renewal?
It is defined in your agreement, commonly thirty to ninety days before the term ends, and modules bought in different years may sit on different dates. Collect every executed document, write down when each notice window opens and closes, and add a decision date sixty days before the earliest one. In most agreements the vendor has no obligation to remind you.
Can we replace only part of SchoolMessenger and keep the rest?
Yes, and it is often the right answer — particularly keeping emergency notification while replacing routine communications, or keeping the website until its natural replacement point. The two costs to plan for are two systems holding contact data, which needs one to be authoritative and the other downstream, and two systems to search for a records request.
Does Kastr replace SchoolMessenger's emergency notification module?
No. We have no emergency console, no two-person authorisation, and we publish no delivery-time, load-test or uptime figures because we are pre-launch. We have an emergency flag that bypasses family channel preferences and quiet hours, which is not the same product. Keep a dedicated emergency capability and replace routine communications separately.
One price. Every feature. Locked for three years.
$3.50 per student per year under 5,000 students. No tiers, no add-on modules, no per-message fees. Published on the site because you should not have to book a call to learn a price.