Salesforce Implementation Plan

Download our ready-to-use project plan template built by a Salesforce Implementation Lead


This is a Salesforce Implementation plan developed by an expert with vast experience in Salesforce implementations. Use the project plan as a basis to create your own customized schedule and save hours of time!

The schedule incorporates best practices developed over several years, and it includes all the required and recommended steps for a Salesforce rollout and migration from a legacy system.

Salesforce implementation schedule in Excel

What does the project plan cover?

The plan contains all steps of a typical Salesforce implementation in a general, midsized company – from project initiation to go-live, lessons learned and project closing – approximately 70 actionable steps.

The plan follows a hybrid approach – Waterfall-like phases and individual activities who ideally are carried out in an agile way.

Activities are broken down into the following phases/work streams:

  • Project initiation: General steps for setting up your project, including establishing a project organization, developing the schedule, risk assessment and other activities. Project initiation closes with the project kickoff meeting.
  • Requirements and design: This phase covers the gathering of requirements via workshops and the development of user stories for all common usage scenarios. User stories are informal descriptions of transactions and steps carried out by an end user. In this phase, we also define the migration approach with respect to the specific source system that is used. Legal and compliance requirements for customer data management should also be looked at in this phase.
  • Salesforce Technical Buildup: In this phase, the Salesforce implementation partner performs the technical customization and preparation of your Salesforce instance. Requirements and user stories serve as input for this activity, which is carried out by the technical team. Key users/end users should be engaged continuously throughout this period, because the implemented processes and features need to be tested and refined. The build phase follows the agile methodology, where features (such as Accounts management, Leads, Contact management and Campaigns) are rolled out across several sprints.
  • Data migration: This workstream covers all migration-related activities, such as the preparation of scripts, data cleansing and the actual migration into Salesforce.
  • User Acceptance Testing: The greater the testing effort, the less you have to worry about go-live and post-go-live issues. The importance of careful testing is also reflected in this implementation schedule, and the schedule foresees at least two rounds of user acceptance testing (UAT) as well as data migration tests. Here is my testing template.
  • Training: Switching to a cloud-based CRM solution like Salesforce can be quite a change (and challenge) for your end-users. Do not underestimate the training effort, and try to plan training related activities such as preparing documentation as well as training sessions early in advance.
  • Go-Live preparation: This implementation schedule covers the key steps for preparing the actual go-live several weeks before the “big date”. Activities include the preparation of a communication to organization but also migration activities.
  • Post Go-Live: The schedule includes the typical post-go live steps such as support and handover to support/operations. Add any steps specific to your organization here, whether it is communication, decommissioning of your legacy system or anything else.

Implementation Plan Features

Key features of this implementation plan:

  • Clean and easy to use
  • Microsoft Excel format (no restrictions, no password lock)
  • Weekly timescale
  • With project phases
  • Including detail activities within each phase
  • All steps from project initiation to go-live included
  • Developed by an experienced Salesforce implementation lead

Who is this plan for?

You are the business project lead heading the Salesforce rollout at your company, and you want to get an overview of the steps involved to make sure all critical aspects are being addressed. In this case, the schedule will instantly provide you a clear picture of what needs to be done.

In the other scenario, you may already be doing Salesforce implementations and you want to refine your approach and improve your toolkit (templates!). Then this schedule is a great way to see how others in your field are approaching Salesforce implementations.

Adapting the plan to your project

The schedule provides the framework for a Salesforce implementation/migration. You need to adapt it to your specific project scenario and organizational setup.

  • Review and adapt the durations for the listed activites. The given durations are meant only as a ballpark figure  you need to make your own estimates based on the specific project scenario, the size of your user base, the usage scenarios and other factors.
  •  Add additional steps to reflect your unique migration scenario. For example, if you are migrating from an existing CRM solution such as SugarCRM, your migration approach will be different than if you migration from an Excel solution.
  • If you want your Salesforce solution to talk to your other business management systems, you need to include the necessary steps for integration and interface development in the schedule. Do not forget to create test cases for testing your backend logic.

Do you have a question about this implementation plan?

Just submit your question here and I’ll get back to you:

Got a question about this product?
Ask your question here!
I typically respond within 24 hours.

Get the Salesforce Implementation Project Plan

  • Covers a complete Salesforce Sales Cloud implementation including migration from a legacy system
  • Weekly timescale
  • With project phases
  • With detail activities for each phase
  • All steps from project initiation to go-live, in total 70+ project steps
  • Developed by an experienced Salesforce implementation lead
Secure payment via FastSpring