Training provider CRM checklist

The shape of the problem

A training provider's CRM has to model three relationships at once: the funder or employer who pays, the learner who attends, and the course they enrol on. Add accreditation bodies (Ofsted, IfATE, awarding organisations), funded-learner reporting (ESFA, devolved authorities), and renewals or re-enrolment cycles, and you can see why a generic sales CRM falls over quickly.

The 10-point checklist

1. Learner records as first-class entities. Not contacts on an account - a learner has their own status, qualifications, attendance and history.

2. Course and cohort scheduling. The CRM should manage course instances, locations, trainers, capacity and waiting lists - not just send a confirmation email.

3. Funder and employer accounts. Often the same organisation pays for many learners across many cohorts; the CRM has to roll value up cleanly.

4. Funded-learner data fields. ULNs, NI numbers, prior attainment, employer details - capture them once, reuse everywhere.

5. Accreditation and qualification tracking. Awarded qualifications, certificate numbers, expiry dates, renewal triggers.

6. Attendance and progress. Even if the LMS is the source of truth, the CRM should surface enough to drive retention activity.

7. Renewal and re-enrolment workflows. CPD courses, annual mandatory training, apprenticeship progression - all need automated nudges.

8. Marketing consent and lawful basis. Different bases apply to learners, alumni, employers and prospects; the CRM has to keep them separate.

9. Reporting that maps to your funder. ESFA ILR exports, awarding-body returns, Ofsted-ready dashboards.

10. Integration with your LMS and finance system. Two-way where it matters; one-way where it doesn't.

How Dynamics 365 handles this

Dynamics 365 Sales plus Customer Service covers most of the list out of the box, with a small amount of configuration to model learners and courses properly. Power Automate handles the renewal workflows, Power BI handles the funder-facing reporting, and the platform's role-based security lets you keep funded-learner data tightly scoped. For training providers already in the Microsoft ecosystem, it's usually a faster path than a specialist training CRM.

The non-CRM question

Be honest about whether the LMS or the CRM should own each piece of data before you start. Most failed implementations we see are because both systems tried to own the same record and neither won. The checklist above assumes the CRM owns the relationship and commercial layer, and the LMS owns delivery and assessment.

Where to go next

If you'd like a sounding board on which items on the checklist matter most for your model, our Dynamics 365 for training providers page is the best starting point.