One playbook for Canvas, Blackboard, and Moodle.
Bulk student roster import is live today via our REST API. Course content, question banks, and the cutover plan are founder-led during the pilot — your faculty in a working session with one of us, your legacy export as the source of truth. No migration SOW, no per-course fees, no surprise renewal escalation.
Two clear categories — no surprises during the pilot.
We tell you up front which parts of your migration are programmatic and which parts a founder runs with your faculty. No marketing fog around what ships today.
- Bulk student roster import
Programmatic via our REST API — POST a JSON array of students (email, name, enrollment ID). Conflict-safe, optionally scoped to a group.
- Tenant provisioning
Your isolated tenant — database-level Row-Level Security, your own subdomain, your own admin account — set up by us during onboarding.
- 2FA / TOTP for every account
Authenticator-app multi-factor enforced from the first login. No add-on, no per-seat charge.
- Native AI proctoring, ready out of the box
Face presence, audio anomaly, server-synced timer, mandatory human review queue — live on day one of staging, not a separate vendor signup.
- Ongoing roster, course, and grade sync
Tenant-scoped REST API for the long tail — once you are live, every primitive is exposed for SIS or warehouse pipelines.
- Course content rebuild
Modules, lessons, video uploads, assignment specs are rebuilt in Cognaxa with your faculty during the staging phase. Bring your Canvas .imscc, Blackboard .zip, or Moodle .mbz to the kickoff — we work through it with you, page by page.
- Quiz and question bank rebuild
Question banks are rebuilt in Cognaxa with your faculty. We do not auto-convert QTI / Canvas question pool exports today — the rebuild lets faculty re-baseline difficulty, sectional timing, and randomization for the new platform.
- Historical grade preservation
Your legacy LMS gradebook stays as a frozen archive (recommended for audit purposes). Cognaxa starts as the system of record from cutover forward — we do not back-fill prior cumulative GPA or per-attempt history into Cognaxa.
- Cutover scoping with the founders
A founder is on the kickoff, the staging dry-runs, and the cutover weekend. No tiered support, no migration SOW, no surprise renewal escalation.
Three phases, scoped to your calendar.
The phase shape stays the same for every institution — durations are scoped to your exam calendar, integration footprint, and faculty bandwidth.
- Founder kickoff with your project lead — scope, exam calendar, faculty bandwidth
- Identify 1–3 pilot courses for parallel run
- Export your existing course archives (Canvas .imscc, Blackboard .zip, Moodle .mbz)
- Pull your current student roster (CSV or via your SIS export)
- Confirm SSO posture, exam volume, and data-handling scope
- Bulk roster import via the REST API into your staging tenant
- Founder-led course rebuild with your faculty using the legacy export as the source of truth
- Question banks re-baselined for Cognaxa with your faculty
- Faculty pilot group runs one full assessment in staging
- Faculty 90-minute training session (per-role runbooks shipped)
- Production cutover — recommend running the legacy LMS and Cognaxa in parallel for one course cycle
- Founder on shared on-call for the first finals window
- Written post-cutover report: incident log, faculty feedback digest, next-step recommendations
Migration FAQ.
Can you import my Canvas .imscc / Blackboard .zip / Moodle .mbz file directly?
Not automatically yet. Bring the export to the kickoff and a founder works through it with your faculty during the staging phase. We do not yet have a one-click importer for the legacy export formats.
What about historical grades and per-attempt records?
Your legacy LMS stays as a frozen archive — we recommend keeping it read-only for audit purposes. Cognaxa starts as the system of record from cutover forward. We do not back-fill prior cumulative GPA or per-attempt history into Cognaxa.
How long will my migration take?
We scope timelines to your exam calendar, integration footprint, and pilot scope — every institution is different. Most cutovers run the legacy LMS and Cognaxa in parallel for one course cycle before flipping the switch.
What does the migration cost?
We don't charge a separate migration fee or per-course fees while we're working with our first cohort of institutions. Talk to a founder for current commercial terms.
What about LTI tools and external integrations?
Cognaxa includes native AI proctoring and AI grading — that removes two common third-party integrations outright. For everything else, our REST API is the integration surface today.
Bring your legacy export to the demo.
A 45-minute working session with a Genfinish founder. We'll open your Canvas .imscc, Blackboard .zip, or Moodle .mbz together, walk through the rebuild, and scope a cutover plan with your faculty calendar in front of us.