[ Salesforce Org Consolidation ] · Post-Merger Integration · 2026
When two companiesbecome one,the org follows.
Four enterprise consolidations, four industries, three continents.
Start the free auditSee case studiesTechila Global Services runs post-merger Salesforce org consolidation — merging, migrating, or retiring Salesforce estates object by object into a single target org. We have consolidated Salesforce environments for IGT × GTECH, loanDepot, Ebara–Kirloskar, and HDFC Bank — across gaming, mortgage lending, industrial manufacturing, and regulated banking.
IGT × GTECH · loanDepot · Ebara–Kirloskar · HDFC Bank
[ Salesforce Org Consolidation ]
When two orgs merge, so should the customer view.
Every acquisition arrives with its own Salesforce org — its own data model, its own automation, its own licence bill. Left alone, that duplication compounds: fragmented reporting, duplicate customer records, divergent security models, and two AppExchange bills for one combined business.
Techila’s Org Consolidation practice makes a merge / migrate / retire call on every object, and lands both estates on a single target org — without a compliance gap or a reporting blackout.
[ Who We Are ]
A Salesforce Summit Partner, the highest partner tier.
Salesforce transformations since 2012 for Fortune 500 and high-growth enterprises — every engagement led by a Summit-certified architect.
Org consolidation is where that bench earns its keep. We have merged Salesforce estates in gaming, mortgage lending, industrial manufacturing and regulated banking.
[ How We Consolidate ]
Five phases, one target org
The same method every time, tuned to the regulatory environment. Nothing moves until the merge / migrate / retire call has been made, object by object, and signed by an architect.
1. Discover and assess
An org-by-org audit of objects, automation, integrations, licences and technical debt.
2. Design the target org
One data, security and process model, with a merge, migrate or retire decision for each object.
3. Migrate and merge
Metadata harmonisation, survivorship rules, and staged loads that are reconciled after each run.
4. Rehearse and cut over
Production-scale dry runs, freeze windows and a rollback option at each gate.
5. Rationalise and run
Licence true-down, legacy org retirement, and a single managed-services and governance model.
[ Decisions ]
Merge, migrate or retire: how each item is decided
Every object, integration and licence gets one decision, signed off by an architect before anything moves. These are the standard decisions:
| Item | Decision | Note |
|---|---|---|
| Objects with the same purpose in both orgs (Account, Contact, Opportunity) | Merge into one target object | Define survivorship rules for duplicate records. |
| Objects that exist in only one org | Migrate as is, or redesign | Review whether the business still needs them. |
| Unused objects, fields and automation | Retire | Archive the data before removal. |
| Integrations pointing at either org | Re-point or replace | Inventory every inbound and outbound connection. |
| Licences and packages | Rationalise | Compare entitlements and renewals before cutover. |
| Users and identity | Consolidate with single sign-on | Resolve duplicate users across orgs. |
[ What We Bring to a Merger ]
What is included
- Metadata diff
- Compares objects, fields, flows, Apex and permissions across the orgs so that conflicts are known before design starts.
- Identity and single sign-on
- Maps users across orgs and puts one single sign-on in front of the target org.
- Golden records
- Defines survivorship rules so that duplicate accounts and contacts become one trusted record.
- MuleSoft re-pointing
- Moves integrations that used to talk to the old orgs onto the target org.
- CPQ merge
- Combines product, price book and quote configuration when both orgs use CPQ.
- Licence rationalisation
- Compares entitlements and renewals so that licences are reduced once the old orgs retire.
- Audit trail
- Records each merge, migrate or retire decision and each reconciliation result.
- Post-merge managed services
- Provides one support and release process for the single org after go-live.
[ Case Studies ]
Four consolidations. Four industries. Three continents.
Gaming & Lottery
IGT × GTECH
GTECH S.p.A. and International Game Technology combined in 2015 to form International Game Technology PLC — two global gaming and lottery businesses, each running its own Salesforce estate across separate geographies and operating models.
The Situation
- Separate Salesforce orgs spanning North American, Italian and LATAM operations
- Duplicate account and operator hierarchies for casino and lottery customers served by both legacy businesses
- Divergent case models, SLAs and escalation paths between the two service organisations
- Licence and AppExchange spend duplicated across both estates
What Techila Did
- Multi-org audit with a merge / migrate / retire call per object
- Unified operator hierarchy with survivorship rules for shared customers
- Consolidated case model, SLAs and escalation into the surviving org
- Re-pointed downstream integrations with no reporting blackout
- Region-phased cutover with follow-the-sun hypercare
The Outcome
Mortgage & Consumer Lending
loanDepot — five brands, one org
loanDepot grew by acquisition — folding in roughly five lenders including iMortgage — and every one arrived with its own Salesforce org, its own loan-officer roster and its own book of referral partners.
The Situation
- Five acquired brands running five Salesforce orgs with five different lead-routing models
- Loan officers, branches and referral partners duplicated across every org with no master record
- Compliance and audit reporting fragmented — no single view of a borrower across brands
- Each new acquisition took months to integrate under the existing approach
What Techila Did
- Repeatable acquisition-intake pattern, reused brand by brand
- Golden records for borrowers, loan officers and referral partners
- One lead-routing, territory and compensation model across channels
- Consolidated compliance and audit into one governed reporting layer
- Retired legacy orgs on each brand's licence renewal date
The Outcome
Industrial Manufacturing
Ebara + Kirloskar
Ebara and Kirloskar brought their pump and industrial-machinery operations together — combining a Japanese parent's global process standards with an Indian manufacturer's dealer, distributor and field-service network.
The Situation
- Two orgs built to different regional standards — Japanese HQ governance against Indian operating reality
- Dealer, distributor and service-partner records duplicated and inconsistently structured
- Product catalogues, price books and asset registers maintained separately per entity
- Field service, warranty and installed-base tracking with no common data model
What Techila Did
- Harmonised product, price book and installed-asset data models
- Merged dealer and distributor hierarchy with region-aware sharing
- Unified field service, warranty claims and installed-base tracking
- Multi-currency, multi-language rollout with locale-aware layouts
- Enabled users across multiple locations in multiple languages
The Outcome
Banking & Financial Services
HDFC Bank + HDFC Ltd
The 2023 merger of HDFC Ltd into HDFC Bank created India's largest private-sector bank and the largest merger in Indian corporate history — two of the country's biggest financial institutions, two Salesforce estates, one RBI-supervised cutover.
The Situation
- Banking and housing-finance estates built on fundamentally different customer data models
- Regulated environment with no tolerance for data loss, downtime or an unexplained record
- Merger-scale record volumes and a heavily overlapping retail customer base
- Cross-sell impossible without one customer view across both books
What Techila Did
- FSC target model spanning retail banking and mortgage products
- Customer identity resolution and golden records at merger scale
- Staged, reconciled migration with a regulator-grade audit trail
- Rehearsed cutover on production-scale data, rollback at every gate
- Weeks of hypercare, then unified cross-sell across both books
The Outcome
[ Why Techila Global Services ]
Why merge with a Summit partner.
Org consolidation carries the full weight of a merger — regulators, boards, and a customer base that can’t see downtime. It’s not a first engagement to hand to a generalist bench.
[ Related Services ]
Pair this with.
Salesforce Consulting
Strategic advisory and target-org roadmap planning ahead of a merger.
Explore→Salesforce Managed Services
Senior-led operations and governance once the consolidated org is live.
Explore→MuleSoft
Re-pointing integrations and API-led connectivity across the surviving org.
Explore→Salesforce Implementation
Full-lifecycle delivery for the newly designed target-state org.
Explore→[ FAQ ]
Frequently asked questions
What is Salesforce org consolidation?
Combining two or more Salesforce orgs into one, by merging, migrating or retiring objects, data, automation and users.
When is it better to keep separate orgs?
When regulation, data residency or very different business processes make a shared org costly or risky. The audit documents the trade-offs.
What does the free audit deliver?
A board-ready document within 15 days that lists each org's objects, automation, integrations, licences and technical debt, with a recommended target design.
What happens to the old orgs?
They are retired after cutover and a read-only period, usually timed to licence renewal.
[ Next Steps · Start With the Audit ]
Bring us your orgs. We'll bring the map.
A full org-by-org consolidation audit — objects, automation, integrations, licences and tech debt — with a phased target-state roadmap. Free, board-ready in 15 days, and yours to keep whether or not you engage us for the build.
Consolidation Track Record
Let's now look at how to build
the next 10 years of
your customer platform.