Most CRM projects do not fail because the company picked the wrong software. They fail because the team copied its spreadsheet into a new tool, added fifty fields, imported dirty data and then told salespeople to start using it on Monday. Six months later, nobody trusts the reports, and leadership starts looking at a different CRM. This plan gives you a practical 90-day structure that works whichever system you use, whether HubSpot, Zoho, Salesforce or another. If you are still choosing, begin with our comparison of [HubSpot and Zoho CRM](/compare/hubspot-vs-zoho-crm). For cost, see the [HubSpot](/insights/hubspot-implementation-cost-india) and [Zoho](/insights/zoho-crm-implementation-cost-india) guides.
What should you agree before a CRM implementation starts?
Write down the decisions the CRM must support. If you begin with features, you will build everything and use little of it. Good questions to answer in a one-page brief:
- What decisions should leadership be able to make from this data?
- What should a salesperson get out of using it each day?
- Which three to five reports matter on day one?
- Who owns the system after go-live?
- What is the budget, including licences, implementation and future admin time?
- What will the CRM replace? Name the spreadsheets and tools being retired.
Then appoint three people: an executive sponsor who can enforce adoption, a project owner with time to do the work and a sales representative who can tell you what is unrealistic. If nobody has protected time, the project will slip, however good the plan is. Be careful not to make a salesperson the project owner on top of a full quota. That rarely ends well.
Read the transcript
The lead came in at 9:02. Nobody called. You paid for that enquiry. It should not depend on someone checking a sheet.
Leads sit in inboxes, sheets and phones. Nobody is sure who should call. By the time someone does, the buyer has moved on.
Leads should not rely on someone remembering.
Every lead lands in one CRM. Routing and first contact happen automatically. Reps get a clear next step instead of a chase.
CRM and automation, with Rahul D Sarker. Book a call at rahuldsarker.co.
What does a 90-day CRM implementation plan look like?
The timeline assumes a team of about 5 to 50 users and a fairly standard B2B process. Larger or more complicated setups will take longer, particularly with custom integrations or strict compliance needs.
| Phase | Weeks | Main work | Done when |
|---|---|---|---|
| 1. Discover | 1 to 2 | Map the current process, reports and data sources | Brief and process map signed off |
| 2. Design | 3 to 4 | Stages, required fields, ownership rules, permissions | Design document agreed by sales and marketing |
| 3. Build | 5 to 7 | Configure pipelines, automation, templates, dashboards | Test scenarios pass |
| 4. Migrate | 6 to 8 | Clean, map and import data, test integrations | Sample records checked by users |
| 5. Pilot | 9 to 10 | A small group uses it for real work | Issues fixed, pilot group willing to continue |
| 6. Roll out | 11 to 12 | Training, go-live, retire old tools | All users active, and old sheets closed |
| 7. Stabilise | 13+ | Weekly adoption checks and fixes | Reports trusted in leadership meetings |
Weeks 1 to 4: discover and design
Start with what happens today. Sit with salespeople, marketers and whoever handles customers after the sale. Trace how a lead arrives, who gets it, what happens at each step and where things fall through.
Then design the smallest system that supports your process:
- Pipeline stages. Each stage should describe a buyer action or a verified fact, not a seller's hope. Use stage exit criteria, so that everyone understands them the same way.
- Required fields. Start with a short list. Our guide on CRM fields that predict revenue can help you choose. Every extra field reduces data quality in others.
- Ownership and routing. Who gets which lead, and what happens when they do not respond?
- Lifecycle definitions. What is a lead, a marketing-qualified lead, a sales-qualified lead, an opportunity and a customer?
- Permissions. Who can edit, delete, export or see what?
Record all this in a data dictionary. Get sign-off from sales and marketing leaders. Changing the design at this stage costs a conversation. Changing it after the migration costs weeks.
Weeks 5 to 8: build and migrate
Configure the system according to the design, and resist adding extras along the way. Keep a "version 2" list for good ideas.
Build in this order: users and teams, objects and fields, pipelines, routing, a few essential automations, email templates and dashboards. Test each with realistic scenarios, such as a duplicate lead, a lead with no owner or a deal that moves backwards.
Plan the migration carefully:
- Decide what to bring. Old, unusable records add noise. A common approach is to migrate active deals, customers and recent contacts, and archive the rest in a safe, accessible place.
- Clean before you import. Deduplicate, standardise country and phone formats, and fix company names.
- Map the fields. Each source column gets a home, or a decision to drop it.
- Preserve history that matters. Original lead source, created date, activity history and owner.
- Do a trial import. Bring in a small sample, and let users check it.
- Check consent. Do not move people who have opted out into new marketing lists. See our DPDP note for India.
If you are moving between systems, our Zoho to HubSpot and Salesforce to HubSpot checklists have detail specific to those platforms.
Connect only what you need first
Integrations are where projects often overrun. Rank them by importance and connect the essential ones before go-live. Everything else can wait.
Usually essential at launch:
- Website forms and lead sources, with UTM and source data kept intact.
- Email and calendar sync, because reps will not log activity by hand.
- Calling, if your team sells by phone, so calls are recorded automatically.
- WhatsApp, in many Indian sales teams, because conversations there otherwise vanish. See HubSpot WhatsApp integration as one example.
- Ad lead forms, such as Meta lead ads, along with IndiaMART where relevant.
Usually able to wait: billing and accounting, data enrichment, product usage data and advanced reporting tools. These add a lot of value later, but they should not hold up a basic rollout.
Test integrations with real examples, including failure cases. Decide which system holds the master record for each piece of data, or two tools will keep overwriting each other. Name somebody who gets alerted when an integration fails.
Weeks 9 to 12: pilot and roll out
Pilot with a small group of real users for about two weeks. Include at least one sceptic: if they can use it, others can. Ask them to work live deals only in the CRM during this period. Daily 15-minute feedback calls find problems quickly. Fix what blocks work, and move everything else to the version 2 list.
For the wider rollout:
- Train by role, not by feature. A rep needs to know how to manage their day. A manager needs to know how to inspect a pipeline.
- Use their own data in training. Generic demos do not stick.
- Provide short guides. One page and a two-minute video for each common task.
- Set a hard cut-off. Choose a date after which old spreadsheets close. As long as both exist, people will use the old one.
- Run a stand-in support hour. A daily help slot for the first two weeks reduces frustration.
- Have leaders use it in meetings. If the sales manager runs pipeline reviews from the CRM, adoption rises very quickly. If they ask for a spreadsheet, it collapses.
Adoption is the real go-live
A CRM is not live until people rely on it. Our article on why reps do not update the CRM deals with the causes. In practice, measure these weekly for the first few months:
- Active users compared with licences.
- Deals without a next step or close date.
- Leads with no first activity within the agreed response time.
- Required field completion by rep.
- Stale deals with no recent activity.
- Records created outside the agreed process.
Make the CRM useful for the rep as well as for management. Automate activity logging, reduce typing, surface the next action and remove fields nobody uses. Then make it non-optional: pipeline reviews, forecasts and commission calculations should all draw from the system. If a deal is not in the CRM, it does not exist for review purposes.
Share progress openly, and praise good usage. Also ask what is annoying, and fix something visible each week. People forgive a new system quickly when they see their feedback change it.
What are the most common CRM implementation mistakes?
These appear again and again:
- Treating it as an IT project. The CRM reflects how you sell. Sales leadership needs to own it.
- Automating a broken process. Fix the process first, or you will just create errors faster.
- Too many fields and stages. Start small. You can add fields more easily than you can get people to care about them.
- Importing everything. Bad data lowers trust from day one.
- Leaving out customer success. If renewals matter, include them, or plan when you will.
- No owner after launch. CRMs decay without care. Someone needs regular time for admin, fixes and change requests.
- Ignoring reporting until the end. Decide on the reports first, and work backwards to the fields you need.
- Heavy customisation early. Stay close to the standard product where possible. It makes upgrades and hiring easier.
If your rollout has already gone wrong, a clean-up may be better than a fresh start. Our CRM cleanup ROI calculator helps you estimate the case, and CRM consulting covers outside help.
FAQ
Many small and mid-sized B2B teams can complete a first version in about 90 days. Very simple setups may take weeks, while complex setups with many teams or integrations may take several months. A smaller first release reduces risk.
Internal teams can manage a simple setup if someone has protected time. A consultant helps most with process design, migration and integrations, or when nobody internally has done this before. Either way, an internal owner must remain after go-live.
Migrate active deals, customers and recent contacts with their important history. Archive the rest somewhere safe. Check your privacy and retention duties before keeping or deleting data, and do not re-add people who have opted out.
Look at active usage, complete and up-to-date records, whether leadership uses CRM reports in meetings, lead response time and forecast accuracy. Revenue effects take longer to show and are often influenced by other factors.