Seesaw alternatives, sorted by what you are actually replacing
Seesaw is two products that share a login: a student work portfolio and a family communication channel. Almost every bad Seesaw replacement decision comes from treating it as one. Answer two questions before you look at a single vendor, and the shortlist writes itself.
| Option | Replaces portfolios | Replaces family comms | Where the data would live | Migration difficulty |
|---|---|---|---|---|
| Google Workspace for Education / Classroom | Yes | Announcements only | Drive, under district identity | Medium — student work moves as files, context does not |
| Microsoft 365 / Teams for Education | Yes | Announcements only | SharePoint, under district identity | Medium |
| ClassDojo | Portfolio-ish, plus behaviour | Yes, classroom-level | Vendor cloud, classroom-origin accounts | High — media rarely transfers cleanly between vendors |
| Your LMS (Canvas, Schoology and similar) | Yes, if you already have one | Weak for guardians | The LMS you already licence | Low if adopted — it is already rostered |
| ParentSquare | No | Yes, district-wide | Vendor cloud, district-governed | Medium |
| Bloomz | Limited | Yes | Vendor cloud, district-governed | Medium |
| Kastr | No — we have no portfolio, attachment or media capability at all | Yes, district-wide | Vendor cloud, district-governed | Medium — people and contacts move; media does not exist to move |
Migration difficulty here is driven almost entirely by media. Text records, people and contact points move between systems adequately. Photographs, video, audio recordings and annotated student work generally do not, because there is no common format and no vendor has an incentive to build the exporter. If years of student work matter to your families, plan the archive before you plan the switch.
Two questions that decide your shortlist
Ask them in this order, and answer them with evidence rather than intuition.
Question one: what are teachers actually using it for? Not what it can do — what is happening this term. Pull whatever usage signal you can get and ask a dozen teachers across three grade bands. The answers cluster into three patterns: portfolio-heavy (student work posted, families comment), comms-heavy (announcements and messages, little student work), and dormant (an account per class, nothing in it since September). Each pattern points at a different replacement, and the third points at not replacing anything.
Question two: is the portfolio a requirement or a habit? A portfolio is a requirement if it feeds conferences, reporting or an assessment practice your district has committed to. It is a habit if it is a nice thing individual teachers do. Requirements need a portfolio product. Habits usually survive fine inside Google Classroom or an LMS you already pay for, and the district saves a licence.
If the answer is portfolio-heavy and the portfolio is a requirement, a communications platform is not a Seesaw alternative and nothing on the comms shortlist will satisfy the need. Say that out loud in the evaluation meeting before anybody schedules a demo, because the alternative is discovering it in month four.
Shortlist one: replacing the portfolio
Sorted by how much new licensing it costs you.
- What you already own. If the district has Google Workspace or Microsoft 365, a workable portfolio exists at no extra licence cost, and the work sits under district identity rather than a vendor's. The trade is real: it is more setup, less delightful for a second-grader's family, and it needs a teacher-facing routine to survive past October.
- Your LMS, if you have one and it is adopted. Canvas, Schoology and their peers all carry assignment and portfolio constructs, and they are already rostered from your SIS. The failure mode is guardian access, which in most LMS products is an afterthought.
- ClassDojo, if the portfolio requirement is really an engagement requirement and the district is comfortable with a vendor that monetises families directly.
- A dedicated portfolio product. Worth considering only where portfolios feed assessment or reporting practice. Otherwise it is a third login for a habit.
Kastr is not on this list and cannot be. We have no portfolio, no attachments, no file uploads, no photo or video sharing and no media of any kind. There is no upload path anywhere in the product. If student work is what you are replacing, we are not a candidate at any price.
Shortlist two: replacing family communication
If the usage pattern is comms-heavy — announcements, reminders, the occasional message thread — then you are not replacing a portfolio tool at all, and the field is much wider and considerably cheaper.
- District-wide platforms — ParentSquare, Bloomz, SchoolStatus and their peers — give you SMS, email and voice reach that does not depend on a family installing an app, plus district-level administration, roles and reporting.
- Comms-only platforms, ours included, do the same job in a narrower product at a lower price. Our argument is a published rate, one tier with everything included, a 28-endpoint REST API with signed webhooks, an MIT-licensed CLI and MCP server, translation preview before you send, cost-and-reach preview before you send, and a SHA-256 hash-chained append-only audit log. Our disclosure is that we are pre-launch, have no single sign-on, no media, no push notifications, no SOC 2 and no district references.
- TalkingPoints if translation is the binding constraint and the budget is thin.
The archive decision, which is the one people forget. Before any Seesaw cutover, decide what happens to existing student work. There are three defensible answers: export and archive centrally, give families a window to download their own child's work, or accept the loss and tell people plainly. There is one indefensible answer, which is not deciding and discovering in August that the account is closed. Whichever you choose, communicate it at least eight weeks out and repeat it twice, because families act on the third message rather than the first.
Questions people actually ask
What can replace Seesaw for student portfolios?
Usually something you already own. Google Workspace or Microsoft 365 both support a workable portfolio under district identity at no additional licence cost, and an adopted LMS carries assignment and portfolio constructs already rostered from your SIS. A dedicated portfolio product is worth buying only where portfolios genuinely feed assessment or reporting practice rather than being a teacher habit.
Is a communications platform a Seesaw alternative?
Only if what your teachers actually use Seesaw for is communication. If student work is being posted and families are responding to it, a comms platform will not replace that and will make the district look as though it did not understand its own usage. Check the usage pattern first, by grade band, before shortlisting anything.
Which Seesaw alternative is best for a whole district?
For district-wide reach, a district communications platform rather than a classroom tool, because reach to families who never install an app is the requirement that only SMS, email and voice satisfy. For portfolios at district scale, whichever of Google or Microsoft you already licence, since it avoids adding a vendor and keeps student work under district identity.
Do Seesaw alternatives keep student work when you migrate?
Generally not. Text and structured records move between systems adequately; photos, video, audio and annotated work usually do not, because there is no common interchange format. Plan the archive as a separate workstream from the platform decision, give families a download window, and communicate the deadline at least eight weeks ahead.
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.