With the prevalence of Salesforce in the marketplace, more and more companies are finding themselves operating multiple instances of Salesforce, whether through mergers and acquisitions or because different departments or business units rolled out unique instances due to the ease and speed of implementation. While circumstances may dictate the need to maintain multiple organizations due to requirements such as security, code or API call limitations, varied licensed edition requirements (Unlimited versus Force.com licensing), companies should take a long hard look at the benefits of merging their Salesforce.com orgs into a single instance. Even if the company needs to partition their org by function, division, business unit, company, product, or however requirements dictate, Salesforce’s innate features and functionality allow for companies to develop applications within applications. So unless the circumstances force you to maintain or build multiple orgs, your multiple org environment should be evaluated for the advantages of one platform.
For a company, the overhead and administrative costs of maintaining multiple orgs are usually the most obvious determinant to a single org strategy. In an initial rollout, these costs include user licensing fees, implementation costs, and on-going administration. But as your company gets more entrenched in the Salesforce ecosystem, the costs of maintaining multiple orgs start to expand when a company considers integrations and 3rd party applications.
Licensing –Salesforce’s traditional licensing model is per seat. Whether you have management or executives that will need access to multiple orgs or have cross-department functional roles that need multi-org access, you will have overlap in your licensing fees.
Implementation – The cost of standing up a Salesforce org from scratch is higher than adding a new business unit or department function to an existing org
Administration – Maintaining your Salesforce environment is an ongoing function. Day to day operations of managing your user base, loading data, managing business operations realignments or process changes, producing reports or troubleshooting errors requires resources. And as your business usage evolves, you will gather new requirements for extending your functionality, implementing new functionality and taking advantage of release updates that are introduced several times per year. For a company with multiple Salesforce orgs, these resources would be required for each org. Having a single org can reduce the resources required for these changes.
….. Want to learn more? Download the full white paper below.
Download the White Paper