CRM & sales process
Technology Transitions: Is Your Team Ready to Switch CRM Systems?
How to switch dealership CRM systems: old-contract notice terms, a data-export checklist, field mapping, a parallel run, cut-over day and the first 30 days.
Quick answer
To switch dealership CRM systems, start with the old contract's notice date, then test a full data export, clean and map your fields, run both systems briefly, and cut over on a quiet day with every lead source re-pointed and tested. Carry opt-outs across, and get written confirmation that the old vendor deletes your data.
When this post first ran in January 2020, it said the hardest part of a technology change is getting the sales team on board. That is still true, and we cover it elsewhere. This rewrite covers the switch itself. A team that is ready for a new CRM can still lose a month of follow-up to a missed notice date, an export without the notes, or a lead source nobody re-pointed.
This guide is for the dealer principal, GM, sales manager or BDC lead moving to a new CRM. If you are still choosing, start with how to choose a powersports CRM, because the questions you ask before signing decide how hard this switch, and the next one, will be. If you are leaving an all-in-one system, decide first which jobs you are replacing; our guide to DX1 alternatives shows how for DX1, and our guide to leaving DP360 for another CRM does the same for a CRM-to-CRM move.
Start with the old contract, not the new demo
The date that drives the whole project is in the contract you already have. Pull it out before you sign anything new and find:
- The term and renewal clause. Does it renew automatically, and how many days before renewal must notice be given? Put that date in two calendars.
- How notice must be given. Some contracts require written notice to a specific address; a call to your rep may not count.
- Early termination terms and fees.
- Data ownership and export: who owns the data, what the vendor must hand over, in what format, how fast and at what cost.
- After termination: how long your data stays available, and when and how it is deleted.
- Phone and text numbers. If the vendor supplied them, find out whether you can take them with you.
If the export terms are vague, ask for a sample export now, while you are still a customer with leverage, and write the exit terms you wish you had into the new contract.
What most switching guides miss
The leading articles on this topic, which we read before writing, cover vendor selection, training and "migrate your data." None deals with the parts of a CRM that are not records in a table, and those are what break on day one:
- Phone and text numbers. Customers reply to the number they already have. If that number dies with the old contract, their replies go nowhere.
- Lead-source plumbing. OEM, marketplace, website and chat leads each arrive through a connection set up in the old CRM. Every one must be re-pointed and tested.
- Opt-outs and consent records. Under the FCC's rules, a customer can revoke consent to covered calls and texts by any reasonable means, and a revocation must be honored within a reasonable time "not to exceed ten business days." An opt-out stranded in the old system does not stop that clock.
- Open work. Future appointments, open tasks and live deals need an owner in the new system before the old one goes dark.
- The old copy of your data. The old vendor still holds your customers' information after you leave. Getting it securely deleted is part of the switch.
The data-export checklist
Ask for each item below, and open the files yourself. An export is only complete when someone has checked it.
What to ask for
- Every contact, including inactive and sold customers, each with the old system's unique ID
- Leads and opportunities with source, status, created date, last activity and assigned salesperson
- Notes and activity history with the original date, time and author
- Text message and email history, linked to the customer ID
- Call logs and call recordings, with an index that ties each audio file to a customer and date
- Appointments, past and future, and open tasks
- Consent and opt-out records for text, email and calls, with dates and source
- Units of interest, trade details and purchased units with VIN or stock number
- The user list, so old salesperson names can be mapped to new owners
- Attachments, if any, handled as sensitive files
How to ask for it
- One file per record type, in CSV or another format your new CRM can import, with IDs that link the files together
- A data dictionary that explains each field and each status value
- Delivery by a secure transfer method, not as an email attachment
- A sample export now, a full export before cut-over, and a final "changes since" export on cut-over day
- The cost, if any, and the turnaround time, in writing
Custom reports, dashboards, automations and templates usually will not move. Screenshot them, and save the last 12 months of key reports as a baseline.
Clean and map before you import
Dirty data moved into a new CRM gives you the same problems in a new system. Clean first, then map every field on purpose.
Clean
- Merge duplicates. One rider with three records gets three follow-up sequences. See finding and merging duplicate customer records.
- Standardize phone formats, emails, state codes and split names.
- Decide what not to move, such as test records and leads with no contact method. Keep every opt-out as a suppression record even if the rest is left behind.
- Build the standard in. The data quality standards for your dealership CRM set the required fields and dispositions for day one.
Map
Build a mapping sheet with your new vendor. Every old field gets a destination or a deliberate "do not import."
| Old system field | New CRM field | Rule |
|---|---|---|
| Full name (one field) | First name, last name | Split automatically; review the ones that fail |
| Phone 1, 2, 3 | Mobile, home, work | Format to 10 digits; mark mobile only where known |
| Lead status (many custom values) | Stage (fewer values) | Map each value; record the reason for lost deals |
| Salesperson | Owner | Departed staff go to a manager, not to nobody |
| Text opt-out flag | Text consent: revoked | Must map; never drop |
| Vehicle of interest (free text) | Unit of interest | Keep the text; link a stock number where possible |
| Notes | Activity history | Import with the original date and author |
Run a trial import of a few hundred records and have a salesperson and a manager look up customers they know. If a record looks wrong, fix the mapping before the full import.
The switch timeline
This is our recommended sequence for a single store; dealer groups should add time per rooftop. Count backwards from the old contract's notice date, not forwards from the new vendor's go-live offer.
| When | Workstream | What gets done |
|---|---|---|
| Weeks 12 to 10 before cut-over | Contract and lead | Read the old contract, diary the notice date, name a project lead, request a sample export |
| Weeks 10 to 8 | Decision | Choose and sign the new CRM, with export and exit terms in writing |
| Weeks 8 to 6 | Data | Full export received and opened; mapping sheet drafted |
| Weeks 6 to 4 | Build | Users, routing, templates, stages; cleanup done; number transfer requested |
| Weeks 4 to 2 | Test and train | Trial import; a test lead from every source; role-by-role training |
| Weeks 2 to 0 | Parallel run | New leads worked in the new CRM; old CRM kept for lookups and open deals |
| Cut-over day | Switch | Final export and import; every lead source and number confirmed |
| Days 1 to 30 | Stabilize | Daily and weekly checks (below) |
| After day 30 | Close out | Old access ends; deletion confirmed in writing |
Give notice once the new CRM has passed its test leads, but never later than the notice date. If the two collide, ask the old vendor for a short month-to-month extension rather than rushing.
Run both systems briefly, then cut over
A short parallel run lets the team learn on real leads while the old CRM still holds the history. Set one rule: from day one of the parallel run, every new lead is worked in the new CRM. The old system is for lookups and deals already in progress. Two systems of record means notes in both and follow-up in neither.
Pick a quiet cut-over day: for most powersports stores, the off-season, clear of the spring rush and event weekends, and midweek rather than a Saturday.
Cut-over day, step by step
- Freeze the old CRM at a set time and pull the final "changes since" export.
- Import the final changes and spot-check a dozen records from that week.
- Re-point every lead source, then send a test lead from each and confirm it arrives with the right source and owner.
- Switch or forward the phone and text numbers, then test an inbound call and a two-way text.
- Confirm the opt-out list is loaded and suppression is on before any automated message goes out.
- Assign every open appointment, task and deal to a named owner.
- Hold a short floor meeting, and name one person the team can grab for help all day.
- Close the day with a count: leads received today, by source, compared with the same weekday last week.
What to tell customers, if anything
Most customers never need to know you changed software. Tell them only when something they see changes:
- A new texting or calling number. If you can, tell the customers you are actively working, from the old number, before it goes.
- Appointment reminders or service messages from a new sender.
- Links in old emails that will stop working.
Do not send a "we have a new system" blast to your whole database. Texting it to people who opted out, or never gave consent, creates the very problem the switch should avoid. See texting powersports customers the right way before any message goes to a list. This is general information, not legal advice.
The first 30 days
| Period | Check | Fix if you see |
|---|---|---|
| Days 1 to 7, daily | Leads by source vs. the same week last year or last month | A source at zero: re-test its connection that day |
| Days 1 to 7, daily | Every new lead has an owner and a first response | Routing gaps or unassigned leads |
| Week 2 | Notes and dispositions on worked leads | Salespeople keeping notes on paper or in the old system |
| Week 2 | Customer replies to texts and calls | Replies going to the old number |
| Week 3 | Key reports against your saved baseline | Gaps that point to a mapping error |
| Week 4 | Open issues list, team feedback | Workarounds that should become settings |
| Day 30 | Old system read-only access | Anything still only in the old CRM |
Keep one issues list with an owner and a date for each, and review it with the new vendor weekly.
Keep the team with you through the switch
The original post asked whether your team is ready. Three things keep the mechanics from wearing them down:
- Do not change the sales process in the same month. If stages, dispositions and pay plans change with the software, nobody can tell which change caused a problem.
- Give each role its own first week. Salespeople need capture, texting and next actions; managers the stalled-deal view; the BDC routing. See the role-by-role CRM training plan.
- Answer doubters with the plan. The rollout plan for overcoming resistance to sales automation and getting salesperson buy-in for a new CRM cover the people side.
Salespeople will also ask which tools they will use every day; the sales tools a powersports salesperson needs in 2026 is a good handout.
Your old data: oversight and secure disposal
A CRM vendor holding your customers' information is a service provider. For businesses covered by the FTC Safeguards Rule, 16 CFR 314.4(f) requires overseeing service providers by "taking reasonable steps to select and retain service providers that are capable of maintaining appropriate safeguards," "requiring your service providers by contract to implement and maintain such safeguards," and periodically assessing them. The same section requires procedures for change management (314.4(c)(7)), encryption of customer information in transit over external networks and at rest (314.4(c)(3)), and secure disposal of customer information "no later than two years after the last date the information is used" for the customer, with exceptions such as information needed for business operations or required by law (314.4(c)(6)(i)).
In practice: put security and deletion terms in the new contract; keep export files encrypted in one known place and delete working copies once the import is checked; get the old vendor's written confirmation of what it deleted and when, including backups; and record what you kept and why.
Whether the rule applies to your store depends on your activities, so ask your attorney. This is general information, not legal advice.
If PSX Ascend is on your list, our AI-powered powersports CRM connects customers across phone, text and email, records and tags every inbound call (and every outbound call where state law permits) in the customer record, and shares vehicle context with AI inventory management. Ask us the same export, mapping and contract questions you would ask anyone.
You can also see the same AI-powered powersports CRM on our sister site, PSXDigital's AI-powered powersports CRM page.
