Implementing a New CRM: How to Avoid Replacing Old Problems with a More Expensive System
A CRM should improve how your organisation manages customers, opportunities and commercial decisions. But if the project begins with software rather than process, data and governance, the new platform may simply reproduce the weaknesses of the old one.
A new CRM promises genuine improvement
A well-implemented CRM can deliver better pipeline visibility, more accurate forecasting, improved sales management, stronger marketing attribution, more consistent processes, reduced reliance on spreadsheets and greater commercial accountability. These are real and achievable outcomes.
But the path from software selection to those outcomes is not straightforward. The software is purchased, the implementation partner is appointed and teams begin listing the fields, reports and screens they want. Much of the discussion is based on how people currently work. Historic processes are reproduced. Old data is imported. Exceptions become custom development.
The project goes live, but employees continue using spreadsheets because the CRM feels burdensome and the reports remain unreliable. The organisation has invested in a modern and more expensive platform that reproduces the weaknesses of the system it replaced.
The principles behind a successful CRM implementation are closely related to those that govern any major software selection. For the broader framework, see Why Software Selection Fails and How to Get It Right.
"The objective is not to implement a CRM. It is to improve how the business manages customer relationships and commercial activity."
Two Very Different CRM Starting Points
Organisations arrive at a CRM project from two very different positions, each with its own risks and requirements.
Common symptoms
Main risk
The organisation rebuilds the old CRM inside the new platform. Historic processes are reproduced, old customisations are recreated and the same adoption problems emerge within months of go-live.
The replacement is an opportunity to remove historic complexity, not to recreate it.
In both scenarios, the organisation must define how it wants to operate before choosing how the platform should be configured.
A CRM Is More Than a Database
A CRM sits at the centre of the organisation's commercial operating model, connecting people, processes and systems across every customer-facing function.
Do not begin by asking which CRM to buy
Platform demonstrations naturally focus on features: dashboards, AI capabilities, automated emails, opportunity stages, marketing journeys and forecasting tools. Features are not outcomes. A feature only creates value when it changes a business result.
Potential CRM business outcomes
"A feature only creates value when it changes a business outcome."
Define the outcomes required before reviewing platform demonstrations. This shapes the evaluation criteria and prevents the selection being driven by whichever vendor demonstrates most impressively.
Do not automate a process simply because it already exists
Documenting the current process is necessary. Reproducing it is not always appropriate. Before configuring any workflow, each existing process should be assessed against a set of direct questions.
Questions to ask about every current process
"How can the new CRM reproduce every step we currently perform?"
"How should this process operate if we were designing it today?"
Experienced users should be involved because they understand operational detail. However, familiarity with the old process should not give any one department an automatic veto over better practices.
A new CRM may require the business to change how it works
Different departments may currently use different sales stages, different definitions of a qualified lead, different account structures, different naming conventions and separate spreadsheets. A shared CRM requires a common operating model.
Where standardisation adds value
Where flexibility may remain appropriate
"The CRM should not preserve every departmental preference. It should establish the common commercial language the business needs."
Best practice does not mean every team must operate identically. It means variation should be deliberate, justified and governed.
Reliable reporting depends on shared definitions
Before configuring the CRM, the organisation must agree on the definitions that underpin every report, forecast and management decision.
"A CRM cannot create accurate forecasts from inconsistent definitions."
Sales stages should reflect an event in the customer's buying journey. For each stage, define entry criteria, exit criteria, required fields, expected actions, ownership and forecast probability where used.
Standard configuration should be the default
Configuration and custom development are not interchangeable. Understanding the difference matters for cost, risk and long-term supportability.
Configuration
Custom development
"Adapt the process to the platform where the standard process is sensible. Adapt the platform only where the business requirement genuinely creates value."
The partner delivering the project may not carry its long-term cost
The CRM vendor earns revenue from licences. The implementation partner earns revenue from consultancy, workshops, configuration, migration, integration, development, testing, training and ongoing support. This is a straightforward commercial arrangement, not a conflict of interest.
Many experienced partners actively challenge unnecessary complexity and can provide valuable process knowledge. However, the customer retains responsibility for deciding whether additional development creates sufficient long-term value. The organisation will support and maintain the outcome long after the implementation project has closed.
The licence price is not the cost of the CRM
Total cost of ownership extends well beyond the initial contract. Organisations that evaluate only the licence cost at selection often discover the full picture during or after implementation.
"The cheapest CRM at contract signature may not be the lowest-cost CRM over five years."
IT should be involved before the preferred platform is selected
IT involvement should enable the project, not obstruct it. Early engagement prevents expensive constraints from being discovered after the contract is signed. This is closely related to the broader governance principles covered in Is Your IT Strategy Supporting Your Business Strategy?
IT involved after selection
IT involved before selection
"Early IT involvement is not about giving technology teams a veto. It is about preventing expensive constraints from being discovered after the contract is signed."
Moving CRM data is not simply an export and import
Data migration should be treated as a separate workstream with its own planning, resourcing and testing. The same principles apply to any governed business-system migration, as discussed in Cloud Transformation Without the Leap of Faith.
Common data sources
Migration strategies
"Do not migrate low-quality data merely because it exists."
Data cleansing is not a one-off implementation task
Data quality is a continuous management responsibility. Without clear ownership and controls, the CRM trust cycle becomes self-reinforcing in the wrong direction.
Decisions to define
Controls that support quality
The CRM Trust Cycle
Connecting systems is easy. Defining ownership is harder.
A CRM typically connects to Microsoft 365, email, calendar, marketing automation, the website, finance, telephony, proposal tools, customer service, business intelligence, contract management and customer portals. For each integration, the organisation must define clear ownership and governance.
"Integration can distribute accurate information efficiently. It can also distribute inaccurate information more quickly."
Define the decisions before building the dashboards
Reporting should be designed around the decisions it needs to support. A dashboard cannot compensate for information the organisation never records.
A CRM contains some of the organisation's most valuable information
Customer contacts, commercial terms, sales opportunities, communications, relationship history, contract information, complaints, marketing consent and strategic account plans all require careful access control. For organisations considering AI features within the CRM, the governance principles in The AI Structure Every Business Should Adopt are directly relevant.
Easy access
Staff can reach the customer information needed for their role, quickly and without unnecessary friction.
Controlled access
Sensitive information is restricted to those with a legitimate need, monitored and reviewed regularly.
Training alone will not make employees use the CRM
Employees may resist a CRM for legitimate reasons: more mandatory information, greater activity visibility, loss of personal spreadsheets, standardisation, new approval processes, unclear personal benefit, poor usability or concern about performance monitoring. These concerns should be addressed, not dismissed.
"If management still asks for a separate spreadsheet before every pipeline meeting, employees will quickly learn that the CRM is optional."
Adoption is a leadership responsibility, not a training exercise. The CRM becomes the system of record when leadership treats it as the system of record.
A stable and adopted core is more valuable than an overambitious launch
Phased delivery reduces risk, improves adoption and allows the organisation to learn before committing to more complex capabilities. The correct phases depend on the business case.
A CRM should be tested through real business scenarios
Practical test scenarios
The implementation project ends. The CRM operating model does not.
Ongoing responsibilities
Going live is an output, not the outcome
Project measures
Business measures
"The CRM is successful when commercial performance and decision-making improve, not simply when the software is available."
Questions to Answer Before Selecting a CRM
If these questions cannot be answered, the organisation may not be ready to choose a CRM vendor.
The Five Foundations of CRM Success
How Wavex can support CRM governance
Wavex is not a CRM software vendor and does not approach the project with a commercial incentive to maximise licence sales or custom development. Wavex can help organisations treat CRM implementation as a controlled business-system change.
The aim is not simply to help the organisation select a CRM. It is to help ensure that the platform remains secure, supportable and valuable long after the implementation project has ended.
CRM implementation FAQs
A CRM should be judged by what it improves
A CRM should not be judged by the quality of its demonstration, the number of available features or whether the implementation reached go-live. It should be judged by whether it improves customer visibility, commercial decisions, sales consistency, data quality, forecasting, accountability, customer retention and organisational knowledge.
For organisations replacing an older CRM, the opportunity is to remove historic complexity rather than recreate it. For organisations implementing CRM for the first time, the opportunity is to introduce structure without creating unnecessary administration.
Both require leadership, process design, trusted data, technical governance and sustained adoption.
"Do not design the new CRM around how the organisation happened to work yesterday. Design it around how the business needs to operate tomorrow."
Related Insights
Further reading from the Wavex team.
Why Software Selection Fails and How to Get It Right
The principles behind selecting business software that delivers long-term value rather than short-term disappointment.
IT StrategyIs Your IT Strategy Supporting Your Business Strategy?
How to ensure your technology investments are aligned with your commercial goals and growth plans.
AI GovernanceThe AI Structure Every Business Should Adopt
A practical governance framework for organisations introducing AI tools, including CRM AI features.
Planning a new CRM or replacing an existing platform?
Before choosing the software, make sure your organisation has defined the future processes, data, controls, integrations and operating model required to make it successful.
Book Your Free IT Consultation
Speak with a sector specialist. No sales pitch - just an honest conversation about your IT challenges and how we can help.