FieldRat vs HappySoup

HappySoup showed you which fields were empty.
FieldRat tells you whether they are safe to delete.

HappySoup focused on population percentages. FieldRat covers the same field usage analysis and adds dependency scanning, risk scoring, and retirement workflow so you know it is safe before you delete. One missed dependency in a Flow can break a production process.

Jump to the capability matrix
See all compare pages
Schema, not records Managed Salesforce package Free

Status check. As of June 1, 2026, happysoup.io redirects to dx0.io. Community discussion and founder comments indicate a transition from HappySoup to dx0.

What FieldRat adds

Everything HappySoup did — and what it never could

HappySoup answered one question: what percentage of records on this object populate this field? That number alone does not tell you whether a field is safe to delete. FieldRat covers the same population analysis and adds the dependency, risk, and evidence layers admins actually need to retire fields with confidence.

Field Analysis — the same population reporting, free

HappySoup's core workflow was field population percentages. FieldRat Field Analysis covers the same job: pick object, set threshold, review candidates. Always free.

Quick Scan — the gap HappySoup did not close

HappySoup answered population. Quick Scan answers where a field is still referenced across 11 critical metadata types natively in Salesforce.

0-100 Deletion Risk Score

Population percentage is not a deletion decision. FieldRat combines usage, dependency breadth, and critical hits into a single risk score for consistent prioritization.

Field Dictionary — your Salesforce data dictionary

Searchable org-wide object and field inventory with point-in-time exports for compliance review. Always free.

Deep Scan — 23 metadata types for complete coverage

Quick Scan covers native critical types. Deep Scan extends to 23 metadata types via metadata ZIP, including reporting-layer references.

Retirement workflow + audit trail

HappySoup gave discovery; FieldRat adds tracked retirement states, reviewer assignment, review dates, and App Log audit trail.

Capability matrix

Side by side, capability by capability

Tie means both tools cover the job. Where the matrix shows FieldRat alone, the capability never existed in HappySoup.

CapabilityFieldRatHappySoupEdge
AppExchange availability (May 2026)Listed; managed Salesforce packageTransitioning to dx0
Field population / usage analysisAsync Salesforce Batchable; built for high-volume orgsPopulation percentage report
Dependency scanning (where is this field used)Quick Scan 11 metadata types + Deep Scan 23 metadata typesNot supported
100% native Salesforce, schema-onlyQuick Scan is 100% native; no record values leave the orgNative, freeTie
0–100 Deletion Risk ScoreComposite score using usage, dependency breadth, critical hitsNot supported
Searchable data dictionaryField Dictionary — your Salesforce data dictionary, always freeNot supported
Run Comparison / drift detectionSide-by-side comparison of any two completed runsNot supported
Scheduler / recurring analysisConfigurable schedule per objectNot supported
Retirement workflow + audit trailStatus tracking, reviewer assignment, App Log audit trailNot supported
Custom field limit trackingPer-object utilization vs Salesforce 800-field capNot supported
Excel + CSV evidence exportExcel workbook + CSV with dependency status, risk, source pathCSV usage report
CostFree; monthly scan allowancesWas free (no longer listed)Tie

The replacement path

If you used HappySoup, here is the migration

Coming from HappySoup

Start with Field Analysis

  • Field Analysis covers the same population workflow HappySoup teams already know.
  • Run threshold-based candidate discovery across high-volume objects.
  • Keep discovery free while adding safer decision layers only when needed.

Then upgrade the workflow

Add dependency evidence and risk scoring

  • Use Quick Scan to surface critical metadata references before deletion.
  • Use Deep Scan for broader 23-type coverage when retirements are high risk.
  • Prioritize with 0-100 risk scoring instead of population-only judgment.
  • Track deletion decisions through retirement states with exportable evidence.

FAQ

HappySoup questions, answered

01What changed with HappySoup?

As of June 1, 2026, happysoup.io redirects to dx0.io. Public community discussion and founder comments indicate a transition from HappySoup to dx0.

02Is FieldRat a HappySoup alternative?

Yes. HappySoup focused on population percentages. FieldRat covers the same population analysis and adds dependency scanning across 11 to 23 metadata types, a 0 to 100 Deletion Risk Score, a searchable Field Dictionary, Run Comparison for drift detection, a Scheduler, and a retirement workflow with audit-ready exports. Field Analysis and Field Dictionary are always free.

03Does FieldRat send Salesforce record data outside the org?

No. Quick Scan is 100% native to Salesforce. Deep Scan processes a metadata ZIP — schema, not record data — and the ZIP is deleted after analysis completes. Business record values never leave your org.

04How is FieldRat priced?

FieldRat is free. Field Analysis and Field Dictionary are always free; monthly Quick Scan and Deep Scan allowances apply per org. There is no per-user pricing and no credit card required. Hit the monthly cap while evaluating? No worries — email contact@fieldrat.app and we'll lift your allowance.

05Will FieldRat help with the Salesforce custom field limit?

Yes. The dashboard tracks per-object custom field limit utilization against the Salesforce 800-field cap, so you can free up headroom by retiring low-usage fields with evidence before hitting a hard limit.

Move on from HappySoup — with evidence.

FieldRat is free. Field Analysis and Field Dictionary are always free. See where every field is used, score the risk, and retire safely.