Fixing Salesforce Org Sprawl: What It Actually Takes to Move Forward
The previous article in this series described how Salesforce org sprawl develops — the piecemeal purchases, the uncoordinated contracts, the gradual accumulation of technical and commercial complexity that nobody planned for and nobody owns. This article is about what to do once you're there.
The honest starting point is that this is harder than most organisations expect, and slower. The path forward is not a project plan. It's a structural change — commercial, technical, and organisational — that requires genuine commitment from the right people and a realistic view of what the journey looks like. Organisations that approach it with that clarity tend to make progress. Organisations that treat it as a tidy IT initiative tend to stall.
Here is what actually works.
Recognition is a process, not a moment
The first thing to understand is that there is rarely a single moment when an organisation wakes up to its multi-org problem. It happens gradually, through multiple conversations over an extended period, and it is rarely driven by one person or one function.
In practice, the recognition process tends to involve three parties working toward the same conclusion from different directions. Architecture is raising the technical complexity in its forums. Procurement is looking at multiple renewal notices and recognising the commercial inconsistency. And the Salesforce account team — often the one with the clearest view of the whole picture, because they can see all the contracts from their end — is having quiet conversations with the CIO about whether the current structure is serving the organisation well.
None of these parties owns the problem. That is precisely the issue. Architecture can describe it. Procurement can quantify part of it. The Salesforce AE can surface it. But the decision to actually do something about it requires an executive who is willing to take ownership of a change that will be complex, expensive, and unpopular with some business unit leaders. Until that person exists, the conversations circle without landing.
The implication for anyone trying to move this forward inside an organisation is to resist the pressure to resolve it quickly. The recognition phase takes as long as it takes. Pushing for a premature decision — before the right people genuinely understand the problem and are committed to addressing it — produces announcements without outcomes. The goal of the early conversations is alignment, not acceleration.
You cannot do this without external help
Once the organisation has genuinely recognised the problem and committed to addressing it, the next reality to accept is that it cannot do this alone.
This is not a reflection on the internal team. It is a reflection on what the process requires. Working through an org rationalisation involves navigating Salesforce's commercial structures, understanding the technical implications of different consolidation paths, and facilitating conversations between business unit owners who have competing interests and entrenched positions. The organisations that try to manage this entirely with internal resource — usually by assigning it to someone who already has a full-time job — consistently underestimate how much it demands.
External help means a Salesforce implementation partner or an independent consultant who has been through this process before. What they bring is not just knowledge — it's the standing to facilitate conversations that internal parties cannot, and the ability to translate between the commercial, technical, and political dimensions of the problem in a way that keeps all three in view simultaneously.
What the organisation needs to bring to that engagement is equally important. Two things matter most. The first is genuine knowledge of the business — what each org is actually doing, who uses it, what processes it supports, and what the business units actually need going forward. Without this, any consolidation path risks solving the architectural problem while breaking the operational one.
The second is a Salesforce roadmap. This is the thing most organisations don't have and most urgently need. Where does the organisation want to go with Salesforce over the next three to five years? Which products are in scope? Which business units might come onto the platform that aren't on it yet? What does the organisation's relationship with Agentforce and Data Cloud look like? The org structure decision is not just about cleaning up the past — it has to support the future. A roadmap, even a rough one, is the essential input to making a consolidation decision that will still make sense in three years.
The commercial path: early renewal as a fresh start
On the commercial side, the mechanism that typically makes rationalisation viable is the early renewal.
An early renewal is essentially a complete rewrite of the organisation's existing Salesforce contracts. Whatever unused credit remains on the existing agreements is carried across and applied to the new contract. The existing contracts are retired. The organisation starts fresh — with a single agreement, aligned renewal dates, and a commercial structure that reflects the consolidated environment rather than the accumulated history.
This is usually brought to the table by the Salesforce account team. From Salesforce's perspective, an early renewal is an opportunity to get the commercial relationship onto a stable, consolidated footing — higher total contract value, longer term, stronger enterprise commitment. That gives the customer some genuine leverage. An organisation that is willing to commit to a multi-year enterprise agreement, and that comes to the table with a clear view of its consolidated requirements, is in a reasonable negotiating position.
One thing to be clear-eyed about: consolidating multiple orgs into one will almost certainly require more base capacity in the single org than was available in any of the individual orgs being merged. A single org that needs to accommodate everything that was previously spread across three environments will need more storage, more processing capacity, and potentially different licensing tiers than any of those three orgs carried individually. This is not a reason to avoid consolidation — it is a reason to model the consolidated requirements carefully before the renewal conversation begins, so there are no surprises when the numbers come back.
Contract date alignment — bringing multiple renewal cycles into a single date — is genuinely straightforward. There is no particular downside here, and the administrative simplification alone is meaningful. Procurement managing one renewal conversation is categorically easier than managing four.
The platform team: the structural requirement most organisations get wrong
The commercial and technical work of rationalisation is tractable. The harder problem — and the one that most organisations consistently underestimate — is standing up the governance structure required to make any of it stick.
An org consolidation without a platform team is not a solution. It is a temporary fix that will accumulate new problems at the same rate the old ones were cleared. The only durable answer is a Salesforce platform team with genuine enterprise-wide authority, a defined mandate, and real budget.
In practice, for a mid-market organisation that is working through this for the first time, that team is built from what already exists. The Salesforce administrators and developers who have been working within individual business unit orgs are the foundation. They are brought together under a shared function rather than sitting within separate business units. Added to that is an architect — this can be a part-time or fractional role in smaller organisations, but it cannot be absent entirely — and a platform owner who is accountable for the Salesforce environment at an enterprise level.
Where this team sits in the organisational structure matters. For organisations that already have a platform team managing other enterprise systems, Salesforce belongs there. The governance model, the funding model, and the cross-business-unit operating model are already in place. Slotting Salesforce into an existing enterprise platform function is significantly more tractable than creating the entire model from scratch.
For organisations where Salesforce would be the first cross-enterprise platform — where there is no existing model for central platform ownership — the challenge is substantially harder. It requires not just creating the team but creating the cultural and structural conditions for it to function. That is a significant change management undertaking, and it should not be underestimated.
Funding is non-negotiable and it has to come from the centre. The CIO or CTO needs to recognise the platform team as a legitimate cost and fund it from central IT budget. An organisation that expects the platform team to be funded by the business units it is supposed to govern has not understood the problem. Business units that have been accustomed to owning their own Salesforce environment will not voluntarily fund a central function that reduces their autonomy. Central funding is not just a practical requirement — it is a signal that the organisation is serious about the change.
A realistic timeline
The most useful thing to know before starting this process is how long it actually takes.
Six months is the minimum for an organisation that moves decisively — where the recognition has already happened, executive sponsorship is in place, and the external support is engaged quickly. Even in the best-case scenario, the commercial negotiation, technical planning, and governance setup consume that time.
Twelve months is the more realistic target for most organisations. The recognition phase takes longer than expected. The platform team takes time to stand up. The business units take time to come along. Twelve months from genuine commitment to a functioning consolidated model is an achievable goal for a mid-market organisation that is well-supported.
Beyond twelve months, the risks compound. At eighteen months, organisations that have not made decisive progress start to lose momentum — the executive sponsor's attention moves elsewhere, the business units resume operating independently, and the consolidation effort begins to feel like a distraction rather than a strategic priority.
At twenty-four months, most programmes that have not reached a functioning state are quietly cancelled. The organisation reverts to something close to what it had before, often with more documentation of the problem and less appetite to try again.
The implication is straightforward: start with a realistic view of what this takes, secure genuine executive commitment before the process begins, and move with enough pace that momentum doesn't dissipate before the structural changes are in place. The organisations that get this right treat urgency and patience as complementary — patient about the recognition phase, urgent about execution once the commitment is made.
That combination is rarer than it should be. It is also the difference between the organisations that resolve this and the ones that don't.
Mike Roberts spent over eight years at Salesforce, including time as a Strategic Account Director, before founding Aequus Consulting. He works with New Zealand organisations on Salesforce licence optimisation and renewal preparation, with no vendor affiliations.