Skip to main content

Quick Tips: Salesforce environment strategy: Single Org vs Multiple Org

Much has been written and presented around Salesforce single organisation and multi-organisation strategies. But, still the question is asked quite frequently. There are really good articles and blogs and I'm hereby trying to compile the information and add my views to it, to provide a summary.

Single Org. Approach

In a single org. approach, an organisation maintains one single Salesforce org. all their required operations (planned to be executed via Salesforce) are executed via same org.

Ideal for: Small and Medium Businesses


  1. Less environment maintenance overhead
  2. Uniform processes - a very good opportunity for organisations which want to implement uniform processes/ functionalities across all units
  3. Easier user provisioning - once a user is setup, they have access to required functionalities


  1. Complicated processes as organisation grows larger and include various operations/ geographies
  2. Increased application conflicts - with same processes being used across different departments/ geographies, one change for a specific unit can impact other unit
  3. Performance issues - with same objects being used across different units, the data volume per object can substantially increase. This leads to special design consideration during design and development phase and also possibly performance degradation or limitations

Multi Org. Approach

Ideal for: Larger organisations with multi-country operations or multiple segregated business units

Note:- It's not that large organisations should not use single organisation, but it's viability varies based on application usage & complexity, data volume and performance expectations.


  1. Flexibility to have unit specific operations within specific environment
  2. Higher Performance - Only unit specific data to be persisted in their Salesforce environment. Leading to better performing functionality
  3. Tailored Solution - Provides ability for each instance to have it's own tailor made solutions, to fulfil desired functionalities with less overhead. In an organisation having multiple segregated business units of Line of businesses, it can help segregate required functionalities/ data based on intended audience.


  1. Reporting - reporting can be complex if data from all (or multiple) organisations is required
  2. Process disparity - without proper control on design and architecture, the applications/ functionalities within each environment can become more and more disparate, leading to operations challenges
  3. Complex user provisioning - a user may be required to be setup in multiple organisations based on needs
  4. Licensing - If a user is required to access more than one organisation, they'll need to have dedicated user account in each org (unless a specific mechanism is built to expose data to them in some way). This leads to additional licensing costs
  5. Complex application maintenance - with some common functionalities across all organisations, it can be complex to roll-out changes in these functionalities across all organisations


Popular posts from this blog

Quick Tips: Salesforce default Images

Well, I'm sure a lot of you still rely on using out of the box salesforce images for displaying quick icons within formula fields or even using them within your Visualforce pages. Lately, I realized that a lot of earlier resources are no longer accessible, so I tried to quickly extract all images from Salesforce CSS files and provide a quick reference here. Please note, I've referenced all images from SF servers directly, so if anything changes, the image should stop rendering here. As these images are completely controlled by Salesforce, and in case they change anything, it might lead to image not being accessible. Image path Image /img/samples/flag_green.gif /img/samples/flag_green.gif /img/samples/flag_red.gif /img/samples/color_red.gif /img/samples/color_yellow.gif /img/samples/color_green.gif /img/samples/light_green.gif /img/samples/light_yellow.gif /img/samples/light_red.gif /img/samples/stars_100.gif /img/samples/stars_200.gif /img/samples/stars_300.

Lightning: Generate PDF from Lightning components with in-memory data

I'm sure as everyone is diving into lightning components development, they are getting acquainted with the nuances of the Lightning components framework. As well as, its current limitations. Being a new framework, this is bound to happen. Although we have our users still using salesforce classic, we have started using lightning components framework our primary development platform and Visualforce is considered primarily for rendering lightning components within Classic Service console. Recently, while re-architecting a critical module, we encountered a problem wherein we needed to generate PDF from lightning components. Now, being Javascript intensive framework, it has limited room for such features (may be included in future roadmap). As of now, there is no native feature within the lightning framework to do so (at least I didn't find anything). Common Scenario - Create Visualforce page to retrieve data and generate PDF For scenarios where the data exist within Sa

Lightning: Generate PDF within Lightning Experience with Salesforce Data

Some time back I posted a solution to generate PDF from Lightning components using in-memory data. Post url: It was developed for a specific scenario, wherein we need to generate PDF where: User interface is Salesforce classic Initiated via Lightning Component Data doesn't exist within Salesforce and is completely in-memory As complex and tricky this situation was, we did end up finding a stable and equally tricky solution. However, I realize that there are still lack of solutions (or maybe my search skills are downgrading) to generate and automatically download PDF document from Lightning Experience, without using any lightning components, wherein data exists within Salesforce. You can use the earlier solution in that case, but it will be an overkill. There are various solutions available to generate PDF from javascript. But, I still think the plain old method of converting HTML to PDF (via