Dealership CRM

CRM DMS Integration for Canadian Dealerships: Reynolds Ignite, CDK Drive, PBS, and Auto/Mate

15+ years in local marketing; Google Ads certified; Shopify Partner.

Here's something I hear from dealer principals more than almost anything else: "We bought a great CRM. We have a solid DMS. And they barely talk to each other."

That's the crm dms integration problem in one sentence. Your CRM is supposed to be the brain for lead management, BDC follow-up, and customer communication. Your DMS is the system of record for deals, ROs, inventory, and accounting. When those two don't sync properly, you end up with salespeople calling customers who already bought, BDC agents who can't see service history, and managers who don't trust any of the reports. It's a mess that costs you real money.

This article is specifically about the integration layer, which DMS platforms are involved, what the connection actually does, what it costs, and where it breaks. I'm not going to cover which CRM is the best overall fit for your store. For that, see our complete guide to dealership CRM. What I will cover here is the plumbing: Reynolds Ignite, CDK Drive, PBS Systems, and Auto/Mate, and what you need to know before you sign anything.

Why the DMS–CRM Connection Is Harder Than It Looks

Most dealers assume the integration is basically automatic. You pick a CRM, the vendor says "yes we integrate with your DMS," and you're done. That's not how it works.

The DMS is the most locked-down piece of software in your dealership. Reynolds & Reynolds built their reputation on a closed architecture. CDK has historically charged third parties for API access. PBS, being a Canadian company, has its own certification requirements. Auto/Mate (now part of the Solera family) has its own data model. Each one of these systems exposes data differently, charges differently for access, and has different limitations on what a third-party CRM can actually read or write.

Here's what a real integration needs to do to be useful:

Pull customer and contact records from the DMS into the CRM, so BDC agents see who they're calling
Push sold deals back from the DMS so the CRM can close the opportunity and stop follow-up
Sync vehicle ownership and VIN history so equity mining and trade-in campaigns work
Surface repair order data so service retention campaigns are based on actual shop activity
Do all of this in something close to real time, not a nightly batch that's 18 hours stale

Most "integrations" handle the first point reasonably well. The last four are where things fall apart.

Per CADA's Canadian Automotive Retail Evolution Study (CARES), 55% of Canadian dealers report integration challenges as a meaningful barrier to getting value from their tech stack. That number tracks with what I see. The CRM and DMS are the two most critical systems in the building, and they're often the least connected.

Reynolds Ignite and CRM Integration: The Walled Garden

Reynolds & Reynolds runs one of the tighter walled gardens in North American auto retail. If you're on Reynolds Ignite DMS, the path of least resistance is eLead CRM, which is Reynolds' own product. The integration there is native, meaning the data flows without a third-party connector and without separate integration fees.

The moment you want a different CRM, the picture changes.

Reynolds controls third-party access through certified interfaces. Getting VinSolutions, DealerSocket, or AutoSync connected to a Reynolds DMS requires going through Reynolds' certification process, which takes time and adds cost. Dealers running Reynolds Ignite with a non-Reynolds CRM typically report:

One-time integration setup: roughly CA$10,000–$30,000 per rooftop, depending on how deeply you want the data to flow
Monthly integration fees: CA$500–$1,500 per store, often billed by the CRM vendor as a pass-through from Reynolds

Those aren't numbers I invented. They're in the ballpark of what Canadian dealers report when they've gone through the process. Actual quotes vary based on your DMS contract, which CRM you're connecting, and whether Reynolds has recently changed its access terms.

The deeper issue with Reynolds integrations is write-back. Most third-party CRMs can pull customer data from Reynolds reasonably well. Pushing data back, so that a deal closed in the CRM updates the DMS record, or a service appointment booked through the CRM shows up in the service lane, is harder and often more expensive to set up properly.

One pattern I've seen across Reynolds stores: the BDC works leads in the CRM, the sale gets entered manually in the DMS, and nobody ever connects the two. The CRM opportunity stays open. The customer gets a follow-up call three days after they took delivery. That's not a training problem. That's an integration problem.

CDK Drive and CRM Integration: More Open, Still Complex

CDK Drive is probably the most common DMS among Canadian franchise dealers. It's more open to third-party integrations than Reynolds, which is one reason VinSolutions, DealerSocket, AutoSync, and others have relatively mature CDK connectors.

"More open" doesn't mean free or simple.

CDK charges for API access, and that cost typically gets passed through to you by your CRM vendor. Based on what Canadian dealers have shared, typical CDK integration costs look like this:

One-time integration setup per rooftop: CA$7,500–$25,000 depending on data depth and CRM vendor
Monthly API and data feed fees: CA$300–$1,000 per store

The range is wide because "integration" means different things. A basic integration that pulls customer records and pushes lead source data is cheaper. An integration that syncs RO data, deal status, F&I products, equity position, and service history in near real time is more expensive and takes longer to configure.

For CDK Drive specifically, the most common integration gaps I hear about:

Service RO data latency. Even when the integration is set up to include repair orders, there's often a lag. Your CRM shows a customer's last service visit as six months ago when they were actually in last Tuesday. BDC agents call with a service offer and the customer says "I was just there." That erodes trust fast.

Deal close-out timing. When a vehicle is sold and the deal is posted in CDK, the CRM opportunity should close automatically. In practice, there's often a delay or a manual step required. The result is that CRM reports overstate open opportunities and managers stop trusting the numbers.

Multi-rooftop data separation. If you're running a dealer group with multiple stores on CDK, each rooftop typically has its own integration contract. A customer who bought at your Toyota store and then submits a lead to your Honda store may show up as two separate people in the CRM, with no connection between the records. That's a cross-rooftop visibility problem, and it's one of the reasons larger groups are looking at CDP layers on top of their CRM. For more on that direction, see our breakdown of automotive CDPs after the Cox-Fullpath acquisition.

PBS Systems and Auto/Mate: The Canadian-Specific Considerations

PBS Systems is a Calgary-based DMS with a significant footprint among Canadian franchise dealers, particularly in Western Canada. If you're on PBS, the good news is that most major CRMs support it. The integration posture is generally more open than Reynolds, and PBS has been moving toward a more API-friendly architecture.

Typical PBS integration costs per rooftop:

One-time setup: CA$5,000–$20,000 depending on CRM and data depth
Monthly fees: CA$250–$800 per store

PBS also tends to have better support responsiveness for Canadian dealers than US-based DMS vendors, which matters when something breaks on a Saturday morning and you have a full sales floor.

Auto/Mate is now part of the Solera family, which also owns DealerSocket. That relationship has some practical implications. If you're running Auto/Mate DMS and DealerSocket CRM, you're inside the same corporate family, which generally means better integration support and lower friction. If you're running Auto/Mate DMS with a different CRM, budget and timeline expectations are similar to PBS: CA$5,000–$20,000 one-time, CA$250–$800 monthly.

One thing that's specific to Canadian dealers regardless of which DMS you're on: CASL compliance in your CRM's marketing automation. Your CRM needs to track consent type (express vs. implied), consent date, and channel separately for email and SMS. Implied consent from a web inquiry is only valid for six months under CASL. Implied consent from a transaction is valid for 24 months. If your CRM integration doesn't pull transaction dates from the DMS accurately, your consent decay logic breaks, and you're sending commercial messages to people whose consent has lapsed. That's a compliance exposure, not just a data quality issue.

What a Real Integration Project Actually Looks Like, Week by Week

I think this is the piece most vendors skip over. They tell you the integration exists. They don't tell you what the next 8–12 weeks actually look like.

Here's a realistic timeline for setting up a CRM–DMS integration on a single Canadian franchise rooftop. I'm using CDK Drive + VinSolutions as the example because it's one of the most common combinations, but the shape is similar for other pairings.

Week 1–2: Scoping and contracts

Your CRM vendor and DMS vendor need to confirm the integration is certified and current. Ask for the specific version of the CDK connector VinSolutions is using and when it was last updated. Get the integration fee in writing from both sides. Confirm what data objects are included: customers, vehicles, deals, ROs, F&I products. If ROs aren't in scope, say so now.

Week 3–4: Data mapping and field configuration

The CRM and DMS use different field names for the same things. "Customer" in CDK might be "Contact" in VinSolutions. Your integration team needs to map these manually. This is also when you set up lead source codes so that when a lead comes in through AutoTrader.ca and eventually closes in CDK, the CRM knows to attribute that deal to the right source. If you skip this step, your attribution reports are garbage from day one.

Week 5–6: Test environment setup and initial sync

The integration runs in a test environment first. Your CRM vendor pushes a batch of historical customer records from CDK into VinSolutions. You check for duplicates, missing fields, and data quality issues. Per what dealers commonly report, expect 10–30% of records to have some kind of data quality problem: duplicate entries, missing phone numbers, mismatched VINs. This is normal. It's also the right time to fix it, before you're running live campaigns against bad data.

Week 7–8: BDC workflow configuration

With data flowing, you configure the actual BDC workflows. Lead routing rules, follow-up sequences, task automation. This is where your CRM vendor's implementation team earns their fee. A common mistake is going live with default templates and default sequences. They're generic and they don't reflect how your BDC actually works. Take the time to build the sequences your team will actually follow.

Week 9–10: Live launch and monitoring

The integration goes live. For the first two weeks, someone needs to check the sync logs daily. Watch for: deals that close in CDK but don't update in the CRM, new customers that don't flow over, RO records that aren't syncing. These issues are common in the first weeks and easier to fix when caught early.

Week 11–12: Reporting validation

Pull a CRM report and a DMS report for the same time period. Compare sold units. If the numbers don't match, find out why before you trust any of the attribution data. Per research from RingLead's 2026 Canadian automotive CRM comparison, the average dealership close rate is around 12%. If your CRM is showing 25% or 4%, something in the integration is off.

The Harvard Business Review research cited in the same RingLead study found that leads contacted within five minutes are 21 times more likely to be reached successfully than leads contacted after 30 minutes. That's a BDC process point, but it's also an integration point: if your CRM isn't receiving leads from your website and DMS in real time, your BDC is already behind before they pick up the phone.

The Multi-Rooftop Problem: When Integration Costs Multiply

Single-rooftop dealers have one integration project. Dealer groups have a different problem entirely.

If you're running five stores and they're split between CDK Drive and PBS, you have two separate integration projects, two sets of monthly fees, and two different data models to reconcile at the group level. If you add a Reynolds store through an acquisition, you have three.

Here's the worked math on what that looks like. Using midpoint estimates from the ranges above:

CDK Drive integration (2 stores): CA$16,250 one-time + CA$650/month per store = CA$16,250 setup + CA$1,300/month ongoing
PBS integration (2 stores): CA$12,500 one-time + CA$525/month per store = CA$12,500 setup + CA$1,050/month ongoing
Reynolds Ignite integration (1 store): CA$20,000 one-time + CA$1,000/month = CA$20,000 setup + CA$1,000/month ongoing

Total for a five-store group with mixed DMS: roughly CA$48,750 in one-time integration costs, plus CA$3,350 per month in ongoing integration fees. That's before your CRM subscription, before your DMS subscription, and before any CDP or marketing automation layer.

That number surprises a lot of dealer principals. It shouldn't. Integration is infrastructure, and infrastructure costs money. The question is whether you're getting value from it. If your CRM is attributing deals accurately, your BDC is working clean data, and your service retention campaigns are hitting the right people at the right time, CA$3,350 a month is a reasonable cost. If your data is still a mess and your managers don't trust the reports, you're paying for infrastructure that isn't working.

For dealer groups specifically, the cross-rooftop customer journey problem is worth understanding before you build the integration. A customer who submits a lead to your Chevrolet store and then walks into your Buick store down the street should show up as the same person in your CRM. Most CRM–DMS integrations don't solve that on their own. That's where attribution and CDP thinking comes in. For a deeper look at that problem, see our article on cross-rooftop attribution for Canadian dealer groups.

And if you're comparing which CRM platform handles multi-rooftop integration best across VinSolutions, DealerSocket, and Salesforce, that comparison lives in our VinSolutions vs DealerSocket vs Salesforce breakdown.

Red Flags to Watch Before You Sign the Integration Contract

This is the close that actually matters for this article. You're evaluating a CRM–DMS integration. Here's what to watch for.

The vendor says "yes we integrate" without specifying what's included. Ask for a written data dictionary: which objects sync, in which direction, at what frequency. "We integrate with CDK" and "we sync customers, deals, ROs, and F&I products bidirectionally every 15 minutes" are very different statements.

Integration fees are buried or absent from the initial quote. Some CRM vendors quote the CRM subscription and then add DMS integration fees later. Get the full monthly cost in writing before you sign.

No mention of write-back. Read-only integrations pull data from the DMS into the CRM. Write-back pushes data the other direction. If your CRM can't close an opportunity when a deal posts in the DMS, your reports will never be accurate. Ask specifically: "When a deal is posted in [DMS], does the CRM opportunity close automatically? How long does it take?"

No test environment or data quality review before go-live. Any integration worth paying for includes a test phase. If your vendor wants to go live immediately without validating the data, that's a problem.

No clarity on who supports the integration when it breaks. The CRM vendor will point to the DMS vendor. The DMS vendor will point to the CRM vendor. Before you sign, get a written answer: who is the single point of contact when the sync stops working on a Friday afternoon?

CASL consent fields aren't part of the integration scope. If your DMS stores transaction dates and your CRM needs those dates to calculate implied consent expiry, that field needs to be in the integration. Ask about it explicitly.