Cloud or on-premise
Compare data location, capacity, network dependencies and support ownership. No specific hosting location or SLA is promised.
Choose infrastructure and system connections with clear operational ownership.
Compare data location, capacity, network dependencies and support ownership. No specific hosting location or SLA is promised.
Map stable identifiers and required fields. Validate authentication, account removal, synchronization and error handling.
Back up the database, files and configuration. Test restore procedures against agreed recovery objectives.
Include integration, migration, licenses, maintenance and monitoring. OpenLMS commercial pricing has not been approved.
Reference: Original source ↗ · Scope reviewed 8 November 2026.
Use these topics to define the scope and evidence needed for your project. Listing a requirement does not mean a deployed OpenLMS feature is available.
Confirm the selected Moodle version, core configuration, any plugin or custom work, and the acceptance evidence for each requirement.
Compare data location, capacity, identity access, backup, disaster recovery and maintenance ownership. Neither deployment model alone establishes security or compliance.
Distinguish course backup from full site recovery. Define database, files, configuration, retention, restore testing and recovery responsibilities together.