CRM for Training Providers: How It Fits With Your TMS and LMS
What a training CRM holds, how it differs from a sales CRM like HubSpot or Salesforce, and which system owns each record when CRM, TMS and LMS connect.
On this page
A training CRM keeps learners, the organisations that pay for them and the managers who book them on one record, next to every booking, certificate and invoice. CRM is short for customer relationship management, the software that holds a business’s customer records. A sales CRM such as HubSpot or Salesforce does a different job: it tracks leads and deals until a sale is agreed. A training provider often needs both jobs done, alongside a training management system (TMS) that runs the courses and a learning management system (LMS) that delivers the online parts. Whether that takes one system or three, the thing to settle is which system owns each record, so the same person is never typed in twice.
Key takeaways
- Two different products are called a CRM. A sales CRM is built around deals. A training CRM is built around bookings, attendance and certificates.
- The CRM comes first and last (the enquiry, then the renewal). The TMS and LMS do the middle: booking, delivery, certificate and invoice.
- Give every record one owner. The sales CRM owns the deal, the TMS owns the booking and the certificate, the LMS owns lesson progress, and the others receive a copy.
- A generic CRM can hold a list of courses. Taking a booking, marking a register and issuing a certificate that expires are TMS jobs.
- Integrations match people by email address and companies by web domain. The usual failures between two systems start there.
Two things are called a CRM
CRM stands for customer relationship management. A CRM is the software where a business keeps its customers: who each person is, which company they belong to, what has been said to them and what they have bought. For a training provider the term covers two kinds of software, met at different moments.
A sales CRM is where a sales team works. Its records are contacts, companies and deals, and its screens are a pipeline: stages a deal moves through until it is won or lost. HubSpot’s standard objects, for example, include contacts, companies, deals and tickets. It is the right tool for a provider with people whose job is to win in-house contracts from employers.
A training CRM starts where the sale ends. Its records are the learner, the organisation that pays and the person who booked, and what hangs from them is training history: which course, which date, whether they attended, what they scored, which certificate they hold and when it expires. It answers the question a client asks a year later, which is who you trained for them and what is about to run out.
| Sales CRM | Training CRM | |
|---|---|---|
| Built around | Deals moving through a pipeline | Bookings, attendance and certificates |
| Main records | Contact, company, deal | Learner, organisation, booker, registration |
| Used by | Sales and marketing | Course administrators and account managers |
| Answers | Who might buy, and how likely is it? | Who did we train, for whom, and what expires next? |
| Stops at | The agreed sale | The next renewal |
The two overlap on one thing, the list of people and companies, and that overlap is where the integration work sits.
Where the CRM sits next to the TMS and the LMS
Follow one client from first contact to rebooking and each system takes a turn.
The CRM holds the relationship at both ends. The TMS and LMS run the course in the middle.
The split between the two middle systems is covered in TMS vs LMS, and the full list of TMS jobs in what a training management system is. The LMS knows what a learner has completed online, the TMS knows what was scheduled, booked, attended and invoiced, and the CRM knows who everyone is and what they have bought before.
Which system covers which job
Scroll sideways to see every column.
| The job | Sales CRM | Training CRM | TMS | LMS |
|---|---|---|---|---|
| Leads, deals and a sales pipelineSome training management systems include a pipeline; see the table further down | Covered | Not covered | Partly covered | Not covered |
| People linked to the organisation that pays | Covered | Covered | Covered | Partly covered |
| Training history on the person's recordA sales CRM shows it only if another system sends it across | Partly covered | Covered | Covered | Partly covered |
| Dates, bookings and paymentAn LMS sells access to content, usually to one person at a time | Not covered | Not covered | Covered | Partly covered |
| Registers, certificates and expiry datesAn LMS certifies online completion; a classroom register sits outside it | Not covered | Partly covered | Covered | Partly covered |
| Online lessons, quizzes and progressBuilt in on some training management systems | Not covered | Not covered | Partly covered | Covered |
| Marketing emails and campaigns | Covered | Partly covered | Partly covered | Not covered |
A training CRM is usually a part of the TMS and shares its records, which is why the two columns agree on people and history.
Which system should own each record
The common failure between systems is two of them both believing they hold the true version of the same record. The fix is to decide, record by record, which system owns it. The owner is where it is created and edited. Every other system gets a copy to read.
| Record | Owner | Who else needs a copy | Why |
|---|---|---|---|
| Lead or deal | Sales CRM | Nobody, until it is won | A deal is a forecast. It turns into a booking when the client agrees |
| Person | Whichever system they enter first | All of them, matched on email address | One person, one record, however they arrived |
| Organisation | Sales CRM if you have a sales team; otherwise the TMS | The other one | The company name, billing contact and VAT number should be typed once |
| Booking or registration | TMS | Sales CRM, as activity on the contact | It carries the date, the place, the price and the payment |
| Attendance | TMS | Sales CRM, as a summary | The register is marked where the date lives |
| Lesson progress and quiz results | LMS | TMS, as a completion status | Progress changes daily; other systems need only the outcome |
| Certificate and expiry date | TMS | Sales CRM, as a date to act on | The expiry date drives the next sale |
| Invoice and payment | Accounting system, raised from the TMS | Sales CRM, as a total per client | Finance needs one ledger |
A provider with no sales team can read the same table with the sales CRM column removed. The training CRM inside the TMS then owns the person and the organisation as well, and there is nothing to sync.
The three common setups
A sales CRM, a TMS and an LMS, connected. This suits a provider with a sales team already working in HubSpot or Salesforce and a catalogue of both live and online courses. Each system is strong at its own job. The cost is upkeep: two or three subscriptions, and connections that someone has to own when a field is renamed or an integration is updated.
A TMS with a training CRM built in, plus an LMS. This suits a provider whose sales are mostly bookings from a website and repeat orders from known clients. The people, organisations and training history live in the TMS, and the LMS is either part of it or connected to it. There is one place to look up a client. If a sales team arrives later, a sales CRM can be added in front.
One system for all three jobs. This suits a small team that wants one login and one bill. Booking, delivery, the client record and the online lessons share a database, so nothing needs syncing. The trade-off is depth: a built-in module can be simpler than a specialist tool, so check the one job you care most about before you commit.
Training management systems differ most on the sales side. These four take different positions, as stated on their own pages on 2 October 2026:
| System | Sales pipeline of its own | Link to a sales CRM |
|---|---|---|
| Arlo | Yes: leads and sales opportunities, each with a rating, a value and an estimated close date | A native Salesforce integration |
| accessplanit | Yes: enquiries and opportunities, and a course can be scheduled from either | None listed on its CRM page |
| Administrate | Works from Salesforce, which it describes as “your source of truth for accounts, contacts, and sales data” | Salesforce, with registrations, attendance and completions sent back |
| Cademy | On the roadmap as of October 2026. Today: contacts and organisations with their training history | HubSpot and Salesforce apps, Zapier, API and webhooks |
Which setup fits
There is no pipeline to manage. What you need is the record of who booked, who attended and what expires.
Deals stay where the sales team works. Bookings, attendance and expiry dates flow back to the contact so the next conversation starts informed.
The marketing tool needs to know who booked what and whether they agreed to be contacted. It does not need to edit the booking.
A second system adds a subscription and a connection to look after, for a pipeline nobody will keep up to date.
A sales CRM can show it only if the TMS sends it across. Check that it does before you promise the client a report.
How the connection works
There are three ways to join a sales CRM to a TMS, and they differ in who maintains them.
| Method | What it is | Suits | Upkeep |
|---|---|---|---|
| A ready-made app | An integration built by one of the two vendors, with the field mapping decided for you | The common flows: contacts, organisations, bookings as activity | Low. The vendor updates it |
| An automation tool such as Zapier | A rule of the form “when this happens there, do that here” | One or two simple flows, such as a new booking creating or updating a contact | Medium. Each rule is yours to fix when a field changes |
| The API and webhooks | Your own code, or an agency’s, reading and writing both systems | Unusual flows, large volumes, or a system with no app | High. You own the code |
Whichever you choose, decide the direction of each flow before you switch it on. A workable default has three parts. Companies and contacts flow both ways, matched on email address and web domain. Won deals flow from the sales CRM to the TMS, where they become a private date or a block of places. Bookings, attendance and certificate expiry dates flow from the TMS back to the sales CRM as activity on the contact, where the sales team can read them and cannot edit them.
A generic CRM can do part of the TMS’s job. HubSpot’s object library includes an optional Courses object for storing courses and tracking who is enrolled, which a Super Admin has to activate. Records beyond the standard ones (sessions, registers, certificates) need custom objects, and HubSpot offers those on its Enterprise subscriptions. The records can be modelled. Taking the booking and the payment, sending reminders, marking the register and issuing the certificate would still have to be built.
What tends to break
The email address is the key. A system that matches on email treats one address as one person and two addresses as two people. HubSpot, for example, deduplicates contacts by email address when they arrive by import or form. A learner who books once with a work address and once with a personal one becomes two people, with half a training history each. Merge them where the record is owned and let the merge flow outwards.
The booker is not the learner. An office manager who books five colleagues and types their own email into every row creates one person with five registrations. Ask for each attendee’s own email at checkout, or collect the names afterwards, and make sure the integration sends each attendee as well as the buyer.
Organisations are matched by web domain. HubSpot links a contact to a company when the domain of the contact’s email matches the company’s domain, and it does not make that link for free addresses such as gmail.com unless the contact has a website filled in. Self-funded learners therefore arrive with no company, which is correct. Groups and franchises that share one domain across several billing entities need a rule of their own.
An integration can create duplicate companies. HubSpot’s documentation notes that companies created through its API are not deduplicated by domain, and that this includes third-party sync apps. Before you switch a connection on, ask whether it searches for an existing company before it creates one.
Two systems edit the same field. If a phone number can be changed in both places and both sync, the older value can overwrite the newer one. The ownership table settles it, because only the owning system edits the field.
Marketing consent gets left behind. A learner ticks or leaves a box at checkout. If the booking reaches the marketing tool without that answer, someone is emailed who did not agree to it. Map the consent field first.
Before you connect anything
- List the records each system holds today, and mark the owner of each using the ownership table.
- Pick the match key for people (email address) and for organisations (web domain, or an ID you control).
- Write down the direction of every flow. Two-way is the exception.
- Clean up duplicates in the owning system before the first sync, because a sync copies them faster than you can merge them.
- Run the connection on ten real records and open each one on both sides.
- Name the person who owns the connection after go-live.
- Check what the app costs, and which plan the API or the automation tool needs, on both sides.
Frequently asked questions
What is a training CRM? A training CRM keeps learners, the organisations that pay for them and the managers who book them on one record, next to every booking, certificate and invoice. It differs from a sales CRM, which tracks leads and deals up to the point of sale. A training CRM is usually part of a training management system and shares its records.
Is a training management system a CRM? A training management system includes a training CRM, because it cannot take a booking without knowing who the person is and who is paying. Whether it also includes a sales pipeline varies. Some systems have leads and opportunities built in, some rely on Salesforce for that, and some hold the client record without a pipeline.
Do I need HubSpot or Salesforce as well as a training management system? You need a sales CRM if you have people working deals: proposals out, follow-ups due, a forecast to report. If your sales are bookings from a website and repeat orders from clients you already know, the training CRM inside the TMS covers the client record and a sales CRM adds a second system to maintain.
Can HubSpot or Salesforce run course bookings on their own? They can store the records. HubSpot has an optional Courses object, and custom objects for anything else on its Enterprise subscriptions. Taking payment for a place on a date, sending joining instructions, marking attendance and issuing a certificate with an expiry date are not built in, so they would need to be developed or handled by a connected TMS.
What should sync between a CRM and a TMS? Contacts and organisations in both directions, matched on email address and web domain. Won deals from the sales CRM to the TMS. Bookings, attendance and certificate expiry dates from the TMS to the sales CRM, as read-only activity on the contact. Invoices go to the accounting system, with a total per client visible in the CRM.
Does the LMS need to connect to the CRM? A direct connection is rarely needed. The LMS sends completion to the TMS, and the TMS passes a summary to the CRM. Connecting the LMS straight to the CRM creates a second route for the same person and a second place for duplicates to start.
Where Cademy fits
Cademy’s training CRM is part of the system that takes the booking, and it is on every plan including the free one. A contact’s record shows their orders, attendance, quiz results, certificates and emails on one timeline. An organisation record holds its contacts, registrations, private dates and invoices, with key contact and billing contact roles and parent organisations for groups. Contacts join an organisation automatically by email domain or from the organisation field at checkout, and duplicates can be merged with a choice of which record survives.
Cademy’s CRM is built around the training record, with enquiry forms, tasks, notes and an inbox for the conversations before a booking. As of October 2026, deals and pipeline stages are on the roadmap, and the public release notes at cademy.io/updates show what has shipped since. Today, a provider with a sales team keeps HubSpot or Salesforce for the pipeline and connects it: the Cademy HubSpot and Salesforce apps share contacts, bookings and training activity. The apps are available on custom plans, so get in touch to see whether they are available on yours. Zapier is included from Pro, and the API and webhooks are on Teams.
The integrations page lists what connects on each plan, and there is a side-by-side page on using Cademy with HubSpot. To talk through what should flow across and what should stay put, book a call, or start for free and look at a contact record with your own data in it.
Sources
Checked on 2 October 2026.
- HubSpot Knowledge Base: How to use objects for business processes (standard objects and the Courses object, updated 29 September 2026), Create and edit custom objects (Enterprise subscriptions, updated 29 September 2026), Deduplicate records in HubSpot (email address, company domain and the API note, updated 25 September 2026), Automatically create and associate companies with contacts (domain matching and free email addresses, updated 26 June 2026).
- Arlo: Training company CRM.
- accessplanit: CRM software for training providers.
- Administrate: Salesforce integration for training teams.
- Cademy: Training CRM, integrations and pricing.