Salesforce org analyzer and health check

An org health check you can rerun

A one-off assessment is out of date the week after it is delivered. MetaLens360 works from scheduled syncs, so the same checks run again whenever the org changes, and history lets you see whether a refactor actually moved the numbers.

• Org Overview. Four lenses on one org — what it does, how it is architected, how it connects to the enterprise, and what needs attention — with a measured profile and a Word export for handovers.
• Platform limits. API calls, storage and other org limits tracked over time, with the ones trending to exhaustion called out.
• Automation architecture. Every trigger, queueable, batch, schedulable, future method, Platform Event and callout, with async chains of three or more hops ranked by risk and objects with more than one trigger listed.

Performance and governor health grade

The performance health grade rolls an org's SOQL and data-access analysis into a single A to F grade. The score is 0.4 × data access health + 0.3 × (100 − duplicate SOQL %) + 0.3 × repository adoption %, and the evidence behind it is on the same page: the transactions closest to the 100-query limit, amplification hotspots where the same data is queried repeatedly, and an estimate of how many queries removing duplicates would save. Query Amplification snapshots taken before and after a change let you prove the improvement.

Salesforce technical debt analysis

• Dead code. A component is listed as safe to delete only when it has no inbound references, no @AuraEnabled, @InvocableMethod, @RestResource or @RemoteAction annotation, is not an async entry point and is not global. Code called dynamically by name is flagged as a risk rather than hidden.
• Orphaned automation. Change data capture analysis finds orphaned listeners and change capture that nothing in metadata consumes; Flow analysis finds automation with risky patterns such as DML in loops or missing entry criteria.
• Anti-patterns. Architecture intelligence grades patterns as Anti-pattern, Inconsistent, Not present or Healthy, and shows the components with the largest blast radius.
• Rule-based findings. Code Analyzer scans Apex, triggers and Flows against a tunable rule catalog and compares two scans to show what is new and what was resolved.

Drift and comparisons

Environments drift. A comparison between two orgs, an org and a Git branch, or two branches shows what matches, what was modified and what is missing on either side, and Drift Overview rolls every comparison into the metadata types that drift most. Promotion tracking shows whether a change has reached dev, QA, UAT or production.

CRM Analytics lineage

For orgs that run CRM Analytics (formerly Tableau CRM and Einstein Analytics), the CRM Analytics assessment parses recipes, dataflows, datasets and dashboards into lineage — what feeds an asset, what it feeds and what breaks if it changes — with a weighted health score and a Keep, Fix, Consolidate or Retire recommendation per asset. Assets whose usage could not be confirmed are marked Retire (unverified), never silently counted as unused.

Answers with evidence

Measured numbers come from the index, not from a model. Written findings are tagged by how firmly the metadata supports them, and the org-aware copilot cites the components behind each answer and says when it cannot tell. MetaLens360 reads metadata and never deploys to your org. For the component-level view, see the Salesforce metadata analyzer.