A Totara LMS implementation plan: the first 90 days

Most LMS implementations do not slip because of the software. They slip because a decision that should have been made in week one, such as how the organisation is structured, which historical records move across, or who owns sign-in, is still open in week eight.

This plan is written from the partner side of a Totara LMS implementation. It sets out what happens in each phase, who does the work, and the points where projects most often lose time. It is based on the plan our technical team uses when scoping a guided implementation, with client specifics removed.

The short version: a guided core implementation runs about 16 weeks. The first 90 days take you from kickoff to a tested pilot. Training, rollout and stabilisation follow.

The plan at a glance

Phases 2 and 3 overlap on purpose. Content work can start once the structure it depends on is agreed, which is well before configuration is finished.

Before day one: decide who builds what

The first scoping decision is the division of labour, and it shapes everything after it.

In a guided implementation, your team does the building: configuring the platform, recreating courses, and executing the data migration. Our technical team guides, reviews and trains throughout, with named senior specialists rather than a rotating queue. The advantage is that platform knowledge lives inside your organisation from the first week, not in a partner's handover document at the end.

That model asks for real internal capacity. Plan for a project owner, LMS administrators and course builders, an integration engineer for HR and identity systems, infrastructure support if you host the platform yourself, subject-matter representatives from the teams whose training is moving, and a group of people willing to run acceptance testing.

The split between your team and your Totara partner is set at scoping. What should not change is that every responsibility has one named owner before kickoff.

Days 1 to 14: alignment and kickoff

The first two weeks produce no configuration at all, and that is correct.

This phase sets governance and communication channels, agrees the success metrics the project will be judged on, and fixes the project plan and RACI. Our technical team hands over configuration and data-mapping workbooks, and if you self-host, an environment readiness checklist for your infrastructure.

Data mapping starts here, not in phase 3. It is the longest-running piece of work in most implementations, and the one most dependent on decisions only your organisation can make.

What to have ready by day 14:

• Agreed success metrics, written down
• A named owner for every row of the RACI
• A first draft of your organisational structure as it should appear in Totara
• A decision on how far back historical training records need to go

Days 15 to 42: guided configuration and integration

This is where Totara starts to look like your organisation. Your administrators configure, and our technical team reviews each area, advises on patterns, and quality-checks the result from the application side.

The order matters more than it does on a simpler LMS, because Totara's features are built on each other:

Organisational hierarchies come first. Positions and organisations are the structure that audiences, assignments and reporting all hang from. Changing the hierarchy after audiences are built means rebuilding them.

Roles and permissions follow, so that managers see their teams and nobody else's.

Audiences group learners, either by hand or dynamically from hierarchy and profile data, so that enrolments and assignments stay correct as people join, move and leave.

Certifications and recertification rules are configured once audiences exist to assign them to. For compliance training, this is the part to test hardest.

Branding, single sign-on against your identity provider, and the HR system integration complete the phase. Sign-on is a common source of delay because it depends on a separate IT team's calendar. Book that time in phase 1.

Days 29 to 70: content recreation and data migration

Content and data move in parallel, and both follow the same discipline.

Courses are recreated in Totara: SCORM packages uploaded, video and documents rebuilt using course templates, and bulk course upload used wherever volume justifies it. This is a good moment to retire content nobody has completed in years rather than migrating it.

User records and historical completions move through trial loads, usually from CSV. The approach our technical team brings follows Totara's published migration guidance:

• Map the data first
• Clean it before moving it
• Move what is needed, not everything that exists
• Reconcile every load

Every trial load should produce a reconciliation report, and nobody should make a cutover decision until those reports have been reviewed jointly. For regulated organisations, historical training, certificate and compliance records should keep their original completion dates and evidence documents. A migrated record that shows the migration date instead of the completion date is an audit finding waiting to happen.

Be realistic about history. Totara's migration guidance puts full-history migrations at two to nine months, which is why the scope decision made in week two matters so much. A 16-week core implementation and a complete historical migration are not always the same project.

Days 71 to 84: testing and pilot

Your team runs user acceptance testing against real scenarios: a new hire enrolling, a manager checking team compliance, a certification expiring, a record being corrected. Our technical team reviews the findings from the application side and supports fixes.

The pilot group should be representative, not convenient. A pilot run only with head office staff will not surface the problems that field, shift or remote learners will hit on day one of rollout.

By day 90 you should have a configured platform, migrated and reconciled data, a tested pilot, and a list of known issues with owners and dates.

What happens after day 90

Weeks 13 and 14 are training and change management. Our technical team delivers administrator and train-the-trainer sessions inside your own configured environment, not a demo site, followed by role-based sessions for managers and supervisors. Your team runs the communication campaign and produces quick-reference material for learners.

Weeks 15 and 16 onward are rollout and stabilisation: a phased go-live on your schedule, with hypercare application support through stabilisation. After that, support moves to business as usual, and Totara upgrades follow a staging-first practice so that nothing reaches learners untested.

Where 90-day plans slip

Most delays trace back to a handful of causes, and all of them are visible early:

• Data mapping starts late. It is the longest task, so it has to start first.
• The organisational hierarchy is still being debated when audiences are being built.
• Single sign-on waits on an IT team that was not booked in phase 1.
• Historical migration scope was never decided, so it grows.
• The pilot group was chosen for convenience.
• Training is treated as a launch-week event rather than a phase.

If your plan does not name an owner and a date for each of these, it is not yet a plan.

Choosing a Totara consultant or partner

A Totara partner's implementation plan tells you more than its sales deck. Questions worth asking:

• Who does the building, and who does the reviewing? Get it in writing.
• Will you work with named specialists, or a support queue?
• What does the migration approach produce before cutover? Ask to see a sample reconciliation report.
• If you host Totara yourself, where does the partner's support end and your infrastructure team's begin?
• How are upgrades tested before they reach learners?
• What does support look like in year two, once your administrators are self-sufficient?

For a broader pre-launch list that applies to any platform, see our LMS implementation checklist: https://www.lambdalearn.io/en/blog/the-ultimate-lms-implementation-checklist-a-step-by-step-guide

Measuring whether it worked

The success metrics agreed in week one are the ones the project should be judged on at the end, not whatever is easiest to report. Totara's report builder answers most operational questions inside the platform: completions, overdue certifications, team compliance. When learning data has to be read alongside HR, CRM or revenue data, Lambda Learning adds Zoola Analytics as a separate reporting layer.

Frequently asked questions

How long does a Totara implementation take?

A guided core implementation typically runs about 16 weeks, from kickoff to phased rollout. Full historical data migration can take considerably longer, depending on how much history you move and how clean it is.

Do we need a Totara consultant, or can we implement Totara ourselves?

Totara is licensed and delivered through its partner network, so a partner is part of the picture either way. The real question is how much of the build your own team does. A guided model keeps the work and the knowledge in-house, with a partner reviewing and training.

Can historical completions and certifications be migrated?

Yes, through staged trial loads with reconciliation after each one. For compliance records, keep the original completion dates and evidence documents, and decide early how far back you need to go.

Can we host Totara on our own infrastructure?

Yes. In a self-hosted implementation, your team runs the infrastructure, operating system and database, and your Totara partner supports the application layer: configuration, troubleshooting, how-to guidance and upgrades.

What should be decided before kickoff?

Who owns each responsibility, what success looks like, how your organisation is structured, and how much training history needs to move.

Bring your timeline. We will tell you if it is realistic.

A conversation with our technical team about your organisation, your deadline and your data. If Totara is not the right fit, we will say so.

Book a demo: https://www.lambdalearn.io/schedule-a-meeting-lambda-suite

Talk to a specialist: https://www.lambdalearn.io/schedule-a-meeting-lambda-suite

Totara is a trademark of Totara Learning Solutions Ltd. Lambda Learning Inc. is a Totara Platinum Partner.