Introducing Anypoint Templates for Salesforce Integration

Companies are looking to connect to their customers while leveraging customer data across the business to make more informed decisions. As organizations drive digital transformation initiatives to cater to today’s online consumer, there is a massive need for businesses to connect to their customer’s in an holistic way.

Most companies turn to CRM solutions to get a better view of their customers, but it’s not as simple as selecting a single CRM system. It takes defining an architecture that is able to span multiple systems, collecting the most important data from each system and presenting it appropriately in the CRM system. Many companies not only have multiple systems with customer data, but in many cases have multiple CRM systems, either by choice, by legacy or by acquisition. In companies with multiple CRM systems, or multiple instances of the same system, allowing customer information to flow from one instance to another is a major challenge.

Today, it is completely common to even have multiple Salesforce instances for a variety of reasons, which is why MuleSoft has created a set of Anypoint Templates to solve common Salesforce org to org integration challenges. Anypoint Templates from MuleSoft address Salesforce integration challenges, while leveraging a proven, optimized framework. They simplify your integration needs and help you connect applications more quickly by configuring or extending integration flows, or starter applications, we have created. All of these can also be expanded to support common integrations between Salesforce and other CRM systems with Anypoint Studio.

Below we illustrate some of the most common reasons to have multiple Salesforce instances, and how our Salesforce to Salesforce templates can help:

M&A (Mergers and Acquisitions)

Migrating customer accounts and contacts from a newly acquired subsidiary to a central Salesforce system can give an organization the ability to uncover up-sell opportunities, while reducing possible churn.  In the absence of a consolidated source of customer data, there are a number of challenges that can be introduced across sales and services.  Companies invest time and money attempting to penetrate accounts they have unknowingly acquired, sales teams find themselves competing on accounts, and services or support may suffer, resulting in customer dissatisfaction and churn.

A solution that allows you to consolidate to a single instance saves your sales organization. With the that we provide as of today, you can leverage the migration pattern consolidate the acquired instance into your main one, and can leverage the broadcast and bi-directional  patterns to create a system where they work together while you plan and execute the migration to one instance. The built off the aggregation pattern can be very useful in reporting across the multiple Salesforce instances and can be a great way to validate that the synchronizations and migrations were successful.

Partner Ecosystem Development

Developing a partner ecosystem without disrupting current sales channels requires the ability to route opportunities both internally and externally with complex business rules.  Without an effective method for connecting to a partner’s CRM system, companies can find it difficult to scale their distribution model and may limit their ability to effectively cater to market demand for an indirect selling model.

Our Salesforce to Salesforce templates allow organizations to rapidly on-board and incorporate new members of a partner ecosystem by broadcasting opportunities to the correct resellers and/or distributors, providing inventory availability from suppliers, or routing opportunities sourced from alliance partners to the correct field teams. You can configure the application to only share the information that you want. For example you may only be comfortable sharing that there is an opportunity which requires one of your partners components, but you probably won’t want to share the opportunity size. Likewise, if you are partnering with re-sellers, you may want to only share leads for deals in territories or sectors that your resellers cover. With our templates leveraging the migration pattern, you can kickstart a partner by doing a bulk data transfer of only the fields that you want, and for only the objects that you want. Once they are up and running, you can leverage the broadcast and bi-directional sync templates to stay in sync, and lastly, the aggregation templates to report across the multiple Salesforce instances.

Business Specialization

Many organizations have dedicated business units or product lines whose operational functions are so varied that they need their own CRM systems, but still need to share data across the multiple business units.  If those different CRM instances aren’t connected, these different internal organizations may operate in data silos and almost as independent businesses.

Global organizations may have geographical differences, whether regulatory or functional, causing the business to use different siloed CRM systems.  Connecting these siloed CRM Orgs and allowing the orgs to synchronize necessary account and contact information bi-directionally is essential for cross-functional collaboration.

It is essential to have a consistent, supportable strategy in place for integrating Salesforce data, and the ability to seamlessly bring data in and out of Salesforce is an essential component of a . When multiple systems need to share data, you end up with an integration need, which is why we have identified the top use cases for org to org integration, as seen above, and have developed to address these challenges.

You can learn more about our Anypoint Templates for Salesforce. We’ll be publishing more blog posts over the coming weeks, giving you a deeper dive into our Anypoint Templates and the challenges they solve – so be sure to check back!

We'd love to hear your opinion on this post