0

How to Go From Multiple Salesforce Orgs to a Single Customer View

 

A World Map

Tracking key information across global, regional and departmental levels is often hard enough without considering multiple Salesforce orgs in your business.

If you’re here, then you may already know what a Salesforce org is, but if not, we have a definition available straight from the horse’s mouth:

“A deployment of Salesforce with a defined set of licensed users. An organization/org is the virtual space provided to an individual customer of salesforce.com. Your organization includes all of your data and applications, and is separate from all other organizations.”

Some businesses will not have encountered this phenomenon until they reach a certain size but the reality is, with an increasing number of businesses with global presence and many growth strategies involving mergers and acquisitions many businesses have found themselves in the situation where they are maintaining multiple Salesforce orgs.

While each instance/org of Salesforce may satisfy local needs, for a global grouped-up business view working separately can mean increased complexity and cost.

This is where the single view comes into play.

If the benefits of getting a single customer view, including the prospect of cross selling and upselling and the chance to leverage the success of your flourishing market in your emerging ones are a temptation too hard to miss, then you’ll wonder if a Single view of a customer and multiple orgs are opposites that cannot be reconciled.

Single Org or Multiple Orgs?

The choice to move all your orgs into one or to try and get your single view and have multiple orgs at the same time  can be rooted back to why you have the multiple orgs in the first place.

Choice or Chance – When talking about how a business has reached the outcome of multiple orgs, we find that many have found themselves there by chance usually as a result of a merger or an acquisition. However, there are still many out there who have made the strategic decision to leverage several instances of Salesforce to accommodate a complex product/sales strategy. If your business has made this choice then you have considered the following key factors:

  • Localized implementations to match a geographical location’s governance rules
  • Local support and administration for each org
  • Legislation that has requested a silo of customer data for each product unit.
  • Holding onto a legacy brand

Whatever the underlying requirements, if the decision has been made to opt for multiple orgs, then the benefits of maintaining these orgs could far outweigh any cost benefit of consolidation into a single org.

In this example, if a single view is what your business needs and the multiple orgs are something you cannot shift, then you need a solution that will give you the chance to have your cake and eat it.

If you have found yourself maintaining multiple orgs by chance, then there are some key considerations you need to make before rushing into a drastic change like a single org project.

A lot of questions to consider, but if you’re considering your multiple orgs then these are all questions you may well already have answers to.

Join us in our next article where I’ll be taking you through how Informatica Cloud data management can help you achieve that single customer view and the benefits of each approach. It’ll come as no surprise that one of the options is the “single org.”

To learn more about Informatica Cloud MDM have a look at our website. If you can’t wait for next week’s article, why don’t you take a look at our Whitepaper: Consolidating Multiple Salesforce Orgs: A Best Practice Guide.

FacebookTwitterLinkedInEmailPrintShare
This entry was posted in Business Impact / Benefits, Cloud Computing, Customer Acquisition & Retention, Customers, Data Migration, Master Data Management, Mergers and Acquisitions. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>