Start With Process, Not Features
Map the business process first. The CRM serves the process, not the other way around. Configuring features before mapping process produces confused users, broken adoption, and a six-month “phase 2” project to undo what phase 1 over-built. Walk the lead-to-cash flow with sales, the case-to-resolution flow with service, and the campaign-to-revenue flow with marketing. Note every system the data touches, every decision a human makes, every handoff. Tools like Lucidchart, Miro, or simple Visio diagrams beat nothing; the discipline is naming the owner of each step. The 2025 Forrester benchmark found projects that produced a process map before configuration finished 35% faster on average.
Phased Rollout
Go live with the minimum viable CRM: core objects (Account, Contact, Opportunity, Case), core automations (lead routing, escalation alerts, opportunity stage progression), core reports (pipeline, win rate, case backlog). Add complexity iteratively. Big-bang launches that try to ship 47 custom objects, 200 fields, and 80 workflows on day one rarely end well — users cannot adopt what they cannot understand. The 2026 default cadence: MVP in 12-16 weeks, ring-1 expansion at 6 months, full feature set at 12 months. Reserve sandbox capacity for ongoing build-test-promote cycles.
Data Migration Early
Data migration is the longest task in any implementation. Start discovery in week 1, not week 12. Inventory every source, profile data quality, identify duplicates, map fields. Fail early on bad data rather than the day before cutover when the executive sees the dashboard and asks why their top 20 accounts are missing renewal dates. The pattern that works: the data work runs in parallel with configuration; the cutover rehearsal happens against full-volume sandbox data four weeks before go-live so surprises are absorbed in the rehearsal, not in production.
Implementation timeline — typical mid-market deployment
W1-2 Process mapping, stakeholder alignment
W1-12 Data discovery, profiling, mapping (runs throughout)
W3-6 Configuration sprint 1 (core objects + automations)
W7-10 Configuration sprint 2 (integrations, reports)
W11-12 UAT round 1
W13-14 Cutover rehearsal in full-volume sandbox
W15 Go-live MVP
W16-20 Hypercare + ring-1 expansion
W21+ IterativeTraining Matches Reality
Generic training produces generic adoption. Use real workflows, real personas, and real data samples (masked for sensitive fields) in training. Build per-role paths: SDR cohort learns lead routing and cadence enrollment; AE cohort learns opportunity stages and forecast categories; CSM cohort learns renewal motions and health scores. Record short focused videos (5-7 minutes) for on-demand reference because nobody re-attends a 90-minute session. WalkMe, Spekit, Pendo, and Userflow provide in-app guidance that catches abandonment in real time.
Post-Launch Hypercare
Keep the implementation team engaged for 30-60 days post-launch. Users hit real-world edges that no UAT scenario anticipated. Fast triage prevents workarounds (spreadsheets, side databases, “I just email the team”) from becoming permanent. Set up a dedicated Slack channel, a daily standup for the first two weeks, and a weekly steering review for the first two months. Track adoption metrics (login frequency, key actions per user, data completeness) with a named owner.
Common Failure Modes
The recurring failures: configuring features before mapping process; treating data migration as a week-12 task; sponsor disappearance after kickoff; training delivered before the system is configured for the actual workflow; and the SI partner disbanding the day after go-live, leaving the customer to discover edge cases alone.
What Changed in 2026
Three shifts: AI capabilities (Agentforce, Microsoft Copilot, HubSpot Breeze) became part of the MVP rather than phase-2 add-ons; outcome-based pricing changed the procurement conversation; and the EU AI Act compliance work added a parallel workstream for any in-scope use case.
What to do this week
Walk one end-to-end business process with the people who do it daily. Note every click, every system swap, every email. The notes are the requirements; the gaps are the risks.
