LMS implementation timeline: a week by week plan that holds
Most LMS rollouts don't slip because of the software. They slip because nobody decided how users match, which courses move or who signs off assignment rules. Here's the 10-week plan we use.

A realistic LMS implementation timeline for a cloud LMS with single sign-on and a moderate course catalog is about 10 weeks of focused work from kickoff to go-live, plus a buffer for holidays and security review. Add time for HRIS integrations, messy content or years of completion history. Projects rarely slip because of configuration. They slip because a decision or a dependency lands late.
In LMS Advisor, each track of this plan maps to something built in: SAML SSO and SCIM 2.0 provisioning for identity, Moodle .mbz, LearnDash and SCORM, xAPI or cmi5 imports for content, and assignments with due dates, overdue reports and expiring course certificates for configuration, in our cloud or on your own server.
Vendor guides usually quote longer. Docebo's 16-step LMS implementation project plan (updated January 9, 2026) gives 3 to 9 months for a cloud LMS and 6 to 12 months on premise, adds 2 to 4 weeks for simple integrations such as SSO or a basic HRIS feed, and 6 to 8 weeks for complex ones. Its plan also starts earlier than ours, with goal setting and product sourcing, so the numbers aren't directly comparable. What it doesn't give you is who does what each week, or which task blocks which. That's this plan. For the technical steps of moving content and records, use our LMS migration checklist.
How long does LMS implementation really take?
The clock starts when the contract is signed and a named owner has real time on their calendar. After that, four things decide the length more than the platform does.
- Identity. SSO alone is a few days of IT work. SSO plus automated provisioning, with groups mapped to departments, is a few weeks once you count testing and security review.
- Content. Forty SCORM packages built in one authoring tool test quickly. Four hundred courses from three content vendors and two previous LMSs don't.
- History. If auditors will ask for old completions, someone has to decide how those records move. That decision often takes longer than the import.
- Hosting. A cloud tenant is ready on day one. A self-hosted install needs a server, backups and IT sign-off first.
These are the planning ranges we use, measured from kickoff to go-live with a core team that has other jobs too. They come from our own projects, so treat them as starting assumptions, not benchmarks.
| Scenario | Plan for | What usually stretches it |
|---|---|---|
| Cloud LMS, SSO, under 100 courses, no history to move | 8 to 10 weeks | Security review started late |
| Cloud LMS, SSO and SCIM, several hundred courses, completion history kept | 12 to 16 weeks | Content inventory, format of the old records |
| Self-hosted, SSO and SCIM, HR-driven groups, regulated training records | 16 weeks or more | Server build, change control, audit sign-off |
The rest of this post uses the 10-week version, which every larger project still contains.
Who owns what across HR, IT and L&D?
A RACI chart assigns four roles to every workstream. Responsible does the work. Accountable signs it off (exactly one per row). Consulted gives input first. Informed hears afterwards. The executive sponsor is accountable for the go-live date and the budget. Everything else sits below that line.
| Workstream | L&D | HR / HRIS | IT / security | Compliance | Vendor |
|---|---|---|---|---|---|
| Project plan and weekly status | A, R | C | C | I | C |
| SSO and user provisioning | C | C | A, R | I | R |
| User attributes and org structure | C | A, R | R | I | C |
| Content inventory and import | A, R | I | I | C | C |
| Assignment rules and due dates | R | C | I | A | I |
| Certificates, validity and records history | R | C | I | A | C |
| Security and privacy review | C | C | A, R | C | R |
| Pilot and learner communications | A, R | R | C | I | I |
| Go-live and support handoff | A | I | R | I | R |
We'd normally make L&D the project owner, because L&D lives with the platform after launch. Two rows cause most of the arguments. Compliance holds the A on assignment rules because whoever defends them to an auditor should sign them off. HR owns the org structure because the LMS should copy the HR system of record, not invent a second one. If LMS departments don't match HR's, every manager report is wrong from day one.
What has to finish before what?
Most schedules are drawn as parallel bars. The trouble hides in the hard dependencies between them. We plan around six:
- Identity before enrollments. Decide the attribute that matches a person across systems (work email or employee ID) and turn on SSO before anyone bulk-enrolls. Accounts created by CSV with one email format, then matched by SSO on another, become duplicate users with split training history.
- Org structure before assignment rules. A rule like "all warehouse staff in Ohio, due in 30 days" only works once departments and locations exist and are filled from HR data.
- Content inventory before import. Decide what to retire first. Importing 600 courses and deleting 350 of them later doubles the testing.
- Certificate rules before the pilot. Templates and validity periods have to be settled before pilot learners complete anything, or you'll be reissuing certificates.
- Assignment rules before the pilot. Test the real rules on real people. Ten friendly users hand-enrolled by an admin prove very little.
- Security review before production data. Many IT teams won't allow real employee records in until the review closes. Start it in week 1.
Everything else can run in parallel.
Weeks 1 to 2: which decisions have to happen first?
The first two weeks produce decisions and lists, not configuration. Leave the kickoff with a named owner and a date for each item below.
| Team | Delivers by the end of week 2 |
|---|---|
| L&D | Content inventory (course, format, owner, last update, keep, retire or rebuild), required courses by role, a proposed pilot group |
| HR / HRIS | The attribute list the LMS will receive (employee ID, email, department, location, manager, hire date, job code) and who is allowed to change it |
| IT / security | Identity provider and method (SAML 2.0, plus SCIM or scheduled CSV), security questionnaire sent to the vendor, hosting decision confirmed |
| Compliance | Which courses are mandatory, the due-date rule for each, what counts as completion (completed, passed or both) and how long records are kept |
| Vendor | Tenant or install ready, admin accounts, a named contact, a test environment if you self-host |
The decision that stalls the most projects is the history decision. Do you move old completions into the new LMS, archive them as exports, or keep the old system read-only for a while? Any can be right. Not answering until week 8 is what hurts. Our table of training records retention requirements shows how long different US rules expect records to be kept.
If you used our LMS RFP questions during selection, IT's identity and hosting answers already exist. Reuse them.
Weeks 3 to 6: what runs in parallel?
Three tracks run side by side, each with its own owner. The project owner's job now is a weekly check on the six dependencies.
Identity track (IT)
- Week 3. Create the SAML app in the identity provider, exchange metadata and test sign-in with a few test accounts.
- Week 4. Turn on SCIM for a small test group. Confirm each attribute lands in the right field and test a deactivation.
- Weeks 5 to 6. Widen the scope to the full population and run the first full sync.
Budget time for that first sync. Microsoft's estimate for the initial Entra ID provisioning cycle is 0.01 to 0.08 minutes per assigned user, group and group member, and a job that creates every user from scratch takes about twice as long as one that matches existing accounts. So 10,000 objects in scope works out to roughly 100 to 800 minutes, before any retries. To test one mapping, Entra's provision on demand pushes a single user, typically in under 30 seconds.
Content track (L&D)
- Import in batches by priority, with mandatory courses first.
- Test every SCORM, xAPI and cmi5 package for launch, resume and the status it reports. A package that only sends "completed" when compliance expects "passed" is a surprise you want in week 3. Our SCORM, xAPI and cmi5 support page lists the package versions LMS Advisor accepts.
- Rebuild only what the inventory flagged as broken. Implementation is a bad time to redesign the catalog.
Configuration track (HR, compliance and the LMS admin)
- Departments, locations and groups mapped from HR attributes, plus manager views and admin roles. The enterprise management features show how that structure looks in LMS Advisor.
- Assignment rules with due dates and mandatory flags, and the overdue report that managers will actually open.
- Certificate templates and validity periods, set up as described on our certificates and compliance page.
- Notification emails. IT often has to approve a new sending domain, so ask in week 3.
Close week 6 with a gate test. A test user signs in through SSO, lands in the right department, sees the right required courses with the right due dates, completes one and gets the right certificate. Fix any failure before the pilot starts.
Weeks 7 to 10: how do you run the pilot and go live?
Weeks 7 and 8: pilot
Pick 30 to 100 real people across two or three departments, including a manager, a shift worker on a phone and someone known to complain. The pilot should prove each of these:
- First login from the launch email, through SSO, with no password reset.
- A required course started on a phone and finished on a laptop.
- A manager pulling the overdue report for their own team.
- A certificate issued, downloaded and verified.
- A help request reaching someone who can answer it.
Keep every issue in one list and triage it daily: blocks launch, fix before launch, fix after launch.
Week 9: fix, freeze and communicate
Freeze configuration at the end of week 9. No new courses, no new rules. Send the announcement: what is changing, when, why and where to get help. Prosci's ADKAR model puts awareness and desire ahead of knowledge. In plain terms, people need to hear why the LMS is changing before they sit through a how-to video.
Week 10: go-live and hypercare
Widen provisioning to everyone, publish the assignments and send the launch email. Keep the old LMS read-only, not off, until the history work is done and checked. Run two weeks of hypercare with a daily 15-minute stand-up and a help desk script. Don't set the first due dates in launch week, or your first overdue report will be mostly noise.
What does an LMS implementation timeline look like for a January go-live?
January is a popular target because annual compliance training often restarts with the calendar year. Say go-live is Monday, January 11, 2027. The OPM federal holiday schedule puts Thanksgiving on Thursday, November 26, 2026, Christmas on Friday, December 25, New Year's Day on Friday, January 1, 2027, and Martin Luther King Jr. Day on Monday, January 18, which lands in the second hypercare week. Most US teams lose the last two weeks of December to vacation, so treat them as a freeze.
| Plan week | Dates | Focus |
|---|---|---|
| Week 1 | Oct 26 to 30, 2026 | Kickoff, owners named, security questionnaire sent |
| Week 2 | Nov 2 to 6 | Content inventory, attribute list, history decision |
| Week 3 | Nov 9 to 13 | SAML app configured, first content batch imported |
| Week 4 | Nov 16 to 20 | SCIM on a test group, assignment rules drafted |
| Week 5 | Nov 23 to 25 | Short week: package testing, certificate templates |
| Week 6 | Nov 30 to Dec 4 | Full sync, week 6 gate test |
| Week 7 | Dec 7 to 11 | Pilot starts |
| Week 8 | Dec 14 to 18 | Pilot ends, triage, configuration freeze |
| Buffer | Dec 21 to Jan 1 | Holiday freeze, no changes |
| Week 9 | Jan 4 to 8, 2027 | Last fixes, launch communications, help desk script |
| Week 10 | Jan 11 to 15 | Go-live and first week of hypercare |
Two things fall out of this. Kickoff has to happen by late October, which surprises teams who think January is far away. And the freeze moves up to December 18, because nobody will fix a broken assignment rule on December 30. If the contract isn't signed by mid-October, move go-live to February instead of squeezing the pilot. Put the first due dates in February either way.
What makes LMS implementations slip?
Almost none of the usual causes are technical.
- The security review starts after configuration. Production data waits for it, and the pilot waits for the data.
- The matching attribute changes mid-project. Switching from email to employee ID after the first sync means cleaning up or re-creating accounts.
- Nobody signed off the assignment rules. Compliance first sees them in the pilot and rewrites half.
- Integrations get added along the way. Docebo's 2 to 4 and 6 to 8 week estimates are a fair reminder that every integration is its own small project. Park anything not needed on day one for phase 2.
- The self-hosted server isn't ready. A server, database, backups and a change ticket can take longer than the LMS setup. Our comparison of self-hosted vs cloud LMS covers the trade-offs.
- The project owner has a few spare hours a week. From week 3 to week 8, plan on at least half of one person's time.
How to run this plan in LMS Advisor
This is the plan we use on our own LMS Advisor projects, and the product is set up so each track has a clear home. Our team spent years building, fixing and migrating Moodle, WordPress LMS and SaaS installs, which is why the content and identity pieces get the most attention.
| Plan phase | What LMS Advisor gives you |
|---|---|
| Hosting decision (weeks 1 to 2) | Our cloud, or self-hosted on your own server (ordinary cPanel or VPS hosting works), with in-app migrations, backups and system-health tools |
| Identity track | SAML 2.0 single sign-on and SCIM 2.0 provisioning, plus Google sign-in, passkeys and two-factor authentication |
| Content track | Moodle .mbz and LearnDash course import, SCORM 1.2 and 2004, xAPI and cmi5 packages as lessons, and course export and import between installs, handy for moving a tested course from staging to production |
| Configuration track | Branches, organizations, groups and roles, course assignments with due dates and mandatory flags, overdue reports, manager views and a certificate designer |
| Pilot (weeks 7 and 8) | The iOS and Android apps or the installable web app for the phone test (the apps can save video, audio and document lessons for offline use), a public certificate verification page and CSV, Excel or PDF report exports |
| Go-live and phase 2 | Emails for never started, stuck mid-course and no login, Slack and Microsoft Teams notifications, and a REST API and webhooks for the integrations you parked |
The limits, so they land in your plan and not in week 9. The Moodle and LearnDash imports move courses, so plan learner history separately. Validity periods apply to course and exam certificates, and renewal by retaking is a course feature. The HR connectors cover BambooHR, Zoho People and Keka. On Workday, ADP or another HR system, people data reaches LMS Advisor through SCIM from your identity provider, a CSV upload or the REST API.
We won't promise a go-live date before we've seen your content, identity setup and records requirements. For a second opinion on your plan, book a demo and bring your content inventory and identity provider details. We'll show you where your critical path sits.
Frequently asked questions
How long does an LMS Advisor implementation take?
Plan on the ranges in this post: about 10 weeks for a cloud install with SSO, a moderate catalog and no large history move, and 16 weeks or more for self-hosted, regulated or history-heavy projects. LMS Advisor has SAML SSO, SCIM provisioning, Moodle and LearnDash course import and assignment rules built in, so most of the time goes to your decisions rather than to setup. We confirm a date only after reviewing your content and identity setup.
How long does LMS implementation take?
Plan about 10 weeks from kickoff to go-live for a cloud LMS with SSO and a manageable catalog, plus buffer for holidays. Self-hosted installs, large catalogs, HRIS integrations and moving completion history push that to 16 weeks or more. Docebo's plan quotes 3 to 9 months for cloud, but its steps start earlier, with product sourcing.
Who should own an LMS implementation, HR, IT or L&D?
L&D should usually own the project, because L&D runs the platform after launch. IT owns identity and security, HR owns the people data and org structure, and compliance signs off assignment rules and certificate validity. Give each workstream exactly one accountable person.
Can you implement an LMS in 30 days?
Sometimes, if the scope is small: SSO only, a few dozen tested packages, no history to move and a short pilot. Teams chasing 30 days usually drop the pilot and the security review, the two steps that catch problems before employees do. Cut scope instead.
How long should an LMS pilot run?
Two weeks is enough for most organizations, as long as the pilot uses real people, real assignment rules and real devices. Shorter pilots miss the second login and the first manager report.
Should we switch off the old LMS at go-live?
Usually not. Keep it read-only until old completion records have been moved or exported and checked against the source. Check the old contract's notice period early, since a renewal date can force the issue.
Add lmsadvisor.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.
