Description

A focused course, tailored for you

The Program Coordinator's LMS Migration Playbook

For program-driven education professionals running an LMS migration across faculty, registrar, IT, and accreditation reviewers without dropping a single course or learner record.

You are the only person in the room who knows which course rubrics did not survive the last mid-term import, which faculty member still grades inside a personal spreadsheet, and which accreditation cycle is going to ask for the historical grade book in three months. The LMS migration plan needs you to hold all of that and still hit the cutover date.

$199 one-time

Tailored to your situation. Access within 24 hours. 30-day money-back.

Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.

Why this course

Program coordinators in education sit at the intersection of every system that touches a learner. The LMS is the centre of gravity, but the migration is never just an LMS swap. It is a course-inventory exercise, a rubric audit, a SIS and SSO integration, an LTI grade-passback contract, a faculty enablement programme, an accreditation evidence project, and a change-communications calendar. The IT lead owns one slice. The registrar owns another. The instructional designers own a third. The coordinator owns the seven seams between them. When something falls through, it is the coordinator who gets the call from the dean asking why a learner's grade for a course that ran two terms ago cannot be retrieved. The playbook is the artefact that prevents that call by making the seams visible to every stakeholder before cutover, and by leaving an audit trail every reviewer signs off on after.

What you walk away with

A course inventory and rubric-survival map every faculty owner has signed.
A registrar-approved grade-passback contract before the SIS integration is switched on.
An accreditation-ready evidence pack showing learner records preserved end to end.
A faculty enablement run that does not collapse at the first term's first assignment.
A post-go-live audit log that closes the migration project formally for the dean.

The 12 modules

Module 1. The Course Inventory and Owner Map

Build the master sheet of every active and archived course with its faculty owner, current LMS location, target LMS location, and a rubric-survival flag. The module walks through how to extract the inventory from the legacy LMS export, how to reconcile it against the registrar's course catalogue, and how to assign each row an owner who signs that the course will travel. The template is the sheet that goes to the dean as the baseline scope artefact.

Module 2. Rubric Translation and Gradebook Mapping

Rubrics rarely survive an LMS migration cleanly. This module covers the rubric-by-rubric translation pass that maps legacy criteria into the new platform, identifies the rubrics that cannot be auto-imported, and creates the manual-rebuild list for faculty enablement. Includes the rubric-audit template and the gradebook reconciliation checklist the registrar will ask for during cutover.

Module 3. SIS and SSO Cutover Checklist

The integration with the student information system and the single sign-on provider is where most migrations fail silently. This module is the cutover checklist IT actually runs against, with the SAML and OIDC configuration verification steps, the SIS roster sync timing windows, the test learner accounts to provision, and the rollback plan if the first roster sync produces drift. Co-owned with IT, signed off by IT lead.

Module 4. LTI Grade-Passback Contract

The grade-passback path between the LMS and the SIS is the contract that decides whether learner grades land in the registrar's record. This module walks through writing the LTI Advantage configuration as a contract document, naming who is accountable for each leg of the passback path, what the validation tests look like, and how the registrar signs that grades will flow before any term opens. The deliverable is the signed contract the registrar files.

Module 5. Learner Record Preservation and Accreditation Evidence

Accreditation reviewers ask for historical learner records years after a migration. This module is the evidence pack: the data-extract methodology, the archival format, the integrity-check process, the chain-of-custody log, and the one-page narrative that explains to a reviewer how every record from the legacy system was preserved. Built to satisfy regional accreditation bodies and programmatic accreditors that require multi-year record retention.

Module 6. Course Template and Accessibility Standardisation

Migration is the moment to standardise course templates and accessibility compliance across the catalogue. This module walks through the master course template, the accessibility audit checklist (WCAG mapped to the institution's policy), and the rebuild-vs-import decision tree for each course. Includes the faculty-facing one-pager that explains why a course is being standardised and what the faculty owner needs to approve.

Module 7. Faculty Enablement Run and Office Hours

The faculty enablement programme is the single biggest determinant of whether the migration is judged a success in the first term. This module is the enablement calendar: the cohort-based training waves, the just-in-time office hours, the asynchronous walk-throughs, the peer-champion network, and the escalation path for the faculty member who calls the night before their first assignment opens. Includes the office-hours roster template and the training-completion tracker.

Module 8. Change Communications Calendar

Coordinators are the comms hub. This module is the change-comms calendar that runs from migration-decision through cutover through the first full term: the dean's announcement, the faculty all-hands, the learner-facing FAQ, the registrar's term-start letter, and the post-mortem readout. Every comms artefact has a template, an owner, an approver, and a send date locked to the migration timeline.

Module 9. Cutover Weekend Runbook

The cutover weekend has its own runbook because the standard project plan stops working at hour zero. This module is the hour-by-hour runbook: the final legacy-LMS export, the integration freeze, the production-tenant smoke tests, the registrar's reconciliation check, the IT sign-off, the dean's go-or-no-go decision, and the comms triggers for each outcome. Built to be printed and walked off paper by the on-call team.

Module 10. Post-Go-Live Audit Log and Issue Triage

The first 30 days post-cutover decide whether the migration closes cleanly. This module is the audit log and the issue-triage protocol: how every learner-reported issue is captured, categorised, routed, and closed with a recorded resolution. The audit log feeds two downstream artefacts, the accreditation evidence pack and the project close-out report to the dean. Includes the daily standup template and the weekly readout to the steering committee.

Module 11. Vendor Contract and SLA Review

The LMS vendor relationship changes shape after migration. This module is the contract and SLA review pass: the uptime commitments to monitor, the data-export and portability rights to verify, the privacy and FERPA terms to revisit, the change-management and roadmap cadence to negotiate, and the renewal-clock calendar. Includes the vendor scorecard template the coordinator runs quarterly with IT and the registrar.

Module 12. Project Close-Out and Steady-State Handover

Closing the migration formally is what frees the coordinator to return to programme work. This module covers the close-out report to the dean, the lessons-learned log, the steady-state operations handover to IT and instructional design, the standing governance forum that picks up where the project steering committee left off, and the personal hand-off file the coordinator keeps for the next migration or the next role. The deliverable is the close-out memo the dean countersigns.

How this addresses your situation

Specific modules that map to what you said you are dealing with.

Modules 1, 2, 6 cover the academic-content side: inventory, rubrics, course templates, accessibility.

Modules 3, 4, 11 cover the technical and contractual side: SIS, SSO, LTI grade-passback, vendor SLA.

Modules 5, 10 cover the evidence side that accreditation and the dean will ask about for years.

Modules 7, 8, 9, 12 cover the coordination, communications, cutover, and close-out work that only the coordinator can hold.

What you get with this course

12 written modules in the Art of Service learning environment.
Downloadable templates and worked examples for every module (course inventory, rubric audit, SIS cutover checklist, LTI contract, evidence pack, comms calendar, cutover runbook, audit log, vendor scorecard, close-out memo).
The hand-built implementation playbook tailored to your institution's stack, accreditation context, and migration timeline.
30-day satisfaction guarantee.

What you will have in hand by Day 1, Week 1, Month 1

Within 24 hours of purchase: learning environment account provisioned and the hand-built implementation playbook delivered.

Self-paced thereafter, with the playbook acting as the running working document through your migration timeline.

Before and after

Before

You are tracking the migration across four spreadsheets, three Teams channels, and a backlog of dean's-office questions about which courses still need owners. The accreditation reviewer call is on the calendar and you do not yet have a one-page answer about how learner records will be preserved.

After

Every stakeholder is reading from the same artefacts. The course inventory has owner signatures. The LTI contract is signed by the registrar. The cutover runbook is on paper. The accreditation evidence pack is built. The dean has a close-out memo template waiting for the post-go-live signature.

What happens if you do not address this

Migrations that are not coordinated through this kind of structure fail in predictable ways. A rubric does not travel and a learner's grade ends up wrong on the transcript. A SIS roster sync produces silent drift and the wrong learners land in the wrong sections at term-start. An accreditation reviewer asks for a record three years later and the data-extract methodology was never written down. Every one of those failures lands on the coordinator's desk to fix.

Who it is for

Program-driven professional with a long career in education, holding a coordinator or program manager role where the work is coordination, communication, and systems-level problem solving across faculty, registrar, IT, and external reviewers. Comfortable in spreadsheets, comfortable running cross-functional standups, less comfortable when the LMS vendor sends a 60-page technical migration guide that nobody on the team will read end to end.

Who this is NOT for. Not for the LMS vendor's professional services consultant who runs migrations as a job. Not for the IT director who only owns the technical cutover and hands the rest to the academic side. Not for a coordinator whose institution has already finished migration and is in steady-state operations. This playbook assumes the migration is upcoming, mid-flight, or recently completed with cleanup still owed.

How it arrives

Text-based course in the Art of Service learning environment, plus downloadable templates and worked examples for every module, plus the hand-built implementation playbook delivered alongside course access.

Time investment. Roughly 60 to 90 minutes per module if read end to end. Most coordinators work module-by-module against their own migration milestone, treating each module as the prep for the corresponding stakeholder meeting.

Why $199 is the right number

The LMS vendor's professional services team will run the technical migration but will not own the rubric audit, the faculty enablement, the accreditation evidence, or the comms calendar. A generic project management course will teach project mechanics but will not teach the specific seams of an LMS migration in an education context. This playbook fills the gap that vendor PS and generic PM training both leave on the coordinator's plate.

FAQ

Does this work if the migration is already mid-flight?

Yes. The modules are written so they can be picked up at any point in a migration timeline. The implementation playbook is built to your current state, not a greenfield start.

Is the accreditation evidence pack tuned to a specific accreditor?

The template is generic across regional accreditors and the major programmatic accreditors. The hand-built playbook is tuned to the accreditor you name at purchase.

What if our institution uses a non-mainstream LMS?

The SIS, SSO, LTI, and grade-passback chapters are written against the LTI Advantage and OIDC standards, which the major LMS platforms all implement. The playbook is adjusted to your specific platforms.

What if I am the only coordinator on this and have no project office support?

The playbook assumes that exact case. Every artefact is written so a single coordinator can produce, circulate, and close it without a separate PMO.

30-day money-back guarantee. If after a week of working through the materials this is not what you needed, reply to the receipt email and a full refund is processed. No questions, no forms.

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.