CRM implementation cost is rarely the licence fee. For a mid-sized team, the software subscription is usually 25–35% of the first-year bill. The rest is data movement, integration, configuration, and the internal hours nobody budgets for.
The five cost lines
| Line | Typical share of budget | What drives it |
|---|---|---|
| Licences | 25–35% | Seats, tier, contract length |
| Configuration | 20–30% | Number of pipelines, custom fields, permission sets |
| Data migration | 15–25% | Source systems, duplicates, field mapping |
| Integrations | 10–20% | ERP, accounting, support desk, marketing tools |
| Training and change management | 10–15% | Team size, turnover, documentation |
What each line actually costs
Configuration. A single sales pipeline with standard fields is a two- to five-day job for an experienced admin. Each additional team with its own process adds one to three days. Permissions and record visibility rules are where budgets slip: they look simple and behave unpredictably.
Migration. Exporting contacts is easy; reconciling them is not. Expect $1,500–$8,000 for a small business depending on how many sources exist and whether activity history (emails, notes, tasks) must be preserved. History is the expensive part — many projects deliberately drop it.
Integrations. Native connectors cost time, not money. Anything custom — a quoting tool with no API, an on-premise ERP — starts around $3,000 and rises quickly. Budget for maintenance too: integrations break when either side changes.
Realistic totals by company size
- 5–15 users: $3,000–$12,000 first year all in
- 15–50 users: $12,000–$45,000
- 50–200 users: $45,000–$150,000
These ranges assume a mainstream platform and a partner-led rollout. Self-implementation cuts 30–50% but usually extends the timeline by several weeks.
Costs that appear in month three
Three items reliably show up after go-live. First, additional licences for people who were not in the original count. Second, storage or automation add-ons once the team hits plan limits. Third, remediation work when the data model turns out to be wrong — usually because the team configured for how they thought they sold rather than how they actually sell.
How to keep the budget honest
- Scope the first release to one team and one pipeline
- Decide in writing what history you will not migrate
- Put integration ownership in the contract, including who pays when an API changes
- Reserve 15% contingency; it will be used
FAQ
Is implementation included in the subscription?
Rarely beyond basic onboarding. Vendors include guided setup calls; configuration, migration, and integrations are normally professional services or partner work.
Can we implement it ourselves?
Yes for a single team with clean data. The trade-off is time: an internal admin typically needs three to six weeks of part-time work compared with one to two weeks for an experienced consultant.
How long does a typical implementation take?
Small teams: two to four weeks. Mid-sized with integrations: six to twelve weeks. Enterprise: a quarter or more, usually in phases.
What is the most common budget mistake?
Underestimating internal time. Even with a partner, your team supplies process knowledge, testing, and training — typically 40–80 hours for a small rollout.