How do I unify DMS, CRM and service data at a car dealership?
Start by confirming in writing that the dealership has the right to access and export its data from every system, then move that data on a schedule into one warehouse or lakehouse the dealership controls. Match customers and vehicles across systems, clean duplicates, and give managers one place to ask questions, instead of reconciling separate reports from each vendor.
Step 1: Inventory every system that holds dealership data
Most stores run 15 or more systems. List each one, what it holds and who the contract owner is.
- DMS: deals, repair orders, parts, accounting
- CRM: leads, contacts, tasks, communications
- Service scheduling, F&I menus, inventory, websites, ad platforms, phone tracking and payroll
Step 2: Confirm who owns the data and how you get it out
Dealers generally treat customer and transaction data as dealership data, but the practical answer depends on each vendor agreement. Read the data access, export, fees and termination sections. Ask each vendor for the supported method (API, scheduled export or certified integration), the fields included, how often it runs and what it costs.
Step 3: Put data access in every contract
Before you sign or renew, ask for these terms in writing.
- The dealership's right to access and export its data at any time
- Export formats and frequency, with no extra fees for routine access
- Access to data for a defined period after termination
- Clear limits on how the vendor may use or resell dealership data
- Security obligations that support your FTC Safeguards Rule program
Step 4: Land everything in one place you control
Move each source into a single warehouse or lakehouse owned by the dealership. A lakehouse keeps raw history and the cleaned, modeled tables together, so you can answer new questions later without re-pulling data from vendors.
Step 5: Match customers and vehicles across systems
The same customer appears differently in the DMS, CRM and service system. Match on combinations of name, email, phone, address and VIN, and keep a record of every merge so it can be reviewed. Customer contact data goes stale quickly as people move and change phones, so schedule matching and cleanup as an ongoing job, not a one-time project.
Step 6: Make it usable by managers, not just analysts
Unified data only pays off when the GM, service director and F&I manager can get answers quickly. That can be dashboards, but increasingly it means asking questions in plain English and getting an answer drawn from every department at once.
Ways to unify dealership data
- Approach: DMS vendor reporting. Best for: Single-system reporting. What to check: Coverage of non-DMS sources and export rights
- Approach: Automotive CDP. Best for: Marketing audiences and campaigns. What to check: Departments covered beyond customer data, and data ownership terms
- Approach: Build your own warehouse. Best for: Groups with a data team. What to check: Connector upkeep, staffing and time to value
- Approach: Dealer-owned data platform (for example QoreVault or QoreCloud). Best for: Whole-store data the dealership owns. What to check: Supported sources, deployment time and pricing
- Automotive data warehouse guide
- Dealer data addendum
- Data rights
- QoreVault
- FTC: Safeguards Rule, what your business needs to know Requirements for protecting customer information, including oversight of service providers.
- Fortellis asynchronous API concepts Example of dealer consent through access grants in a DMS integration context.
- Fullpath Help Center: Identity Resolution and Merge Rules Example of how a dealership CDP matches and merges customer records.
Frequently asked questions
How do I unify DMS, CRM and service data at a car dealership?
Start by confirming in writing that the dealership has the right to access and export its data from every system, then move that data on a schedule into one warehouse or lakehouse the dealership controls. Match customers and vehicles across systems, clean duplicates, and give managers one place to ask questions, instead of reconciling separate reports from each vendor.
Who owns dealership customer data, the dealer or the DMS vendor?
Treat it as dealership data, and confirm it in each vendor agreement. The contract's access, export and termination terms decide what you can do in practice.
How do I get my data out of my DMS?
Ask your DMS provider which access methods your agreement supports, such as an API program, certified integration or scheduled export, and what fields and fees apply. Get the answer in writing.
How do I clean duplicate customer records in a dealership CRM?
Match records on several fields together (name, email, phone, address, VIN), merge with a reviewable log, and run it on a schedule because contact data keeps changing.
How do dealerships stay compliant with the FTC Safeguards Rule when using AI?
Treat AI tools like any service provider with access to customer information: include them in your written security program, limit access, require security commitments in the contract and monitor them. See the FTC's guidance linked below.
What does QoreAI offer for this?
QoreVault is a dealer-owned data foundation and QoreCloud adds plain-English intelligence across every department. QoreCloud is $3,000 per rooftop per month for the platform, plus $400 per rooftop per month for data movement and a one-time $5,000 setup. Month-to-month from day one. QoreVault is $1,000 per rooftop per month for the data foundation, plus $400 per rooftop per month for data movement, totaling $1,400 per rooftop per month at list price. One-time $5,000 setup per rooftop. Month-to-month from day one. 60-day deployment standard. SOC 2 Type II examination in progress.