Global
Salesforce Org Consolidation
Expertise to rationalize business process, consolidate data and optimize license costs
Salesforce Integration
What Ness Offers
Companies use multiple Salesforce Orgs to manage the rapid growth due to M&A, or to scale business units adopting their own Orgs tied to products and teams. Over time, companies end up having multiple Salesforce Orgs for different business units, regions, and business functions.
Consolidation is not an easy task and should start with an effort to standardize business process across the company followed by arriving at the right strategy for consolidating a Salesforce Org.
Salesforce Integration
What Ness Offers
Companies use multiple Salesforce Orgs to manage the rapid growth due to M&A, or to scale business units adopting their own Orgs tied to products and teams. Over time, companies end up having multiple Salesforce Orgs for different business units, regions, and business functions.
Consolidation is not an easy task and should start with an effort to standardize business process across the company followed by arriving at the right strategy for consolidating a Salesforce Org.
Innovative Solutions
Key Steps for Salesforce Org Consolidation
Business Process Standardization
- Go-To-Market strategy and goals
- Business units and operating structure
- Sales territories and team structure
- Process governance structure
Org Consolidation Strategy
- Business needs / requirements
- Salesforce apps currently in use
- Tech debt and customizations
- Technology governance structure
Architecture Alignment
- Process standardization
- Process integration
- Data governance structure
- Regulatory requirements
Salesforce License Rationalization
- Salesforce users across company
- Users that access multiple orgs
- Shared roles
- AppExchange add-on licenses
Innovative Solutions
Key Steps for Salesforce Org Consolidation
Business Process Standardization
- Go-To-Market strategy and goals
- Business units and operating structure
- Sales territories and team structure
- Process governance structure
Org Consolidation Strategy
- Business needs / requirements
- Salesforce apps currently in use
- Tech debt and customizations
- Technology governance structure
Architecture Alignment
- Process standardization
- Process integration
- Data governance structure
- Regulatory requirements
Salesforce License Rationalization
- Salesforce users across company
- Users that access multiple orgs
- Shared roles
- AppExchange add-on licenses
Considerations and Rationale
Key Considerations for Salesforce Org Consolidation
Thinking holistically is the right way to go about Salesforce Org consolidation. It is essential that Sales Process is aligned with company’s GTM strategy, customer data needs deduplicated and consolidated, Salesforce Org needs to be designed to handle all processes and data, and all this needs to be done with full transparency with customers, partners, and employees.
Considerations and Rationale
Key Considerations for Salesforce Org Consolidation
Thinking holistically is the right way to go about Salesforce Org consolidation. It is essential that Sales Process is aligned with company’s GTM strategy, customer data needs deduplicated and consolidated, Salesforce Org needs to be designed to handle all processes and data, and all this needs to be done with full transparency with customers, partners, and employees.
Methodology
Experience The Ness Approach
Our methodology consists of assessing current business processes and salesforce instances (for functionality, data, and integrations) followed by design and implementation of target state business processes and systems.
4-6 WEEKS
Assess
As-is Business Processes Current Salesforce Instances, Data, Integrations
- Analyze as-is business processes and analyze for similarity and variances
- Analyze current salesforce instances and analyze for functionality, level of customizations, utilization of licenses, data, file storage, and integrations
- Develop technology strategy aligned with GTM objectives
- Develop business process and technology integration project roadmap
4-6 WEEKS
Design
Target Business Processes Target Salesforce Instance, Data Migration, Integrations
- Design future state processes, including retired process and exceptions by product line / business units
- Design data consolidation templates, mappings of fields
- Hi-level target system design for Salesforce modules
- Design target state integrations with field mappings
- Build detailed project plans for implementation
- Develop training and change management plan
18-30 WEEKS
Implement
Target Business Processes Target Salesforce Instance, Data Migration, Integrations
- Build product backlog, prioritize backlog
- Develop sprint plans
- Configure Salesforce target instance
- Conduct sprint reviews and demo to finalize the functionality with Product Owner approval
- Develop integrations and system test
- Migrate data and test using sample data set
- Develop cutover and rollout plan and execute
- Develop and deliver end user training
Methodology
Experience The Ness Approach
Our methodology consists of assessing current business processes and salesforce instances (for functionality, data, and integrations) followed by design and implementation of target state business processes and systems.
4-6 WEEKS
Assess
As-is Business Processes Current Salesforce Instances, Data, Integrations
- Analyze as-is business processes and analyze for similarity and variances
- Analyze current salesforce instances and analyze for functionality, level of customizations, utilization of licenses, data, file storage, and integrations
- Develop technology strategy aligned with GTM objectives
- Develop business process and technology integration project roadmap
4-6 WEEKS
Design
Target Business Processes Target Salesforce Instance, Data Migration, Integrations
- Design future state processes, including retired process and exceptions by product line / business units
- Design data consolidation templates, mappings of fields
- Hi-level target system design for Salesforce modules
- Design target state integrations with field mappings
- Build detailed project plans for implementation
- Develop training and change management plan
18-30 WEEKS
Implement
Target Business Processes Target Salesforce Instance, Data Migration, Integrations
- Build product backlog, prioritize backlog
- Develop sprint plans
- Configure Salesforce target instance
- Conduct sprint reviews and demo to finalize the functionality with Product Owner approval
- Develop integrations and system test
- Migrate data and test using sample data set
- Develop cutover and rollout plan and execute
- Develop and deliver end user training