Change Management: The Guide to Getting Your CRM, ERP or AI Project Actually Adopted
Change management is the set of actions that let your teams genuinely take ownership of a new tool or process — a CRM, an ERP, an AI agent — instead of working around it once the vendor has left. Without it, a technically successful project can end up dead on arrival: an under-used tool, poorly entered data, a return to old habits within a few weeks. At turnK, adoption isn't a side step in the project: it's the obsession that shapes our method, from scoping through to post-launch support.
Change management: what does it actually mean in a CRM, ERP or AI project?
Change management brings together the communication, training, user involvement and follow-up that accompany the rollout of a new tool. In a CRM integration project, an ERP project or a Data/AI project, the goal isn't just to deliver a solution that works technically: it's making sure sales reps log their opportunities, finance teams close the books reliably, and employees actually use the AI agent instead of going back to a spreadsheet.
That's a different challenge from training alone. You can train teams on a tool and still never get lasting adoption, if the project hasn't addressed resistance, perceived workload, or the lack of a visible executive sponsor beforehand.
Why adoption fails even when the technical project succeeds
Most adoption failures don't come from a technical flaw in the tool, but from a flaw in how the change itself was managed. For an IT department running several projects in parallel, this risk is amplified by the starting state of the information system.
A fragmented IT landscape that complicates every new project
When the IT landscape is made up of siloed tools and fragile integrations built up over the years, every new project inherits technical debt and the wariness of users burned by previous, poorly supported rollouts. Change management then has to work with that history, not just with the new tool.
A project designed around the tool, not the use case
Many IT projects are scoped around the features to deliver, rarely around the target use cases and the operational pain points to solve. The result: a functionally complete tool that's poorly aligned with teams' daily work, who find it quicker to keep doing things the old way.
The levers behind effective change management
Effective change management rests on a handful of concrete levers, activated from the scoping phase onward — not just at go-live. Here are the ones we rely on across our projects, whatever the domain — CRM, ERP or Data/AI.
- A visible executive sponsor, who champions the project publicly and arbitrates resistance.
- A diagnosis of real usage before configuring the tool, so existing pain points aren't reproduced.
- Contextualized training, built around each profile's daily tasks rather than a generic user manual.
- Post-launch support, in the weeks following go-live, when old habits creep back fastest.
- Adoption metrics tracked over time — real usage rate, quality of entered data — not just a login rate.
Answering IT leaders' number-one fear: disrupting the business during the project
This is the most common objection from IT and Transformation leaders: a modernization project, however necessary, risks slowing down the business for months and pulling in teams that are already stretched thin. It's a legitimate concern, especially on an IT landscape where several projects already overlap.
The answer lies in the method more than the technology: break the project into stages, migrate by scope rather than in a single big bang, and build change management into every stage rather than bolting it on at the end. Across our projects, this approach typically delivers implementation in around 3 months instead of 6 — a shorter timeline that reduces the period during which teams have to work with both the old and the new system.
Change management in practice: CRM, ERP and AI, same principles, different weighting
On a CRM project, the adoption challenge mostly concerns sales teams: a poorly adopted CRM quickly shows up as an under-filled pipeline and unreliable forecasts, whether it's Salesforce or another tool on the market.
We cover the steps of a successful CRM project, from scoping through to sales adoption, principles that apply well beyond HubSpot.
On an ERP project, change management has to work with financial and logistics processes that are more rigid, where a data-entry error has a direct impact on the close or on stock levels; that's why choosing a partner able to secure every stage of the ERP project matters as much as choosing the tool itself.
On a Data/AI project, adoption ultimately comes down to trust: an AI agent or copilot only gets used day to day if teams understand what it does and stay in control of the output it produces.
How turnK structures adoption across its projects
We build our CRM, ERP, custom application and Data/AI projects across three phases — audit/scoping, production, support — where change management is present from the first phase, not added at the end. That's what lets your teams keep control of the tool once the project is delivered, instead of staying dependent on a vendor long-term.
At Horse Republic, the migration from Salesforce to HubSpot was built with this logic in mind: a supported tool change so sales teams could keep working without a break in their pipeline during the transition.
Where to start your change management plan
Before launching a CRM, ERP or AI project, take the time to answer three questions: who will be the visible internal sponsor of the project, which real-world usages need to change — not just which tools — and who will support teams in the weeks following go-live. These answers, more than the technology choice, will determine whether your project is actually adopted.
the most common questions
It's the set of communication, training and support actions that let teams take lasting ownership of a new tool or process, instead of reverting to old habits once the project is delivered.
Because a technically successful but poorly adopted tool creates no value: an under-filled pipeline, poor-quality data, workarounds. Change management is what turns a rollout into real usage.
It starts at scoping and continues for several weeks after go-live — this often-overlooked post-launch period is what determines whether good practices stick for good.
Login rate isn't enough: you need to track the real usage rate of key features and the quality of entered data over time, several months after rollout.
