Keep the classroom stack you've already invested in. We integrate around it.
Edumagined doesn't replace Microsoft 365, Google Workspace, or Apple School Manager. We federate identity, surface classroom data on the family record, and wrap the operational layer (admissions, tuition, parent communication, attendance reporting, finance) around the classroom stack your teachers already use.
The classroom layer and the operational layer solve different problems.
Your teachers have invested years building Teams channels, Google Classroom sites, Drive folders, OneNote notebooks, and shared calendars. That's their working environment. Forcing a migration to a new SIS vendor's proprietary classroom tool destroys teacher productivity and trains everyone to hate the new system.
What legacy SIS vendors do
Ship a half-built proprietary "learning management" layer bundled with the SIS. Force teachers to recreate their materials inside it. Charge for the LMS module on top of the SIS subscription. Make migration so painful schools never leave even when the LMS is worse than what they had.
What Edumagined does
Federate with the classroom stack you already have. Pull in identity, calendar, assignments, and grades. Surface that data on the family record alongside the operational data only Edumagined runs (tuition, transport, lunch, admissions, finance). Teachers keep their tools. The OS wraps them.
Three classroom stacks, one operational layer.
Microsoft 365 for Education
Entra ID federated SSO. Teams calls launched from CRM and Help Center. Outlook + Calendar for term boundaries, conferences, and meetings. OneDrive for shared documents + KB attachments. OneNote for lesson plans linked to the SIS course record.
Google Workspace for Education
Google SSO for all roles. Gmail + Calendar integration. Google Classroom assignments and grades sync into the SIS family record (read-only, conflict-free). Drive shared folders surfaced in Help Center KB. Meet for parent conferences.
Apple School Manager
Managed Apple IDs for student + staff devices. Schoolwork app federation. Classroom app session data flows into Edumagined attendance + behavior surfaces. iPad-first schools keep their MDM and identity provisioning workflow.
Federated identity, one-way classroom-to-OS data flow.
Federated SSO
Staff and students sign in to Edumagined with their existing MS 365, Google, or Apple credentials. No second password to manage. Provisioning + deprovisioning follows your existing identity workflow.
Classroom data flows in
Assignments, grades, calendar events, and attendance from the classroom stack surface on the SIS family record. One-way (classroom → Edumagined) so there are no sync conflicts or write-back race conditions.
Operational layer wraps it
Edumagined owns admissions, tuition, transport, lunch, finance, parent communication, and the family record. All operational apps read enriched data from the federated classroom stack. Teachers see no change in their working environment.
School owns every relationship
Your MS 365 / Google / Apple tenant stays yours. Your Stripe Connect stays yours. Your Twilio number stays yours. Edumagined orchestrates them; it never sits between your school and a vendor relationship.
Schools with classroom investments worth protecting.
MS 365 or Google power users
Faculty actively using Teams, OneNote, Google Classroom, or Meet daily. Migration to a proprietary LMS would mean rebuilding hundreds of teacher-built artifacts. Federation preserves all of it.
Centralized identity teams
Schools with a sysadmin or IT director who manages provisioning, group policy, and account lifecycle centrally. SSO + SCIM provisioning fits their existing toolchain.
Migrating from legacy SIS
Schools leaving Blackbaud / PowerSchool / Veracross who want a clean break from the proprietary LMS bundle while keeping their classroom stack intact. Lower-friction migration story.
Multi-campus + Network tier
Schools running multiple campuses on a single MS tenant or Google Workspace org. Edumagined federates once; identity flows to every campus. See Network Architecture →
Faith-aligned schools
Catholic, Christian, Islamic, classical schools where the classroom culture matters. Teachers don't want a generic LMS — they want their existing community-built materials preserved.
iPad-first programs
Schools running Apple School Manager + Schoolwork + Classroom. Edumagined federates with the Apple stack so 1:1 iPad programs don't lose their device management or curriculum delivery model.
Limits to be upfront about.
- We don't build a classroom layer. No proprietary LMS, no native quiz engine, no built-in document editor. Use the tools your school already runs.
- We don't write back to the classroom stack. Federation is one-way (classroom → Edumagined) to keep the data model conflict-free.
- We don't sit between your school and the vendor. Your Microsoft, Google, Apple, Stripe, Twilio accounts stay direct relationships. We orchestrate; we don't intermediate.
- We don't pretend to replace your classroom investment. If you're brand-new to K-12 and don't have a classroom stack yet, you'll need to pick one. Edumagined is honest about that.
See how federation fits your stack
30-minute walkthrough — bring your current MS 365 / Google / Apple licensing and we'll map exactly how Edumagined federates with your existing classroom and identity infrastructure.
Get a demo →