Trade Moodle plugin sprawl for a managed, audited platform.
Native .mbz import. Preserved roster, grade history, and question banks. Plugin-to-native mapping during pre-flight — most notably native AI proctoring and AI grading, removing two plugin relationships. White-glove engineering support, no separate migration SOW, and your team stops being a Moodle SRE.
Moodle vs Cognaxa, at a glance.
Honest, narrow comparison — only the differences customers actually weigh during evaluation. See the full matrix →
| Capability | Moodle | Cognaxa |
|---|---|---|
| Tenant isolation | Single-instance per institution | PostgreSQL Row-Level Security at the query planner |
| AI proctoring | Plugin / third-party integration | Native subsystem — one SLA, one on-call |
| AI essay grading + confidence | Not natively supported | GA — confidence bands + human review queue |
| Hosting + ops burden | Self-hosted or via partner | Fully managed; private VPC on Enterprise |
| SOC 2 Type II | Partial — depends on hosting partner | Yes (achieved Mar 2026) |
| Plugin / version sprawl risk | Common pain point | Single managed codebase, no plugin marketplace |
| Direct engineer escalation | Community / partner support | Yes — engineer-to-customer on Enterprise |
Two weeks, three phases, one weekend cutover.
Typical Professional-tier timeline. Multi-campus enterprise migrations land in 4–8 weeks; the phase shape stays the same.
- Export Moodle course backups (.mbz) for in-scope courses — full or selective
- Pull current roster from your SIS or Moodle's native CSV export
- Identify 1–3 pilot courses for parallel run
- Genfinish engineer joins kickoff; we map your active plugins to Cognaxa-native equivalents
- Bulk import .mbz archives into a staging tenant
- Roster + grade history mapped, dry-runs against historical attempts
- Visual fidelity QA on every module, quiz, and resource
- Faculty pilot group runs one full assessment in staging
- Faculty 90-minute training session (per-role runbooks shipped)
- Production cutover — most institutions run Moodle + Cognaxa in parallel for one course cycle
- Decommission self-hosted Moodle infrastructure (or hand to your partner for archival)
- Written post-cutover report: incident log, gradebook reconciliation, faculty feedback digest
What we migrate — and what we verify.
Course content
Modules, activities, resources, files. Moodle .mbz preserves structure; we verify rendering on every page.
Rosters + enrollments
Cohorts, groups, groupings. Mapped 1:1 to Cognaxa roles with no manual cleanup needed.
Grade history
Gradebook with grade items, categories, and historical attempts preserved. Auditable diff before cutover.
Question banks
Question categories, random-question rules, and tagging carry over. Calculated questions need a manual review pass.
Files + media
Course files migrated via signed URLs. Media references rewritten to Cognaxa storage.
Active plugins
We map common Moodle plugins to Cognaxa-native equivalents — most notably proctoring and AI grading. LTI 1.3 outbound is on the Enterprise roadmap (Q3 2026).
Migrating from a different LMS? See the Canvas playbook or Blackboard playbook — same playbook, different export formats.
Migration FAQ.
How long does a Moodle migration take?
Two to four weeks for typical Professional deployments. Multi-campus enterprise migrations land in 4–8 weeks. Parallel running for one course cycle is the recommended cutover pattern.
What about my Moodle plugins?
We map common plugins to Cognaxa-native equivalents during pre-flight. Native AI proctoring replaces SafeExamBrowser-style plugins; native AI grading replaces essay-grader plugins; native analytics replaces dashboard plugins. Custom plugins without an obvious mapping are flagged on the kickoff call.
We self-host Moodle today. What changes operationally?
No more PHP version juggling, no more plugin compatibility matrices, no more cron debugging. Cognaxa is fully managed (or private VPC on Enterprise). Your team stops being a Moodle SRE and starts being a learning team.
Will my Moodle course look the same on Cognaxa?
Structurally yes — sections, activities, quizzes, and gradebook configuration carry over. Cosmetic differences (theme, fonts, navigation chrome) will be visible. We do a side-by-side visual fidelity QA before cutover.
What does the migration cost?
White-glove migration is included with all Professional and Enterprise plans — no separate migration SOW, no per-course fees. Contact sales to learn more.
Bring your Moodle .mbz to the demo.
A 45-minute working session with a Genfinish engineer. We'll import a real course on screen, walk through the plugin-to-native mapping, and scope your cutover — including the operational handover from self-hosted ops to managed.