780px-Human-emblem-handshake (1)

Nuances of Salesforce Org. Mergers & Splits, by Vikas Arora

If your organization is a compilation of merged business units and you are in the midst of planning an overall salesforce.com strategy, you’re probably debating the pros and cons of a single salesforce.com org or multiple salesforce.com orgs. While the answer to this question depends entirely on your business and organization, the following insight and guidelines can help your decision process. There are many business and technical considerations to consider before deciding on a single or multiple salesforce.com org. I think that by discussing the benefits of a single org, we can surface the drawbacks of a salesforce.com multi-org business environment.

First, a definition: salesforce.com defines an ‘org’ as “a deployment of salesforce.com with a defined set of licensed users. An organization/org is the virtual space provided to an individual customer of salesforce.com. An organization includes all of the client’s data and applications, and is separate from all other organizations.” Benefit #1: A single salesforce.com org for multiple business units provides greater
management visibility with unified reporting along with roll up and drill-down into pipeline across the business units. This is critical for executive stakeholders of any business. Benefit #2: A single salesforce.com org supports your company’s standardized processes for Sales and Services, especially if your customers have a consistent journey through Sales Cloud, Service Cloud or Marketing Cloud with well-defined touch points.

Benefit #3: A single salesforce.com org enables team collaboration through Chatter and the Content Library – not possible with multiple orgs. Such collaboration reduces the chances of duplicate efforts of team members on the same lead or account and certainly enhances the upsell and cross sell productivity of your team members.

Benefit #4: A single salesforce.com org allows you to maintain data cleanliness because designing and developing any number or application integrations are much less tedious if you have a single org for multiple related business units.

Benefit #5: Most importantly, a company’s top stakeholders/executives will have one centralized view of all reports and dashboards in a single salesforce.com org. Not so with multiple orgs.

Having said the above, your salesforce.com org strategy today should be based on how you expect your business will look two years from now. For a quick check, have your business executives respond to the following set of five questions / statements. If the answer is “Yes” to at least three, a single salesforce.com org is the way to go.

1. Do we have a common set of products and services across multiple business units? (These multiple business units would be the ones for which you are considering separate salesforce.com orgs)

2. Executives need and expect all business reports and dashboards in a single instance / do not want to manage multiple salesforce.com credentials.

3. We have a common client services team across business units.

4. I have/will have the budget for a “Super Admin” who can manage record types, workflow rules and a large user base.

5. Our team requires a document repository for the amount of knowledge sharing they do around sales and marketing best practices.

One of best practices when merging a customer’s multiple salesforce.com orgs is to first build standard entities, objects, reports, dashboards, applications and almost everything needed in the resultant salesforce.com org, and then, in later phases, migrate data and switch users over the weekend or non-working days. This is, of course, a very complex and procedure that is more planned and organized than simply stated here.

SOURCE:

https://www.linkedin.com/pulse/nuances-salesforce-org-mergers-vikas-arora

what-is-lightning-featured-footer-resized-200x74
download-footer-resized-200x96
newlogo

EAC2 Consulting

Making Technology Customer Friendly…

Contact Info

EAC2 Consulting Customer Service

(888) 860-2077

helpdesk@eac2consulting.com

P.O. Box 571, Pulaski, VA 24301