How to Plan a CRM Implementation
Picture the Monday after you sign the CRM contract. Someone on your team asks where the leads from the trade show should go. Someone else asks whether a customer who bought twice is one record or two. A third person wants to know if the old spreadsheet can be thrown away. None of those questions are about software features, and none of them are answered by the vendor's onboarding video.
That is the real shape of a CRM implementation. The tool is a container. What goes in it, who maintains it, and what decisions it supports are choices you make before anyone logs in. If you are choosing a first CRM, the planning you do in the weeks before configuration will decide whether the system becomes the place your team lives or a monthly charge that nobody opens.
This guide walks through the planning in the order I would do it, with a 90-day schedule at the end. It assumes a small team, somewhere between three and thirty people, a mix of spreadsheets and inboxes as the current system, and a budget that cannot absorb a failed rollout.
Start with the question the CRM must answer
Before you compare products, write down five questions you want to answer in under a minute once the system is running. Examples that come up often in small firms.
- Which opportunities are likely to close this month, and what is the total value?
- Which customers have not heard from us in 60 days?
- Where do our best customers come from?
- Who owns this account, and what was the last thing we said to them?
- Which quotes went out and never got a reply?
If a question cannot be answered from data that someone will actually enter, it is a wish and not a requirement. Pruning the list now saves you from building fields that stay empty. Keep the final list to five to eight questions. Everything else in the plan exists to make those answers true.
Design the lifecycle before the fields
A lifecycle is the path a person or company takes from stranger to customer and beyond. Most CRM failures trace back to a lifecycle that exists only in the heads of the people who sell.
Draw it on paper first. A simple version for a services business might read like this.
- Contact. Someone you have a name and email for, with no conversation yet.
- Lead. Someone who has shown interest, such as filling in a form or replying to an email.
- Qualified opportunity. A conversation has confirmed need, budget range and a decision maker.
- Proposal. A written offer is out.
- Won or lost. A closed outcome, with a reason recorded.
- Active customer. Work is under way or the product is in use.
- Renewal or dormant. A future date to talk again, or a reason it is over.
For each stage, write an entry rule and an exit rule in plain sentences. "A lead becomes qualified when we have spoken by phone or video and confirmed a budget range and a timeline." The rule is more important than the label. If two salespeople would apply a stage differently, your pipeline report will lie to you, and you will not know why.
Keep the number of stages small. Five to seven is plenty. Every added stage is one more thing someone has to remember to update, and stale stages are the main reason forecasts drift.
Decide who can move a record and when
Some stage changes should be automatic, such as a deal moving to Proposal when a quote is sent. Others need a person. Decide which is which, and decide who is allowed to mark a deal as lost. Without this, the pipeline fills with deals that are quietly dead.
Objects and fields without the jargon
CRM software organizes information into objects, which are just types of record. The common ones are contacts (people), accounts or companies (organizations), deals or opportunities (potential sales), and activities (calls, emails, meetings, tasks). Some systems add products, quotes and custom objects.
The relationships matter more than the list. One account has many contacts. One account can have many deals over time. One deal may involve several contacts, and one of them is the buyer. If your business sells to households, you may treat the person as the account. If you sell to companies, keep the two separate, or you will not be able to see that three different people at the same firm have all been quoted.
The field budget
Every field is a promise that someone will fill it in and someone will read it. I use a simple rule. A field earns a place only if it does at least one of these things.
- It is used in a report you listed in your five questions.
- It drives an automation, such as a reminder or an assignment.
- It is legally or contractually required.
- A person needs it to do the next step in the conversation.
Everything else is clutter. A common starting size is around 10 to 15 fields on a contact and a similar number on a deal. You can add fields later. Removing them after people have habits around them is harder.
Prefer pick lists to free text
Wherever the answer comes from a small set, use a drop-down. Lead source, industry, loss reason and preferred language are classic cases. Free text produces "Referral", "referral", "Referal" and "word of mouth", and your source report becomes useless. If you serve both English and Spanish speakers, a language field with two values is a small addition that pays off every time you send a message.
A worked example with illustrative numbers
Here is a hypothetical. A twelve-person landscaping and facilities firm in Puerto Rico wants to know which lead source produces profitable contracts. Their five questions include "where do our best customers come from?"
They define a lead source pick list with six values, a deal value field, and a loss reason pick list with five values. After one quarter, suppose the data shows 40 leads from referrals with 14 won, and 60 leads from the website form with 6 won. The win rate is 35 percent for referrals and 10 percent for the form. That is the kind of answer a CRM is for. It only works because the source was a pick list, required on every new lead, and because "won" had a clear definition. This example is illustrative and the numbers are not from a real company.
Migration is a data project, so treat it like one
Moving existing contacts into the CRM looks like a simple import. It is usually the step that creates the most lasting damage, because bad data entered on day one is trusted by everyone for years.
Inventory your sources
List every place customer information lives. The usual suspects are one or two spreadsheets, the accounting system, the email address book, a phone contact list, and an old CRM or help desk. For each, note who maintains it and how recent it is.
Choose a matching key
Duplicates are the central problem. A matching key is the field you use to decide that two rows are the same person or company. For contacts, a normalized email address is a strong key. For companies, a website domain is often better than a name, since "Acme Inc", "ACME" and "Acme, Incorporated" are the same firm. Phone numbers work if you strip punctuation and country codes consistently.
Decide a survivorship rule too. When two records disagree, which one wins? Typical rules are to prefer the most recently updated record, or to prefer the accounting system for billing addresses and the spreadsheet for notes. Write the rule down so that it is applied the same way to every conflict.
Clean before you load, then trial load
Do the cleanup in a spreadsheet or script outside the CRM. Remove obvious junk, standardize state and country values, split full names if needed, and merge duplicates by your key. Then run a trial load into a sandbox or a test copy of the account. Most reputable CRMs offer one, so ask the vendor during evaluation.
After the trial, check three things.
- Record counts match what you expected, within a stated tolerance.
- A sample of 30 to 50 records, picked by hand, looks right field by field.
- Relationships survived. Contacts are attached to the right accounts.
Only after that do you do the real load. Keep the original files untouched and dated. If something is wrong a month later, you will want the source.
Mind the privacy side
You are moving personal data. Know what you hold and why. If you email people in bulk, you need a record of how consent was given, and the rules differ by country and by state. I am not a lawyer and this is not legal advice, so have counsel confirm what applies to your customers. As a practical matter, add a consent source and date field now, since retrofitting it is painful.
Plan adoption like you are changing a habit
A CRM that is configured perfectly and used by half the team is a failed CRM. Adoption is a behavior problem more than a training problem.
Make the CRM the only place that counts
The strongest adoption lever is a simple rule. If it is not in the CRM, it does not exist for forecast, commission or assignment purposes. Run your weekly pipeline meeting from the CRM screen and nowhere else. People update records when the meeting depends on it.
Remove double entry from the first day
If a salesperson has to type the same note into the CRM and a spreadsheet, the spreadsheet will win. Connect the email and calendar, so that messages and meetings log themselves. Retire the old spreadsheet on a stated date and make it read-only.
Name an owner
Someone has to own the system. In a small company that is often a part-time role, perhaps four hours a week. The owner approves new fields, fixes data problems, handles user access and talks to the vendor. Without an owner, the CRM slowly becomes a junk drawer.
Train on the job, in short sessions
Two 45-minute sessions on real deals beat one full-day class. Teach the three things everybody does daily, which are logging an interaction, creating a next step, and updating a stage. Leave reporting and automation for the owner. Record the sessions in both English and Spanish if your team works in both languages, and write the quick reference in the language people actually use on the floor.
What to ask a vendor
Questions worth asking before you sign.
- Can I export all of my data, including notes and activity history, in a standard format, at any time and without a fee?
- Is there a sandbox for testing imports and changes?
- What happens to my data and my integrations if I downgrade a plan?
- How are API calls limited, and what does the next tier cost?
- Which of the features I need are in the plan I am pricing, and which are add-ons?
- What does the vendor do for uptime, backups and access logs?
Pricing is usually per user per month, with tiers that gate automation, reporting and API access. Count the real number of seats, including part-time users. Ask what a read-only or limited seat costs, since managers and owners often only need to view.
Failure modes to watch for
| Failure mode | What it looks like | Early fix |
|---|---|---|
| Field sprawl | Forms with 40 inputs, many left blank | Apply the field budget and archive unused fields |
| Duplicate records | Two accounts for the same customer | Matching key, merge rules, a monthly duplicate review |
| Pipeline fiction | Deals stay open for a year | Stage exit rules and a required next step date |
| Shadow spreadsheets | Reps keep a private list | Retire the sheet on a date and review from the CRM |
| Integration drift | Email sync silently stops | Name an owner and check the sync status weekly |
| Unowned system | Nobody approves changes | Appoint an administrator with a few hours a week |
A 90-day plan
This is a template, and you should stretch it if your team is part-time on the project.
Days 1 to 15, define
- Write your five to eight questions.
- Draw the lifecycle with entry and exit rules.
- List objects, relationships and the fields you need, within the field budget.
- Name the CRM owner and an executive sponsor.
- Inventory data sources and choose matching keys.
Days 16 to 40, build and prepare data
- Configure stages, pick lists, required fields and permissions.
- Connect email and calendar.
- Clean source data outside the CRM and resolve duplicates.
- Run a trial load and check counts, samples and relationships.
- Draft two or three reports that answer your questions, with sample data.
Days 41 to 60, pilot
- Move two or three users onto the system with real deals.
- Hold a weekly 20-minute review for what is confusing or missing.
- Adjust fields and stages. Resist adding anything that is not needed.
- Do the final data load and freeze the old spreadsheets.
Days 61 to 90, roll out and stabilize
- Train everyone in short sessions on the daily tasks.
- Run the pipeline meeting from the CRM only.
- Measure adoption, such as the share of deals with a next step date and the percent of leads with a source.
- Review duplicates and data quality at day 75 and day 90.
- Decide what to add next, and put it on a list for the following quarter.
A useful target at day 90 is modest. Every active deal is in the system, the five questions can be answered from a report, and the old spreadsheets are retired. Anything beyond that is a bonus.
Monday morning
If you only have an hour this coming Monday, do this. Write your five questions. Draw the lifecycle on a sheet of paper with entry rules. List every place where customer data lives today. Those three pages will make every vendor conversation sharper, and they will make the eventual configuration almost mechanical.
If you would like a second pair of eyes on that plan, Ozcorp InfraOps helps small teams with exactly this kind of groundwork, from data cleanup to integrations, and InfraOps Base starts at $500 per month with vendor and license charges billed separately. I am happy to talk it through, and I will tell you if you do not need any help at all.
Discuss your infrastructure requirements
Review the current service offer or schedule a conversation about the scope you need.
Stay in touch
Follow Ozcorp
Leave your details for occasional notes about new articles and Ozcorp updates.