A successful Salesforce implementation starts with your strategy, not with the technology. If you first sharpen your business goals, involve your team early, take data migration seriously and train users thoroughly, you lay a foundation your organisation can build on for years. In this article we share the checklist Resolve IT has used since 2019, based on more than 340 completed projects.
Why does a Salesforce implementation deserve a checklist?
A Salesforce implementation touches your processes, your people and your customers all at once. Without a structured approach, the technology quickly takes the lead and you end up with a collection of disconnected features that nobody uses. A checklist forces you to set goals first, design next and only then build, in that order.
Salesforce is a tremendously powerful platform, but you only unlock that potential when the setup aligns with your strategic goals and is embraced by your entire team. In practice, we rarely see implementations fail on the technology itself. They fail on unclear goals, poor data or users who were never properly brought along.
The checklist in this article is not a theoretical model. It is the way of working we apply to every implementation and onboarding project, from small Sales Cloud engagements to environments spanning multiple departments and integrations with systems such as Exact Online.
How do you start: with strategy or with technology?
Always start with strategy. Before a single field is created, your business goals should be on the table: what do you want to achieve, which processes do you want to improve and how will you measure whether you have succeeded? The technology then follows naturally from those answers, never the other way round.
Many implementations run aground because the technology becomes the driving force instead of the goals. We deliberately turn that around: we start with what you want to achieve and build the solution around it. That sounds obvious, but it takes discipline. The temptation to start building fields, flows and dashboards straight away is strong, especially when the platform makes so much possible.
Before you begin, ask yourself at least these questions:
- Which business goals must Salesforce support, both now and three years from now?
- Which processes are running poorly today, and why exactly?
- Who will work with the system on a daily basis, and what do those people need?
- Which systems need to be connected, such as your accounting or marketing tools?
- How will you measure whether the implementation has succeeded?
Together, the answers form a blueprint that translates goals into concrete functionality and user stories. Unsure about the right scope or priorities? Independent consultancy advice ahead of the project prevents costly changes of direction later on.
How do you make sure your team actually uses the system?
Involve future users from the very beginning, not just at go-live. Let them contribute to the design, let them test interim deliveries and train them on their concrete daily tasks. Adoption is just as decisive for success as the technical setup: the best implementation fails if nobody uses the system.
Users who are involved early will later recognise their own way of working in the system. That lowers the barrier enormously. They also surface bottlenecks you cannot see from a management perspective: a mandatory field whose value is simply unknown at first customer contact, or a process step that in reality runs very differently from what the process diagram suggests.
In addition, plan training as a fixed part of the project, not as an afterthought. Well-trained users demonstrably get more value out of Salesforce and make fewer data errors. You can read how to prevent resistance and build support in our article on getting end users to embrace Salesforce.
What should you watch out for in data migration?
Clean up your data before the migration and validate the result afterwards. Poor data leads to poor decisions and undermines users’ trust in the new system. Reserve sufficient time and budget for data migration from the start; it is a fully fledged work package, not a side item on the schedule.
In our approach, a structured data migration goes through these steps:
- Inventory: which data lives where, in which systems and in what quality?
- Cleansing: merging duplicates, archiving outdated records and completing missing information.
- Mapping: determining which source field goes to which Salesforce field and which rules apply.
- Migration: carrying out the transfer in a structured, phased manner, with a test migration beforehand.
- Validation: spot checks and controls to establish that the data has arrived complete and correct.
Above all, do not underestimate step two. A CRM that starts with polluted data loses credibility with the team immediately. In our article on data migration best practices we cover each of these steps in more depth.
Why is it better to start small?
Start with a working foundation and expand from there in a controlled way. A system that is too complex at launch causes confusion and resistance among users. Short delivery cycles let you see value along the way and give you room to adjust before choices become final. No big bang, but grip.
This does not mean your ambitions have to shrink. It means you realise them in the right order. A manageable first phase proves the value of the platform, gives users confidence and produces practical experience that makes the following phases better.
A good example is Marie-Stella-Maris: that engagement began with a manageable Sales Cloud implementation and later grew into something much larger. Because the foundation was in place, each expansion could build on proven choices rather than on assumptions.
How long does a Salesforce implementation take?
The lead time depends on the size and complexity of your project. Simple implementations can go live very quickly, while larger engagements are delivered in short cycles so you see results along the way. You will get a realistic estimate in an initial conversation, based on your goals and processes.
By way of illustration: at Talpa Studios, the first department was live within four weeks. That was possible not in spite of, but thanks to tight phasing: first the department where the gain was greatest, then controlled expansion.
Be cautious with parties who promise an exact end date up front without knowing your processes. A reliable schedule only emerges after a thorough analysis of your goals, your data quality and the integrations you need.
What does a structured implementation project look like?
A proven project runs through four phases: Discover, Design, Build and Elevate. First we get to the bottom of your processes and goals, then we translate insight into a clear design, next we build in short sprints, and after go-live, training and support ensure your team can carry on independently.
In practice, it looks like this:
- Discover: we dive into your processes, goals and bottlenecks, together with the people who work with them every day. That way we know not only what needs to change, but also why.
- Design: insight becomes a clear plan, with designs, user stories and a roadmap you can steer by.
- Build: we build in short sprints, with your organisation at the table. See results quickly, adjust early, no surprises at delivery.
- Elevate: go-live is the starting point, not the end. Training and support ensure your team works confidently from day one, with us as a partner in the background.
This phasing avoids the two classic pitfalls: building for months without interim feedback, and going live without a plan for adoption and maintenance.
The checklist in brief
Use this checklist as a guide and you will stand considerably stronger at the start of your project:
- Record your business goals and success criteria before anything is built.
- Involve future users in design and testing from the very beginning.
- Deliberately keep the first delivery simple and expand in phases afterwards.
- Treat data migration as a fully fledged work package: cleanse, map, migrate, validate.
- Plan training and guidance as a fixed part of the project, not as an afterthought.
- Choose an approach with short cycles, so you see value along the way and can adjust.
- Arrange support and further development for the period after go-live.
Ready to get started?
Would you like to talk through your Salesforce implementation or get a realistic estimate for your project? Get in touch: we are happy to think along with you.