The Real Timeline for a Salesforce Implementation (From Discovery to Go-Live)
"How long will our Salesforce implementation take?" is the question every stakeholder asks, and the honest answer is: longer than the vendor's optimistic pitch and shorter than your worst fear. This guide lays out realistic timelines for each phase and each project size, so you can plan resourcing, communicate to leadership, and spot when a quoted timeline is fantasy.
Quick Answer: A basic Sales Cloud implementation takes 4 to 8 weeks. A mid-market multi-team build with integrations runs 3 to 6 months. An enterprise multi-cloud rollout takes 6 to 12+ months. Every timeline moves through five phases, which are discovery, design, build, test, and deploy, and the discovery phase is where realistic projects are won or lost.
Key Takeaways:
Basic Sales Cloud takes 4 to 8 weeks; mid-market with integrations takes 3 to 6 months; enterprise takes 6 to 12+ months.
Every implementation moves through discovery, design, build, testing, and deployment.
Discovery is the most-skipped and most-important phase; rushing it inflates every later phase.
Data migration and integrations are the two biggest timeline risks on most projects.
A quoted timeline with no discovery phase is a red flag, not a fast track.
[IMAGE: horizontal timeline graphic showing five Salesforce implementation phases across small, mid-market, and enterprise projects]
The Five Phases
Every Salesforce implementation, regardless of size, moves through the same five phases:
Discovery: understanding your processes, requirements, and data before anyone builds.
Design: mapping requirements to a Salesforce architecture and data model.
Build: configuration and custom development.
Testing: validating against requirements, including user acceptance testing.
Deployment: go-live, data migration, and user cutover.
Timelines by Project Size
Here's what realistic timelines look like:
Basic (Sales Cloud, one team): 4 to 8 weeks, driven by configuration depth and user count.
Mid-market (multiple teams, integrations): 3 to 6 months, driven by integrations, data migration, and custom work.
Enterprise (multi-cloud, multi-geography): 6 to 12+ months, driven by complexity, governance, and change management.
These are working ranges, not guarantees. The two factors that most often blow past estimates are data migration and third-party integrations.
Why Discovery Determines Everything
The phase companies most want to skip, discovery, is the one that most determines whether the rest stays on schedule. Rushing discovery means requirements surface mid-build, which triggers rework, which cascades into every subsequent phase.
A quoted timeline that has no real discovery phase isn't fast. It's setting you up for change orders and delays once the unexamined requirements finally emerge.
The Two Biggest Risks
Data migration is a timeline killer because real-world data is always messier than anyone expects, with duplicates, inconsistent formats, and missing fields. Budget more time here than feels necessary.
Integrations are the other risk. Every external system you connect adds testing surface and failure modes. A single complex integration can add weeks.
Summary
Salesforce implementation timelines range from 4 to 8 weeks for a basic build to 6 to 12+ months for enterprise, moving through discovery, design, build, testing, and deployment. Discovery is where realistic projects are protected, and data migration plus integrations are where they most often slip. A vendor quoting a timeline with no discovery phase is quoting a fantasy. At Inforge, our AI-agent delivery model compresses build timelines significantly, but we never skip the discovery that keeps a project honest.
Frequently Asked Questions
Q: How long does a Salesforce implementation take? A: A basic Sales Cloud setup takes 4 to 8 weeks, a mid-market build with integrations runs 3 to 6 months, and an enterprise multi-cloud rollout takes 6 to 12+ months.
Q: What are the phases of a Salesforce implementation? A: Discovery, design, build, testing, and deployment. Every implementation moves through these five phases regardless of size.
Q: What causes Salesforce projects to run over schedule? A: The two biggest causes are data migration complications and third-party integrations, both of which are consistently underestimated.
Q: Why is the discovery phase so important? A: Discovery surfaces requirements before the build begins. Skipping or rushing it causes requirements to emerge mid-build, triggering rework that delays every later phase.
