Field Trip
Scans every record to find fields with zero or low population. Reports on field usage across reports, list views, page layouts, and automations. Flags candidates for deprecation. Tracks usage trends over time.
Why it ranks here
- Only tool focused exclusively on field-level adoption; catches unused fields that dependency tools miss
- Data-driven deprecation decisions instead of guessing
- Tracks trends: shows if a field was used last year but abandoned this quarter
Where it sits
- Deeper field analysis than Sonar or Elements for actual record population
- Narrower scope: fields only, no broader governance
- More accurate than native Schema Builder for real-world usage
How GTM Systems teams use it
- Run quarterly field audits to identify deprecation candidates
- Measure field adoption after launching new processes or integrations
- Generate field inventory reports for data governance and compliance teams
- Prioritize field cleanup by combining usage data with dependency maps from Sonar
In-depth notes
- Pricing is per-org; one-time or annual license
- Requires read access to all objects; some orgs balk at permissions
- Usage stats are backward-looking; does not predict future need
- Pairs well with Sonar: Sonar shows technical dependency, Field Trip shows actual use
- Some teams run it once per quarter instead of keeping it always-on
Best for
Orgs with 500+ custom fields and an active deprecation program
Avoid if
Field bloat is not a problem or cleanup is not a priority
The rest of Documentation & governance
Learning guide
Setup
Install the app, grant read access to all objects, then run your first scan to find fields with zero or low population across all records.
First thing to build
Generate a quarterly field audit report showing which custom fields are unused, prioritize deprecation candidates, then cross-check technical dependencies in Sonar before deleting.
What actually matters
- Scans every record to measure actual field population
- Tracks usage trends over time to catch abandoned fields
- Reports on fields used in reports, layouts, and automations
- Refresh manually each quarter or on-demand
Watch out
Usage stats are backward-looking; a field unused today might be needed next quarter for a new process.