top of page

Salesforce Org Strategy

In Salesforce, an "org" generally refers to a Salesforce instance allowing users to access and deploy applications with diverse feature sets. In simple terms there are three standard org strategies, 1. Single Org, 2. Multi Org and 3. Hybrid Org.  As an aside, there are also some specific variations of hybrid such as Hub and Spoke. All of these options have specific technical, commercial and business implications. 

Salesforce org strategies often tend to just 'happen' and in the majority of cases are unplanned. Alternatively, as needs and usage patterns change over time, the org strategy employed at the time of initial deployment can become no longer fit for purpose. This can become an issue when increasing complexity drives up costs and/or the implementation becomes unwieldy. 

Aequus's general position on Org Strategy is that there is no right or wrong approach rather all the options are equally valid and should be assessed and considered. However, they all have different implications for the three main areas i.e. Technical, Commercial and Business, e.g. a more flexible licence type or a higher level edition may involve higher cost but is ultimately more beneficial to the business and vice versa. This often leads to a discussion as to which of these areas is most important in the decision, however a deep understanding of the short and long term implications by all parties is the best outcome if it can be achieved. 

The key takeaway is that there is no single "right" answer, but rather different approaches with different implications. When establishing or evaluating a Salesforce org strategy, the choice between Single-org, Multi-org or Hybrid architectures can be perplexing. 

Typically, Single-org salesforce architectures are suited for organisations with streamlined processes and similar data, processes and users across all business functions. Benefits include improved visibility, consolidated reporting, standardised processes, collaboration enhancement, and global standardisation, whilst the challenges include increased complexity, longer deployment cycles and limit-related issues. 

Multi-org salesforce architectures are recommended for diverse business processes requiring separation, offering simplified security models, unit autonomy, risk reduction, and performance improvements. Challenges include process clarity, limited reuse, customization needs, duplicated functions, complexity for sign-on, and elevated integration costs. 

Aequus has significant experience with this issue and we would welcome the opportunity to discuss how we can help, please contact us.

bottom of page