Common Moodle Site Transfer Practices

By July 25, 2017Blog

During the transition to implementation process at eThink we encounter a wide variety of client needs and specifications. Whether a client is transitioning to eThink’s Moodle environment from another Moodle host, another LMS entirely, or are making their first dive into the LMS world, we are able to smoothly get them up and running with eThink.

Below is a quick list of some of the common Moodle site transfer practices we use when moving a client into the eThink environment.

Coming to Moodle by eThink from another Moodle provider or transitioning from a self-hosted Moodle site

This is the most common scenario that we encounter. With Moodle-to-Moodle site transfers, eThink is able to easily bring over entire Moodle sites exactly as they are with all site and user data intact.

Transferring Moodle site data can be completed in one of two ways when transferring to the eThink Education environment:

  • SFTP Transfer – If transferring via SFTP a full backup of the moodledata folder must be created, along with a full backup of the Database. This allows us to take over a full snapshot of the site in one fell swoop.
  • Rsync – Rsync offers for an overall decrease in needed downtime during the site transfer, as our team is able to run many subsequent Rsyncs after the initial data pull (only pulling across those updated files in the moodledata). This means a much shorter downtime for our clients using Rsync, as that final Rsync run is only pulling across minimal delta files in the transfer.

*The only potential issue we see when transferring from one Moodle site to another is caused by the Database type.  Moodle HQ does recommend the use of MySQL for your database, but we do sometimes see clients come our way with MSSQL, Postgres, Oracle, etc.  For those clients, it is recommended to begin a new Moodle site to help ensure a clean standup of your past data.

Coming to Moodle by eThink from another LMS

The biggest “roadblock” of transferring a non-Moodle site to the eThink environment is that there is no direct transfer process available, but that is not to say that we cannot bring over your current course data to our site.  Instead of a full site transfer, we are able to transfer content on a course-by-course basis via the usage of .imscc packages.

  • IMSCC Content – The IMS Course Content package is a ubiquitous backup type that can be transferred between different LMSs.
  • IMSCC packages function within Moodle similar to how a .mbz or .zip package would work, in that upon restore a user needs simply to upload this .imscc file and work through the standard Moodle restore steps. Moodle itself will recognize that this is a .imscc file and will work through its internal process to help restore the file.

Creating A New Moodle Site From Scratch

We often see brand new users to the LMS world who choose Moodle for its modular approach and ease of use for new users. We at eThink love to see new Moodlers come aboard, but we understand that this can be a daunting process to jump into alone. eThink will work with clients to customize their Moodle site and can give new Moodlers a bit of a leg up by offering out some of our collective knowledge and guidance on integration setups, pedagogical needs, and tips and tricks on how to get the most of Moodle.

eThink’s Training and Orientation courses help clients familiarize themselves with not only Moodle, but the eThink environment. eThink also offers remote and onsite Admin and Faculty training to help ensure that new users get the most out of their Moodle site. (See what Mississippi College thought about their Moodle 3.2 upgrade training here.)

 

Interested in scheduling onsite or remote Moodle training? Speak with a Moodle expert to learn more.

Request a Demo