A CRM implementation can go wrong long before anyone logs in. The usual story is a team that buys the software, configures it in a week, imports a spreadsheet and then wonders why reps keep working out of their inboxes. The tool was never the problem. Nobody decided what the system was for, so it was set up to be a place to put things.
This guide lays out a four phase framework for implementing a CRM, with the decisions each phase needs and a clear test for when it is done. It applies to any platform. Where we use examples from the field, they come from HubSpot, because that is the system we build in as a
HubSpot Platinum Solutions Partner.Read it as a planning document. If you work through the questions in order, you will know what you are asking an implementation partner to do, or what you need to do yourself, before anyone is paid to start.
CRM implementation is the process of planning, configuring, populating and adopting a customer relationship management system so that it matches how your business really sells and serves customers. It covers the software setup, the data that goes into it, the connections to your other tools and the training that makes people use it.
That definition is wider than most vendor pages suggest. Many treat implementation as account setup: create the users, add the fields, import the file. Setup is real work, but it sits inside a larger project. If a company skips the planning and the adoption, it ends up with a configured system and the same process problems it had before.
It also helps to separate implementation from the work that comes after it. Implementation ends when your team can run the system without outside help. Ongoing administration, such as new properties, new reports and user changes, is a separate job. If you have not decided who owns that job, our guide to
CRM administration is a good place to start.Discovery is where you find out what the CRM has to do. The goal is a short, honest description of how revenue works in your company today, written by the people who do the work and not by the people who bought the software.
Talk to the users, not only the managers. A rep who keeps notes in a notebook is telling you what the system needs to replace. Ask what they would stop doing if the CRM worked.
Done when you have a one page statement of goals, a named owner for each area of data, and a list of the teams and integrations that are in scope for the first release.
On our own HubSpot onboarding, this phase is a kickoff with a dedicated strategist who learns the business and the goals. You can see how that fits into the rest of the work on our
HubSpot onboarding page.Strategy and mapping turns the goals into a design. You decide what the system will track, how records relate to each other and where each piece of existing data will land. This is the phase that prevents the expensive rework later.
Migration is its own decision. For each source, whether that is a spreadsheet, an old CRM or a quoting tool, decide what to move, what to archive and what to leave behind. Merge duplicates, standardise names and delete records that have no value. Then write a mapping that says which source column feeds which new property.
If you are moving between systems, plan a test import with a small sample and check it by hand before you load everything. Our
data hygiene checklist covers the cleaning work, and our migration service is there for teams that would rather not do the move alone.Done when there is a written data model, a signed off pipeline definition and a field-level mapping for every source you plan to import.
Now you configure. Because the design is on paper, the build becomes a matter of carrying it out in order, and each piece can be reviewed against the plan.
Resist the urge to automate everything at once. Automation built on an untested process spreads mistakes faster than a person could. Release the build in stages and have a small group of real users try each stage before it reaches everyone.
Starting from a proven build also saves time. For HubSpot, our
fixed-price HubSpot build clones a tested setup of pipelines, workflows and dashboards into your portal and then tailors it, so you are not designing every list and report from nothing. We have configured 315+ HubSpot portals.Done when every item in scope is built, each integration passes a test with live data and a pilot group has used the system for their real work.
This is where many implementations stall. The system is configured, the launch email goes out and within a few weeks reps are back in their old habits because nobody made the new way easier than the old one.
Then measure against the outcomes you wrote in Phase 1. If you said every deal should have a next step, report on it. If renewals should be visible ninety days out, build the view and check it monthly. A goal that is not measured gets forgotten.
For a sense of what a full plan looks like in practice, see our
HubSpot onboarding implementation checklist, and for the usual causes of a stalled rollout, read why most HubSpot implementations fail.Done when the owners of each area can run the system without outside help, the old tools are retired and the first report against your goals has been reviewed by leadership.
You have three realistic options, and the right one depends on how much experience your team has with the platform and how much time it can give.
If you are still deciding, our comparison of a
consultant, an agency and a solutions partner sets out the trade-offs, and our HubSpot consulting page describes when a consultant is the better fit. For budgeting, see what HubSpot onboarding costs and our pricing.Whichever route you take, judge the proposal by the hand-off. A good implementation ends with your team able to run the system, a written record of how it is set up and a plan for what comes next. If you want help scoping yours, you can
book a call with Shawn and we will map the four phases to your business.CRM implementation is the work of planning, configuring, populating and adopting a CRM so it fits how your business sells and serves customers. It includes setup, data migration, integrations and training, and it ends when your team can run the system on its own.
It depends on how many teams, data sources and integrations are in scope. A focused rollout for one sales team is far shorter than a company-wide migration. On our own HubSpot onboarding, guided implementation runs about four to six weeks after kickoff and planning, and a wider build takes longer. Ask any provider for a timeline tied to specific phases and sign-offs.
Cost follows scope: the number of users, the amount of data to clean and move, how many integrations you need and how much training your team requires. Ask for a fixed price with a stated scope, so extra hours are agreed in advance. Our onboarding cost guide explains what to expect on HubSpot.
Skipping discovery, copying dirty data into the new system, automating a process nobody has tested and treating training as a single session at launch. Each is avoided by the phase it belongs to: decide first, clean the data, release in stages and keep measuring adoption.
Choose in-house if someone on your team has done this on the same platform and has protected time. Choose a partner if you need a repeatable method, broader coverage across strategy, build and training, or a faster path to a working system. In both cases, insist on a written hand-off.
Yes, if you release in stages. Build in a test environment or a controlled pilot, move a small group of users first and set a cutover date for everyone else. Keep the old tool read-only for a short period so nobody loses history.