Available in: Enterprise

Transitioning from domain-based login to SSO is a two-step process: set up the SSO integration, then migrate any existing staff accounts whose email addresses are changing.

Domain access provides no school-site delineation — it cannot associate users with specific campuses, so reporting cannot be broken down by school and site-level features (site admin roles, site-based tool sharing) are unavailable.

To unlock school-level data, the district needs SSO with site-level data sharing enabled through Edlink. How that data flows depends on the provider:

The district configures sharing in their SSO provider, then submits the MagicSchool Onboarding Form. Setup typically completes within 3–5 business days.

This step is only required if staff email addresses are changing.

If staff email addresses are the same in the new SSO system as they were under domain access, no migration is needed — users will automatically connect to their existing accounts on first SSO login.

If the email format is changing (e.g., @district.net to @district.org), a bulk migration is required to preserve prior account data. Without it, staff get a blank new account when they log in via SSO.

The migration preserves:

To request a migration, contact your Customer Success Manager or email [email protected] with a CSV mapping each staff member's current email to their new SSO email, plus user roles (teacher or org_admin). The MagicSchool team validates, queues, and processes the migrations in batches.

📝 Note: If a staff member's SSO email already exists in the system (e.g., they also had a free account), content from the old account is automatically merged into the existing one.