How Long Does a Salesforce Implementation Take? Realistic Timelines for 2026

Every Salesforce vendor will tell you a timeline. The question is whether that timeline reflects what actually happens or what they need to say to close the deal. After implementing Salesforce across dozens of organizations — from 10-person startups to 2,000-person health systems — here is what the numbers actually look like.

The short answer: 4–6 weeks for a focused quick start, 8–12 weeks for a full SMB implementation, 14–24 weeks for a mid-market multi-cloud project, and 6–18 months for enterprise-scale deployments. The rest of this guide breaks down what happens in each phase and what makes timelines slip.

Quick Start: 4–6 Weeks

A Quick Start is appropriate when you are standing up one Salesforce cloud (typically Sales Cloud or Service Cloud), you have fewer than 30 users, your data migration is straightforward (one clean spreadsheet or a simple CRM export), and you need standard functionality with light customization.

Week 1–2: Discovery and Design The first two weeks cover business requirements gathering (4–8 hours of stakeholder interviews), data model review, basic org setup (user roles, profiles, security settings), and a configuration plan. For a Quick Start, discovery is compressed — if it takes longer than two weeks, you’ve outgrown the Quick Start scope.

Weeks 2–4: Configuration Standard object customization (custom fields, page layouts, record types), basic automation (5–10 Flows covering lead assignment, email alerts, approval processes), report and dashboard templates, and connected apps if needed (email integration, calendar sync).

Week 4–5: Data Migration and Testing Data validation from source system, data transformation and import (typically one pass of import with one correction cycle), and user acceptance testing with 3–5 representative users.

Week 5–6: Training and Go-Live Two to four hours of role-based training, admin training for whoever will manage the org, go-live, and two weeks of post-launch support.

What pushes a Quick Start past 6 weeks: any integration with an external system, messy source data, more than one data source to migrate, or stakeholder unavailability that delays approval cycles.

SMB Full Implementation: 8–12 Weeks

This scope covers a complete Sales Cloud or Service Cloud implementation for a company with 20–75 users, moderate customization requirements, and one to two integrations with external systems.

Weeks 1–3: Discovery and Solution Design A thorough discovery phase for an SMB implementation produces a data model document, an integration architecture spec, a migration plan, and a project plan with milestone dates. Cutting this phase short is the most reliable predictor of timeline overrun later. The time you save by rushing discovery you spend twice as long fixing mid-project.

Weeks 3–8: Configuration and Build Custom object and field configuration, page layout design by persona, automation development (10–25 Flows), integration build with external systems, and role hierarchy and sharing rule design. Integration work runs in parallel with configuration but frequently extends beyond it — assume integration takes 2–3 weeks longer than configuration for most systems.

Weeks 8–10: Data Migration Data profiling and cleaning (often the longest part, especially when source data is in a legacy CRM), transformation mapping, a test data import to sandbox, correction cycle, and final production import. Two weeks is realistic for clean data from one source. Add a week for every additional source or data quality issue.

Weeks 9–11: UAT User acceptance testing with real users working through real scenarios. Plan for two UAT rounds minimum — the first pass surfaces issues that need to be fixed before the second round. Users who are asked to test with scripted test cases rather than their actual workflows miss real problems. Give them actual work to do in the system.

Weeks 11–12: Training and Go-Live Role-based training sessions, admin certification walkthrough, go-live, and 2–4 weeks of hypercare.

Mid-Market Multi-Cloud: 14–24 Weeks

A mid-market implementation typically involves two or more Salesforce clouds (Sales + Service, or Sales + Service + Experience), 75–500 users, three to five external integrations, and meaningful custom development.

Weeks 1–4: Discovery Extended discovery is not optional at this scope. You need separate sessions for each business unit, each cloud, and each integration. The outputs are a solution architecture document, a data model, an integration architecture, a change management plan, and a phased project plan. Budget 4 weeks for discovery — trying to compress it to 2 weeks at this scope produces a solution design that will be revised mid-project.

Weeks 3–14: Parallel Build Tracks Configuration, custom development, and integration all run in parallel, managed against weekly sprint checkpoints. For multi-cloud implementations, each cloud typically has its own configuration stream with a shared architecture layer. Dependency management between streams is where mid-market projects most often develop timeline problems — one delayed integration blocks UAT for the entire project.

Weeks 12–18: Integration Testing and UAT At this scope, integration testing and UAT are separate phases. Integration testing validates that data flows correctly between systems; UAT validates that the end-to-end workflows work as users expect. UAT at this scope takes 3–4 weeks and involves department representatives from each functional area.

Weeks 18–22: Training, Cutover Planning, and Go-Live Multi-cloud go-lives require a detailed cutover plan covering the sequence in which systems are switched over, data freeze periods, rollback criteria, and a go/no-go checklist. Training programs for mid-market implementations are multi-session, role-specific, and often include recorded content for asynchronous use.

Weeks 22–24: Hypercare Six weeks of elevated post-launch support is standard for mid-market multi-cloud projects.

Enterprise: 6–18 Months

Enterprise Salesforce implementations — 500+ users, global scope, multiple clouds, deep ERP and legacy system integrations — are programs, not projects. They require dedicated project and program management, formal change management, and an organizational change management workstream that runs the entire duration.

Months 1–2: Program setup, governance structure, detailed discovery, solution architecture Months 2–6: Core build, integration development, data migration architecture Months 5–9: System integration testing, performance testing, UAT preparation Months 8–12: UAT, training development, cutover planning Months 11–14: Phased go-live by region, business unit, or user group Months 13–18: Hypercare, optimization, subsequent phase planning

Enterprise timelines at the shorter end (6–9 months) require an exceptional internal team with full-time project management, pre-existing internal Salesforce expertise, clean data, and a well-defined scope. Organizations underestimating enterprise timelines consistently — plan for 12–18 months and be grateful if you finish in 9.

What Makes Timelines Slip

Data Quality

This is the single most common timeline killer, and the most consistently underestimated. Organizations believe their data is cleaner than it is — until a data profiling exercise reveals 30% duplicate rate, inconsistent field values, missing required data, and records that cannot be mapped to the new data model.

The rule of thumb: if you’ve never run a formal data quality assessment on your source system, plan for your data migration to take 50% longer than your initial estimate.

Stakeholder Availability

Decision-makers who are available for the sales process are often unavailable for the implementation. When the person who needs to approve the data model, the automation logic, or the page layout design is traveling, in budget season, or simply deprioritizing the project, every approval cycle adds a week.

Build stakeholder availability requirements into your project contract — minimums on hours per week, required participants for each workshop, and escalation paths when approvals are delayed.

Scope Creep

The most common form: “While we’re in here, can we also…” The first five times this phrase appears in a project, the project gets longer. New requirements after Week 4 of discovery are scope changes — they should go through a formal change control process with explicit timeline and cost impact.

Integration Complexity

External system integrations almost always take longer than estimated. APIs change, authentication requirements are more complex than documented, the external system’s team is unavailable for testing, or the data structure in the source system doesn’t match what the API documentation describes. Add 30% to any integration timeline estimate as a baseline.

What You Can Do to Move Faster

Assign a single internal decision-maker with authority. Projects with decision by committee are slower than projects with one empowered owner. That person needs to be able to approve designs, resolve conflicts between departments, and make trade-off decisions without escalating.

Complete a data quality assessment before kickoff. If you know your data problems before the project starts, you can plan for them. If you discover them mid-project, you replanning under time pressure.

Respect the discovery phase. Every hour spent in discovery saves three hours of rework later. Organizations that push to skip or shorten discovery to “start building faster” consistently experience the longest total project durations.

Limit integrations in the first phase. If you are integrating with five external systems, ask which three are truly required for go-live. The other two become Phase 2. Every integration you add in scope is a dependency that can delay your go-live.

Engage your users during UAT with real work. Scripted test cases miss real problems. Give users actual scenarios they’d encounter on the job and let them find issues. Two rounds of real-world UAT catch more than four rounds of scripted testing.

---

Estarei is a boutique Salesforce consulting firm built by ex-Salesforce alumni. We build realistic project plans based on what implementations actually require — and we don’t pad timelines to protect margins. Learn about our Salesforce consulting approach or book a free consultation to get a real timeline estimate for your project.