Upload CSV, JSON, and file-cabinet content. Middos classifies every file and preserves structured source rows.
Move your school into Middos without guessing what transferred.
Connect OneRoster for live roster data, stage Alma exports and documents, review coverage, then commit only after the package is ready.
Sign in to an administrator account to use the migration workspace.
Test credentials, preview a roster import, then commit externally-linked records into the school workspace.
Nothing from an Alma package is merged until analysis finishes and an administrator explicitly commits it.
Stage and analyze an Alma package
Select the complete export folder. Middos uploads each file, computes transfer coverage, and shows what is mapped, archived, or still missing.
Choose the folder containing CSV/JSON exports and file-cabinet documents.
Middos classifies the package, counts rows and documents, and compares it against the transfer checklist.
Only commit after the coverage below matches what you expect to move from Alma.
What Middos found in this package
Connect Alma or another OneRoster provider
Credentials are sent directly to the Middos server for the requested test/import and are not placed in the page URL or saved in your browser.
Migration history
Review migration runs created for this school, including analysis status, coverage, and committed archives.
What to bring from Alma
A complete SIS migration is more than a roster export. Use these channels together when the source data exists.
Students, staff, courses, classes, enrollments, organizations, academic sessions, and demographics.
Households, attendance, grades, fees, admissions, behavior, custom fields, messaging, reports, and other structured records.
Student documents, report cards, forms, attachments, and other files that do not belong in a roster API.
Missing means Middos did not receive matching source data. Archived means it was preserved even when a native mapping is not available yet.