No comments yet

Salesforce Org Strategy

Many organizations struggle with the number of Salesforce orgs that they need. What are the pros and cons between a multi-org and single-org environment? What tools and techniques are available to help you come to the right decision for your enterprise? Choosing the right Salesforce Org Strategy is one of the hardest decisions to make during your CTA review board.

Join us and learn about why you need to have a Define an Org Strategic, pros and cons of multi vs single org Salesforce architectures the best practices for creating one.

Org Strategy Balancing Act

Defining Org Strategy is a balancing act to satisfy business needs while keeping the technology landscape simple. It’s an enterprise architecture’s decision that laid the foundation for Salesforce implementation.

Factors Influencing Salesforce Org Strategy

Org Strategies

Business Point of View

  1. Std. or diverse business processes and their ownership
  2. Collaboration between different business streams
  3. Sharing data across different business processes, including customers and partners related information

Organization Point of View

  1. Corporate Strategy and Sponsorship
  2. Associated Change Management
  3. Org Administration and Governance around it

Single Org

Pros

  1. Collaboration across different users of the organization
  2. Std. Business Processes across the globe
  3. Cost-effective
  4. Reduced number of integrations
  5. Licensing cost reduction, Salesforce + Appexchange
  6. Minimal efforts for reporting and analytics
  7. Centralized Admin
  8. Consistent Delivery Processes

Cons

  1. A high volume of data
  2. Hitting Salesforce limits
  3. Performance implications
  4. Security and sharing difficult to manage
  5. Complex org e.g. additional apex code and page layouts
  6. Challenging to manage Salesforce components into a single org
  7. Slow to react to the changes needed for business as thorough testing required
  8. Constraints on storage limits

Single Org – Example

Multi Org

Pros

  1. Record Sharing and the Security model is simplified by non-complex sharing rules
  2. Provides greater BU autonomy through individualized processes and customized functionality
  3. Greatly reduces the risk of exceeding Org limits 
  4. Org-wide settings are easier to govern and manage
  5. Lower data volumes within a single Org potentially improves performance
  6. Improved time to market and the freedom to innovate
  7. Reduced complexity within a single Org

Cons

  1. Harder to get a clear global definition of processes and data
  2. Customization required to deliver unified reporting across Orgs
  3. Duplicated administration functions required.
  4. Increased complexity for SSO
  5. Third-party license costs increase depending on the solution
  6. Salesforce Integration cost increases with process & data integration across Orgs
  7. Cross Business Unit collaboration between business users of different Salesforce Org becomes another challenge
  8. Time to deployment is quick as the number of impacted components will be minimal due to the code or config change
  9. Individual Org works best where business users from different geography tend to have different working styles and the Org can be customized based on their preferred working style

Multi Org Multi Orgs Approach – Master Org Sync Example

Multi Org Multi Orgs Approach – Reporting Org Example

Multi Orgs Approach – Without Reporting Org Example

New Single Org

  1. Setting up completely new Single Org
  2. Migrate data from sunset applications to the new Org

New Multi Org

  1. Setting up completely new Multi Orgs considering Salesforce Limits, Business Units, Compliance, Reporting, Collaboration etc.
  2. Migrate data from sunset applications to the new Multi Orgs
  3. If necessary, setup integrations between Orgs and consider reporting requirements as well
  4. Think about Integration, Identity Strategy

Old Org to New Single Org or Multi-Orgs

  1. Consider migration of data and metadata from existing org to the new org
  2. Profile and cleanse data prior to migration
  3. Do not bring technical debts from old org to the new org
  4. Remove technical debt

Continue with Old Org

  1. Consider Lightning migration
  2. Remove technical debts
  3. Simplify business processes to get rid of complexity

New Single/Multi Orgs + Continue Old Org

  1. Completely different business unit using old org. e.g. HR department
  2. New Orgs are dedicated to completely isolated business function

Ripple effect on changing Org Strategy

Strategy Approach

Recording

Post a comment