Taking over a Sales Cloud org starts with measuring: dormant leads and opportunities, duplicates, logins, profiles, inherited automations. Native screens are enough, but Salesforce Optimizer is being retired. Workflow Rules and Process Builder have been unsupported since December 31, 2025, while still running. Our order: process, security, data, automations, adoption.
A Salesforce built in a hurry, inherited from another provider, or simply neglected: the situation is more common than the brand-new project. Sales reps keep their pipeline in a spreadsheet, forecasts are redone by hand, and nobody knows anymore what a given automation triggers. Before touching anything, you need to measure. This article describes the signs we look at, the native screens that show them, and the order in which we take over a Sales Cloud org. Sources were read on November 13, 2026.
01Eight signs of an org that needs a takeover
Salesforce publishes no alert threshold: the ones we use are our own reading, and we set them with you. The signs themselves can all be observed on standard screens.
| Sign | Where to see it | What we infer from it |
|---|---|---|
| Leads open for months, neither converted nor disqualified | Lead report, by status and age | Qualification is not being run |
| Open opportunities with a past close date | Opportunity report, by close date | The pipeline is not used for forecasting |
| Duplicates, inactive duplicate rules | Duplicate rules and matching rules | Trust in the data is damaged |
| Licensed users who do not log in | Login History | To be cross-checked with record creations and updates |
| Workflow Rules and processes still active alongside flows | Setup, Migrate to Flow tool | Duplicate behaviors are possible |
| A very large number of custom profiles | Profiles and permission sets | Security was built one exception at a time |
| Setup changes made in production by many people | Setup Audit Trail | There is no release framework |
| Custom fields that are rarely filled in | Reports or queries: Salesforce has no native report for this | The data model grew without sorting |
02The native diagnostic tools, and the one that is gone
A serious diagnosis requires no paid tool. It requires knowing where to look.
- Setup Audit Trail shows the twenty most recent changes and lets you download those of the last 180 days, with the date, the author and the nature of each change (documentation).
- Login History keeps up to 20,000 logins over six months, exportable (documentation). A login does not prove usage: the Trailhead module User Adoption Metrics recommends tracking record creations and updates as well.
- Health Check compares your security settings with a baseline and gives a score out of 100 (documentation). It only covers security, and Trailhead warns that fixing a risk in one click can disrupt an integration.
- Duplicate rules rely on standard matching rules for accounts, contacts and leads, and can alert or block data entry (Trailhead module).
One tool is missing from this list: Salesforce Optimizer. Long cited as the starting point of an audit, it is being retired by Salesforce, which now points to several separate screens. Likewise, no native report gives the fill rate of a field, as Salesforce states itself: we measure it with queries.
03Workflow Rules and Process Builder: what to do?
Salesforce no longer supports Workflow Rules or Process Builder as of December 31, 2025. Active automations continue to run as before: what has stopped is support and bug fixes. So there is no need to convert everything overnight, but there is a reason to plan.
The Migrate to Flow tool, available from Setup, converts a rule or a process into a flow, lets you test it in Flow Builder, then switches the activation from the old to the new (Trailhead project). It does not suit every case, and we have not reread the list of its limits. Our rule: use the migration to group the automations of a given object, rather than copying one by one rules whose purpose nobody remembers.
04The order in which we work
No official source prescribes an order for a takeover. This one is ours, justified by dependencies.
- Understand the real sales process - before opening Setup. What sales reps actually do, step by step, and what management wants to read.
- Security and sharing - who sees what. The Salesforce Well-Architected guide invites you to start with trust and reliability; data seen by the wrong people cannot be taken back.
- The data model and its quality - fields to keep, duplicates to handle, sales stages to redefine.
- Automations - once the model is stable, group them and migrate to Flow.
- Adoption - train on real data, then measure logins, creations and updates every month.
Each step is delivered separately. Teams keep working in the org during the takeover: we never ask you to stop selling in order to rebuild the CRM.
05What we avoid
- Starting from scratch by reflex. An org holds data, habits and integrations that have value. We sort what is kept, what is simplified and what is rebuilt.
- Deleting before measuring. A field that looks useless sometimes feeds a management report or an integration.
- Fixing in production. Changes go through a test environment, then through a traced release.
- Promising a quantified gain. We measure the starting point, and we measure again afterwards.
06Our approach
We start with a free Health Check: a thirty-minute conversation, a read-only look at your org, written feedback on three priorities. Do not confuse it with the Salesforce Health Check screen, which only looks at security. If the org warrants it, we continue with a full audit (page in French), which ends with a roadmap. The takeover itself relies on our Sales Cloud expertise, and on our migration method when data comes from another tool.