Salesforce implementation typically takes 4 to 16 weeks for mid-market companies, depending on scope, data complexity, and the number of integrations involved. A lean Sales Cloud setup for a 30-person team can go live in four to six weeks. A full Revenue Cloud or CPQ deployment for a 200-person organization with ERP integrations will realistically run three to four months. Understanding what drives that range before you sign a statement of work is how you avoid surprises.
At TeraQuint, we've run implementations across IT services, SaaS, and managed services firms — including a full CRM migration for HeyMilo.ai that wrapped in seven weeks. The timeline variables are predictable once you know what to look for.
What Actually Determines Your Implementation Timeline
Most timeline estimates fall apart because they treat Salesforce as a single product. It isn't. The clock starts at very different places depending on what you're deploying.
Product Scope
Sales Cloud alone — opportunity management, pipeline, basic reporting — is the fastest path. Add CPQ and you're pricing complex quote logic, approval workflows, and product catalog structure. Add Service Cloud or Revenue Cloud and the project surface area expands significantly. Each product layer adds two to four weeks in a typical mid-market deployment.
Data Migration Complexity
Migrating from a spreadsheet is faster than migrating from HubSpot or Dynamics. The real variable is data quality: duplicate records, inconsistent field naming, missing contact associations. We've seen data prep consume 30% of a project timeline when it wasn't scoped properly upfront. If your team hasn't audited your existing CRM data before kickoff, build extra time in.
Integrations
Native Salesforce connectors to tools like Slack or DocuSign add a few days. Custom API integrations to ERPs, billing systems, or proprietary databases can add two to six weeks depending on the availability of the other system's API documentation and your internal IT bandwidth. The integration that always gets underestimated: your email platform. Syncing Gmail or Outlook with proper activity capture requires more configuration than most teams expect.
Internal Readiness
This is the variable consultants talk about least and it affects timelines most. If your executive sponsor can approve decisions in 48 hours, your project moves. If approvals require committee review or your subject matter experts are available only part-time, two weeks of consulting work can stretch into five. The fastest implementations we run share one trait: a designated internal owner with authority to make calls.
Timeline by Package and Deployment Type
Here's how typical mid-market deployments break down by scope:
Salesforce Starter (from $5K) — 2 to 4 Weeks
Best for teams under 30 that need a clean Sales Cloud foundation: lead management, opportunity pipeline, standard reports, and basic user setup. Limited data migration, no custom integrations. This is a get-running-fast engagement, not an enterprise build.
SMB Package (from $8K) — 4 to 8 Weeks
Covers Sales Cloud configuration, moderate data migration, one or two integrations (typically email and a marketing tool), and custom reporting. This is the right fit for companies moving off HubSpot or a homegrown spreadsheet system with 30 to 100 users.
RevOps Accelerator (from $10K) — 8 to 12 Weeks
Designed for revenue teams that need more than a CRM — forecast frameworks, pipeline health scoring, territory logic, and cross-functional reporting. Includes CPQ configuration if quoting is part of the scope. Appropriate for 100 to 300 person organizations running complex sales motions.
CPQ or Data Cloud Deployments (from $10K) — 10 to 16 Weeks
CPQ implementations require product catalog design, pricing rule logic, approval workflow mapping, and quote template build. Data Cloud Foundation engagements add data ingestion pipelines and identity resolution on top of that. These are not fast projects and shouldn't be treated as such.
For a detailed breakdown of what drives cost alongside these timelines, see our Salesforce Implementation Cost Guide.
The Phase Breakdown Most Consultants Skip
Quoting a six-week timeline without explaining what happens in those six weeks is how clients end up frustrated at week four. Here's how a structured implementation actually runs:
- Discovery (Week 1–2): Process mapping, stakeholder interviews, integration inventory, data audit. This phase determines everything that follows. Skipping it is how you end up rebuilding in month three.
- Build (Week 2–6+): Configuration, custom object creation, automation logic, integration setup, data migration prep. The longest phase and the one most sensitive to scope changes.
- UAT (1–2 weeks before go-live): User acceptance testing with real data and real scenarios. The goal is breaking things before users do.
- Go-Live and Hypercare (1–2 weeks post-launch): Monitored launch, rapid issue resolution, adoption check-ins. Most problems surface in the first two weeks after go-live.
Our implementation methodology is built around this structure. Predictable phases reduce change orders and keep timelines honest.
What Can Compress or Extend Your Timeline
Things That Compress Timelines
- Pre-cleaned data ready before kickoff
- An internal Salesforce admin already on staff
- Limited integration scope (one or two tools)
- Executive sponsor with fast decision authority
- A clear, documented sales process before configuration starts
Things That Extend Timelines
- Scope additions mid-project (the most common cause of delay)
- Slow UAT feedback cycles
- Third-party API limitations outside your control
- Undocumented legacy workflows discovered during build
- Multiple stakeholders with conflicting process opinions
A Note on Vendor Timeline Promises
If a consultant promises a full CPQ deployment in three weeks or a Data Cloud implementation in 30 days, ask them to walk you through the phase plan. Compressed timelines without a corresponding reduction in scope are almost always a sign that discovery is being skipped or testing is being rushed. Both create problems you'll pay to fix later.
The seven-week HeyMilo.ai migration worked because scope was locked before kickoff, the client had a dedicated internal point of contact, and data migration was handled in parallel with configuration — not sequentially. Speed is possible, but it's earned through preparation, not promises.
If you're still evaluating what scope makes sense for your team, our implementation packages outline what each tier covers and what's typically out of scope.
Frequently Asked Questions
How long does Salesforce implementation take for a small business?
For a small business with under 30 users and a straightforward sales process, a basic Sales Cloud implementation typically takes two to four weeks. Timelines extend when data migration, integrations, or custom automation are added to the scope.
Can Salesforce be implemented in 30 days?
Yes, but only for limited-scope deployments with pre-cleaned data, minimal integrations, and an available internal owner. A 30-day timeline for a complex or multi-product implementation usually means discovery and testing are being compressed, which creates post-launch problems.
What causes Salesforce implementations to run over schedule?
The most common causes are mid-project scope additions, slow internal approval cycles, and data quality issues discovered after the project starts. Locking scope before kickoff and auditing your existing data upfront are the two most effective ways to protect your timeline.
How does CPQ implementation compare to Sales Cloud in terms of timeline?
A standard Sales Cloud deployment for a mid-market team runs four to eight weeks. CPQ adds significant complexity — product catalog structure, pricing rules, approval workflows, and quote templates — and typically adds four to eight weeks on top of a base Sales Cloud timeline. Most standalone CPQ implementations run ten to sixteen weeks.