Assuming you’ve been managing your code and upgrades via a version control system such as Git or
SVN, we can roll back to the previous version of your site and upgrade from there. There will be a
little more work and testing involved, but it won’t stop you moving to Totara.
Yes, but we’ll need to invest some additional time into getting your site upgraded to 2.2.11
first. There were some significant changes between these versions and upgrading will require work
not only to the code base but also around user and course data migration.
All user data and content - so grades, completion data, courses, activities, resources etc - gets
carried across during your migration from Moodle to Totara. Because the two applications share the
same code base, you’re not going to lose anything, just gain access to new functionality.
There’s a rather neat piece of functionality within Totara called HR Sync. HR Sync allows you to
create and update your Positional and Organisational hierarchies either via a csv upload or direct
database query export. You can also create and update users using this tool, including linking
learners to their managers.
Once you’ve got your hierarchies and staff/manager relationships set up, you’ll be able to make the
most of some of the other great features of Totara such as Competency Hierarchies, Performance
Management, Management Approval Workflows and contextual Reporting.
In addition to the unlimited support offered by Mind Click, there is a dedicated Subscriber
Community forum area and an online manual (including tutorial videos) for Totara.
Well, it’s going to depend on those customisations. Integrations with other systems should be
relatively straightforward assuming we can reuse the code or they use standard Moodle
functionality. If your integration is with your HR system then perhaps Totara’s HR Sync can provide
this functionality out of the box.
Code customisations will be evaluated individually. The first thing we’ll check is whether that
custom work is available in Totara as standard - we find this happens pretty often. If so, we can
probably take that off the to-do list.
If your customisation isn’t part of core Totara we’ll need to work out how to add that to your new
site. Ideally it would have been developed as a separate module or plugin and we can upgrade and
migrate that separately. If you’ve had core changes made to your site, we’re going to have to
evaluate that and work out how best to manage and reproduce that code.
We love open source because of the freedom it offers our clients, so we make sure our code,
wherever possible won’t affect your upgrade path or choice of vendor down the line.