Blackboard has large institutional bases and tightly bound processes — so migrating calls for planning, not haste. With IMS Common Cartridge, SSO/SCIM and LTI 1.3, you can migrate in waves and without disruption. Here's the step-by-step.
Quick answer
- Content: IMS Common Cartridge (Blackboard exports; Studeia imports)
- Users: SSO (SAML/OIDC) + SCIM 2.0
- Transition: LTI 1.3 (Blackboard + Studeia coexistence)
- SCORM not supported — recreate as native lessons
- Migrate in waves, starting from a pilot
Step by step
- Export from Blackboard. Export/Archive Course → IMS Common Cartridge.
- Import into Studeia. Via
POST /api/institution/courses/importor UI. - Connect SSO/SCIM. Institutional IdP (Shibboleth, ADFS, Azure AD) via SAML/OIDC + SCIM.
- Run in parallel via LTI 1.3. Studeia as a tool in Blackboard, with AGS.
- Validate and migrate in stages. Pilot → waves until the final cutover.
Why migrate in waves
Large Blackboard bases have many integrated processes. Migrating all at once is risky. In waves — a pilot course or department first, then expansion — you validate each step and keep the operation running. Coexistence via LTI 1.3 is what makes this possible.
What needs attention
| Item | Transfers via | Note |
|---|---|---|
| Courses (modules/lessons) | IMS CC | Recreated on import |
| Users and classes | SSO/SCIM | Syncs with the directory |
| Historical grades | Export/CSV | Check mapping |
| SCORM/H5P | Recreation | SCORM not supported |
| Compliance/processes | Planning | Map before cutting over |
FAQ
Does Blackboard export in a compatible format? Yes — IMS Common Cartridge, which Studeia imports.
Is migration risky? That's why you migrate in waves, with coexistence via LTI 1.3.
Does it import SCORM? No — Studeia uses IMS CC + LTI; SCORM/H5P is recreated.
How do I keep institutional login? SSO (SAML/OIDC) + SCIM integrated with the IdP.
See the Studeia vs Blackboard comparison and SSO Enterprise + SCIM.