The decision has been made. The contract is signed. The team is (relatively) excited.
Now what?
That's the question I hear most often from business leaders in the first days after a Salesforce project kicks off. The expectations are there, but visibility into what lies ahead is low — and that creates unnecessary anxiety.
This post is a map of what to expect: the phases, who needs to be involved, the milestones that signal things are on track, and the warning signs you need to catch early.
The phases of a typical implementation
Regardless of project size, every Salesforce implementation goes through similar stages. What changes is how long each one takes.
Phase 1: Discovery and mapping (1 to 3 weeks)
Before configuring anything, the implementation team needs to understand how your business works. This phase involves alignment meetings, interviews with key users, and documentation of the current process.
What happens here:
- Sales process mapping (and other processes, if the implementation is broader)
- Identification of required integrations
- Definition of custom fields and layouts
- Alignment on reports and metrics that need to exist
What you need to do: Make the right people available for interviews. Cancelled meetings here delay everything that comes after.
Warning sign: If the consultancy skips this phase or runs very superficial meetings, the configuration will be generic — it won't reflect the reality of your company.
Phase 2: Configuration and development (3 to 8 weeks)
This is where the system starts taking shape. The consultancy configures modules, creates custom fields and objects, builds approval flows, and — if applicable — develops integrations.
What happens here:
- Environment setup (sandbox first, production later)
- User profile and permission creation
- Customizations agreed upon in the discovery phase
- Integrations with external systems
- Data migration preparation
What you need to do: Review and approve configurations in intermediate alignment sessions. The faster the feedback, the less rework.
Warning sign: Weeks without communication or progress demos. Good implementation is iterative — you should be seeing and commenting on the system regularly.
Phase 3: Data migration (1 to 3 weeks, can run in parallel)
Bringing data from the current environment (spreadsheets, previous CRM, etc.) into Salesforce. This is one of the most underestimated phases — and the one that generates the most surprises.
What happens here:
- Mapping and cleaning existing data
- Deciding which data to migrate (not everything needs to go)
- Test environment import
- Validation and error correction
- Final production import
What you need to do: Have someone with business knowledge available to validate whether data was migrated correctly. The consultancy migrates — but the person who knows whether it makes sense is the one who knows the customers.
Warning sign: Data migrated without human validation. Migration errors discovered after go-live are far more expensive to fix.
Phase 4: Training and go-live (1 to 2 weeks)
The system is ready. Now the team needs to know how to use it. This phase includes role-based training (salespeople, managers, admins) and the go-live moment — when Salesforce becomes the official system.
What happens here:
- In-person or remote training by user group
- Quick-reference documentation
- Parallel use period (a few days running both the old CRM and Salesforce)
- Official go-live date and decommissioning of the previous system
What you need to do: Ensure training happens close to go-live — not weeks before. Content learned too far in advance gets forgotten.
Warning sign: Go-live without a defined date. Without a clear milestone, the project drags.
Phase 5: Post go-live support (4 to 8 weeks)
The first weeks after go-live are critical. Questions come up, adjustments are needed, and the team needs support to build the habit.
What you need to do: Ensure there's a fast communication channel with the consultancy during this period. Unanswered questions lead to disengagement.
Who needs to be involved
One of the most frequent causes of troubled projects is insufficient involvement from the right people. These are the essential roles on the client side:
Executive sponsor The C-level or director with authority to make decisions and remove blockers. Doesn't need to be in every meeting — needs to be available when there are impasses.
Internal project owner The person who will follow the project day-to-day, be the point of contact with the consultancy, and drive accountability internally. Usually the sales manager, COO, or a senior analyst.
Key users Representatives from the teams who will use the system. They participate in validation sessions, test the configuration, and become the reference point for colleagues after go-live. One key user per area is sufficient.
IT (when integrations are involved) If the project involves integration with internal systems, someone from IT needs to be accessible to facilitate access, APIs, and environments.
Realistic timeline by project type
| Project type | Typical duration |
|---|---|
| Quick Start (basic Sales Cloud) | 6 to 10 weeks |
| Mid-size implementation (Sales + Service, no complex integrations) | 12 to 20 weeks |
| Full implementation (multiple clouds + integrations) | 4 to 9 months |
| Enterprise (large scale, multiple BUs) | 9 to 18 months |
These are realistic numbers. Be skeptical of delivery promises that fall well below these benchmarks — either quality will suffer, or the scope is being underestimated.
What to measure to know if it's working
Before go-live, define your success metrics. Projects without defined metrics are never considered successful — because there's nothing to compare against.
Adoption metrics (first 90 days):
- % of users active weekly
- % of opportunities created in Salesforce vs. outside it
- Average time to update records
Process metrics (3 to 6 months):
- Average sales cycle length (compared to the prior period)
- Lead-to-opportunity conversion rate
- Opportunity win rate
Business metrics (6 to 12 months):
- Revenue growth
- Reduction in deals lost due to lack of follow-up
- Pipeline velocity
Don't expect business results in the first 60 days. During this period, success is adoption and process. Financial results come later.
The most common mistakes — and how to avoid them
Scope that grows mid-project (scope creep) It's natural to want to add things as the system takes shape. The problem is that each addition delays go-live and increases cost. Have a change management process — new requests go into a queue for the next phase.
Underestimating the data migration effort Data is never as organized as it appears. Reserve time and energy for this phase — and don't delegate validation entirely to the consultancy.
Insufficient training A well-configured, poorly-trained system will have low adoption. Training is not optional — it's as much part of the project as the technical configuration.
No plan for the post go-live period The first 30 days after go-live are the most critical for adoption. Having support available, someone internally to answer questions, and a process for reporting problems makes all the difference.
What comes next
A successful implementation is not the end — it's the beginning. The companies that extract the most value from Salesforce are those that treat the platform as something alive: they review configurations regularly, add functionality as the business evolves, and continue investing in training.
The first year is about adoption. The second is about optimization. From the third year onward, it's about scale.
Marina Borges is founder of Rangers League, a Salesforce consulting firm for growing businesses in Brazil.
Frequently Asked Questions
How much does a Salesforce implementation cost? Quick Start: BRL 15,000–40,000 (roughly USD 3,000–8,000). Mid-size implementations: BRL 50,000–150,000. Enterprise projects: BRL 200,000+. These are implementation costs — Salesforce licenses are billed separately by Salesforce.
Does my company need IT involved? Only if there are integrations with other systems. For Sales Cloud implementations without external integrations, IT is not required. For projects integrating with an ERP, e-commerce platforms, or legacy systems, yes.
What happens if the project runs late? Delays are common and aren't always a problem — as long as the causes are known and managed. What matters is having transparent communication about the reason and the impact on go-live. Unexplained delays are a warning sign.
Can I change the scope mid-project? It's possible, but it has a cost: time and money. The best practice is to log change requests, assess the impact, and decide consciously whether the change enters the current project or goes to the next phase.
How long until I see return on investment? Companies with good adoption and a structured sales process typically see returns between 6 and 12 months after go-live. The return comes from deals not lost, shorter sales cycles, and greater sales team efficiency.
