Salesforce health check
A Salesforce health check from an independent consultancy: adoption, data quality, technical debt, security and permissions, licence utilisation and reporting, ending in a costed roadmap and a renewal position. The same CRM audit is available for HubSpot and Dynamics 365 orgs.
Delivered for and alongside
































A typical Salesforce org is five or more years old and has passed through several admins, two or three partners and at least one reorganisation. Nobody holds the whole picture, the renewal is approaching and someone has asked whether Agentforce should be switched on. That is the moment for a Salesforce health check: a structured review of a live org by people who neither built it nor sell the licences.
Salesforce gives admins useful instruments. Security Health Check in Setup scores the org against the Salesforce Baseline Standard and groups settings into high, medium, low and informational risk. The Org Health and Usage page adds cards for login errors, guest user exposure, unassigned permission sets, Apex limit consumption, storage, pending release updates and the licences nearest their maximum. The optimisation report app Salesforce used to offer, which pulled much of this together, was scheduled for retirement in Winter '26, and Salesforce's replacement advice is a list of manual checks in Setup and SOQL queries.
Those tools measure the org against Salesforce's standards. They do not tell you whether sales managers trust the forecast, whether finance recognises the account list, how much of the licence bill is idle or what it would cost to switch off the automations nobody understands. A CRM health check answers those questions across six areas: adoption, data quality, technical debt, security and permissions, licence utilisation and renewal, and reporting. We run the same review on HubSpot and Dynamics 365 Customer Engagement orgs, because the questions are identical even when the tooling is not. If the org is still being built rather than lived in, our Salesforce implementation consultancy page is the better starting point.
Beyond what Setup tells you
Adoption first, because an org nobody uses has no data worth cleaning. The Lightning Usage App shows daily and monthly active users, the pages visited most, the slowest record pages and the count of active user, feature and permission set licences, so we can see which teams live in Salesforce and which log in once a month to update a forecast they keep elsewhere. We then interview the people behind those numbers. The regional manager with a private spreadsheet usually has a reason, and it is often a design fault rather than a training gap.
Data quality follows. We profile the core objects for completeness, age and duplication: accounts with no owner or industry, contacts with no activity in two years, opportunities past their close date, picklists with twelve values that mean the same thing. Salesforce duplicate management rests on matching rules, which define what a match is, and duplicate rules, which decide whether to block or warn, and we check both are active and sensible. Leads and contacts are different objects and cannot be merged directly, so weak conversion discipline shows up in the data at once. Storage matters too: an org gets 10 GB of data plus 20 MB per Enterprise user licence, and old tasks and attachments fill it quietly.
Reporting comes last because it inherits every problem above. We list the dashboards executives actually open, trace each figure back to the fields and stages it depends on, and show where two dashboards disagree and why. In a HubSpot portal the equivalent evidence comes from the data quality overview and the duplicates tool, which surfaces up to 10,000 duplicate pairs on Professional and Enterprise. In Dynamics 365 it comes from Dataverse capacity reporting, where exceeding the tenant's storage blocks environment copies and restores and, after 90 days, locks every user out of the affected sandboxes.
Data quality, profiled
Salesforce stopped supporting Workflow Rules and Process Builder on 31 December 2025. Existing automations still run, but Salesforce no longer fixes bugs in them or takes support cases, and it points customers at its Migrate to Flow tool. Many orgs still carry dozens of these, often firing alongside flows and Apex triggers on the same object in an order nobody has written down. We inventory every automation per object, trace the firing order and recommend which to rebuild, merge or retire.
Apex gets the same treatment. Production deployments need unit tests covering at least 75 per cent of the code, so a falling coverage number is an early sign that nobody is maintaining the classes. We check API versions as well, because Salesforce treats code bound to old versions as a maintenance issue, and we look at the invalid and outdated classes the Org Health page lists.
Security and permissions are where a review earns its fee. We read the Security Health Check score and the settings behind it, test what guest users can reach, and map profiles, permission sets and permission set groups to the people who actually hold them. Permission sets assigned to a handful of users, or to nobody at all, are a recurring finding.
Integrations are reviewed for API consumption against the daily allocation, for error handling and for ownership. A HubSpot to Salesforce sync alone can use up to four API calls per contact each time it runs. For Dynamics 365 orgs we run the Power Platform solution checker, which performs static analysis of plug ins, web resources and flows and flags deprecated patterns such as the Dynamics CRM 2011 object model. PEF holds basic membership of Microsoft's AI Cloud partner programme, with no Solutions Partner designation and no fees or incentives from Microsoft. Where a system is heading for replacement rather than repair, our CRM migration page sets out the route.
The automation debt
The licence review starts in Company Information and the Most Used Licenses card: how many of each licence type you own, how many are assigned and, from Login History, how many of those users have signed in recently. Then it moves to the paperwork. Salesforce's Main Services Agreement renews subscriptions automatically for a further year unless written notice is given at least 30 days before the term ends, does not allow quantities to be reduced during a term, and lets promotional pricing renew at list price. If you want fewer seats, a different edition mix or price protection, the work has to be done before that notice date, and a health check three to four months out gives you the evidence to do it.
The edition question is live for every customer in 2026. Core, Advanced and Max replaced Enterprise, Unlimited and Agentforce 1 in September, Salesforce says legacy pricing is unchanged for existing customers, and Premier Success is bundled with the new editions rather than sold on top. Whether moving is worth it depends on what you actually use, which is exactly what the review has just measured. Our Salesforce pricing guide carries the current UK list prices.
You receive a written report with findings graded by risk and cost, a prioritised backlog of fixes with effort estimates, a twelve month roadmap and a one page renewal brief. Our team ran the procurement of every software provider on the National Grid separation, and that experience shapes the renewal advice. The reviewers themselves are PEF consultants who have led and analysed the decisions before, during and after CRM implementations and migrations. Under Part A we review and advise while your admin team or partner carries out the fixes; under Part B our practitioners do the work. Our fees are shown plainly on the pricing page. For platform specific support see HubSpot consultancy and Dynamics 365 Customer Engagement, or contact us to scope a review.
Why timing the review matters
Ran the procurement of every software provider on the National Grid separation, more than 22 million assets, through to implementation including Oracle to SAP S/4HANA.
Delivered the Oracle to Microsoft Dynamics migration at BP Pulse 39 days ahead of forecast, with a £25m saving, the largest on a programme where PEF held the main contract.
Delivered the £9bn Energy Bills Support Scheme for Ofgem, BEIS and HMRC.
Implemented and delivered most major finance systems over 19 years: Oracle, Microsoft Dynamics, NetSuite, Sage, SAP S/4HANA, Unit4 and Access.
A suite of consultants who have led and analysed pre, mid and post migration decisions and implementations across ERP and CRM platforms, independent of every vendor.
A structured review of a live Salesforce org covering adoption, data quality, technical debt in flows, Apex and integrations, security and permissions, licence utilisation and reporting. It ends with graded findings, a prioritised backlog with estimates and a roadmap. Salesforce's own Health Check in Setup scores security settings only; an independent review covers the whole org and the commercial position as well.
Setup tools such as Security Health Check, the Org Health and Usage page and the Lightning Usage App measure the org against Salesforce's standards and report usage. They cannot tell you whether the forecast is trusted, which automations are safe to retire, what the idle licences cost or how the renewal should be negotiated. An independent CRM audit interprets those readings against your business and puts a cost and a priority on each fix.
Our fees are shown plainly on the pricing page. The effort depends on the size of the org: the number of users, objects, automations and integrations, and whether HubSpot or Dynamics 365 systems are in scope as well. A review of a single org with a few integrations is a short engagement; a multi org estate with a marketing platform attached takes longer. We agree the scope and the price before starting.
Yes. The questions are the same for any CRM: who uses it, how clean the data is, what debt the automations and integrations carry, who can see what, which licences sit idle and whether the reports are trusted. Only the tooling differs. In HubSpot we use the data quality overview and the duplicates tool; in Dynamics 365 we use the Power Platform solution checker and Dataverse capacity reporting.
Three to four months before a renewal, because Salesforce requires written notice at least 30 days before the term ends and quantities cannot be reduced mid term. Also before switching on Agentforce or any AI feature, which depends on clean data and tidy permissions; after a partner or lead admin leaves; and before deciding whether to migrate to another platform rather than repair the one you have.
Where next
Book an independent review before the renewal notice date, and decide from evidence rather than habit.