Why Implementations Fail
After 250+ Salesforce implementations, we have seen every type of failure. The pattern is almost always the same: not a technology problem, but a process problem. Poor requirements, bad data, insufficient training, or unrealistic timelines. This checklist covers the 10 things that separate a smooth go-live from a painful one.
1. Define Success Metrics Before You Start
Before configuring a single field, agree on what success looks like. Is it faster lead response time? Higher conversion rates? Lower support costs? Define 3-5 measurable KPIs and baseline them. If you can't measure the before, you can't prove the after.
2. Map Your Processes Before Customising
The biggest mistake organizations make is trying to replicate their existing broken processes in Salesforce. Instead, map your current processes, identify what's working and what isn't, and design your Salesforce org around how you want to work - not how you work today. This is the single highest-ROI activity in any implementation.
3. Clean Your Data Before Migration
Migrating dirty data into Salesforce is like moving trash into a new house. Deduplicate contacts, standardise fields, validate email addresses, and archive stale records before migration. Our rule: if a record hasn't been touched in 2+ years, archive it. You can always bring it back.
4. Keep Customisation Minimal in Phase 1
Every custom field, flow, and automation you add increases maintenance cost and complexity. For Phase 1, stick to out-of-the-box features as much as possible. Customise only where standard functionality genuinely cannot meet a critical business requirement. You can always add complexity later - removing it is much harder.
5. Build a Data Migration Strategy Early
Data migration is never as simple as 'export and import'. Plan for field mapping, data transformation, relationship preservation (Account-Contact-Opportunity hierarchies), and validation rules that might reject imported records. Run a test migration in sandbox at least 3 times before attempting production.
6. Test with Real Users, Not Just Admins
Admins know how Salesforce works. Your sales reps don't. User acceptance testing (UAT) must involve actual end users performing their real daily tasks. Watch them use the system - where do they get confused? Where do they create workarounds? Fix those issues before go-live, not after.
7. Plan Training by Role, Not by Feature
Don't train everyone on everything. A sales rep needs to know how to manage leads and opportunities. A service agent needs case management. A manager needs dashboards and reports. Create role-specific training paths and keep sessions under 60 minutes. Record everything so new hires can self-serve.
8. Set Up Dashboards and Reports Before Go-Live
Dashboards should be ready on day one. If leadership can't see pipeline, case volume, or team performance immediately, they will lose confidence in the platform. Build executive dashboards, team dashboards, and individual dashboards before launch - not as a Phase 2 afterthought.
9. Plan Your Go-Live for a Low-Volume Period
Never go live on a Monday morning or during your busiest season. Choose a Friday afternoon or weekend when volume is low and your team can troubleshoot without pressure. Have a rollback plan in case of critical issues. The first 48 hours after go-live are the most important - make sure your implementation team is available.
10. Budget for Post-Launch Optimization
The implementation doesn't end at go-live. Budget 20-30% of your implementation cost for post-launch optimization in the first 90 days. You will discover new requirements, fix adoption issues, and refine processes. Organizations that skip this step end up with an expensive system that nobody uses properly.
Follow this checklist and you dramatically increase your chances of a successful, on-time, on-budget Salesforce implementation.