Objectives and Key Deliverables
We are two separate entities joining forces to create the world’s largest software company focused exclusively on patient safety and quality improvement. Both of the merging parties rely on Salesforce as their CRM solution. Additionally each business also relies on Salesforce as the foundation for a number of other important add on business systems and processes.
The most important and critical add on system is Financialforce which has been used by one entity for the last 3 years and is the other entity's community hub.
There are 280 seats across the organisation.
2. Purposes of project.
As a stage 1, we would like to merge our Salesforce instances in order to have a single location for all world-wide current and future customer records whilst not impacting any of the associated business systems and processes. This should be done by 30 June 2019.
Stage 2, once salesforce in fully merged, the company will look to roll out Financialforce to the other entity and eliminating and the merging other businesses system.
The benefits of this is not to be debated but is expected to aid the sharing of business information, aligning of business processes/activities and elimination of duplication.
The company would like assistance in evaluating, constructing, communicating and deciding upon the best approach to this plan.
For stage 1 the business would like a review of the various options available and ultimately make a recommendation to the CFOs of the business of the best option to merge Salesforce. Once an option is agreed then a detailed project plan should be prepared with the MIS merger team, tasks allocated to the team and then implemented with the consultant overseeing progress
The options should be reviewed using a number of criteria including, but not limited to, complexity, effort, amount of testing, risk and cost.
For stage 2, a project plan for evaluating any current shortfalls in Financialforce applications compared with current system needs. This should be done to assess what changes need to be made to Financialforce prior to rolling it to the other entity.
Drafting a project plan for migration from the current finance system to Financialforce.
Finally the consultant should review the other systems and evaluate any overlaps, systems deficiencies, ease of use, cost, complexity and make recommendation of which systems should prevail.
a. Scope of the Project:
i. Analyze each instance of Salesforce and their respective ancillary add-ons (key systems list can be found below).
ii. Research the complexity and usage of each instance including
1. the amount of data accumulated across all the applicable objects
2. the risks involved with each option
3. the level of effort expected
4. if outside consulting might be needed
5. the costs involved with each option (license and service costs)
i. Initial timeframes: Up to 1 month to complete the project.
b. Experience: At a minimum, the consultant needs to have extensive experience with Salesforce and FinancialForce. The consultant should have significant merger and integration experience and be able to communicate at all levels of the organization in plain language.
c. Communication: A daily standup de-brief
d. List of Applications in use at both entity's
i. Salesforce Sales Cloud
ii. Salesforce Service Cloud
iii. Salesforce Lightning
iv. Salesforce CPQ
v. Salesforce Communities
vi. Salesforce Lightning Knowledge
vii. Salesforce Einstein Analytics
ix. Clarizen - lower priority
x. Zendesk - lower priority