Definition
Field History Tracking is a Salesforce administration feature that helps system administrators configure, secure, and maintain their org. It provides control over how the platform behaves and how users interact with data and functionality.
Real-World Example
Consider a scenario where an admin at Redwood Financial is working with Field History Tracking to ensure the Salesforce org runs smoothly and securely. They configure Field History Tracking during a scheduled maintenance window, test it in a sandbox first, and then deploy to production. The result is tighter security and a more streamlined experience for all 200 users in the org.
Why Field History Tracking Matters
Field History Tracking is a Salesforce feature that records changes to specified fields on standard and custom objects, maintaining an audit trail of who changed what, when, and what the old and new values were. Unlike Feed Tracking (which posts changes to the Chatter feed), Field History Tracking stores change data in a structured related list on the record and in queryable history objects (like AccountHistory and OpportunityFieldHistory). This data can be used in reports, dashboards, and even automated processes. Organizations can track up to 20 fields per object, and history data is retained for up to 18 months by default (extendable to 24 months with a policy or longer with Big Object archival).
As regulatory requirements and internal governance mature, Field History Tracking becomes essential for compliance, dispute resolution, and data forensics. Financial services firms need audit trails showing when deal amounts or risk ratings changed. Healthcare organizations must document when patient record fields were modified. Sales leaders use Field History to analyze how opportunity stages progressed and identify deals that were pushed out repeatedly. Without Field History Tracking, organizations have no way to reconstruct what happened to a record, making it impossible to investigate data quality issues or respond to audit inquiries. The 18-month retention limit is a critical consideration — organizations that need longer-term history should archive data to Big Objects or external systems before it's automatically purged.
How Organizations Use Field History Tracking
- Redwood Financial — Redwood Financial enabled Field History Tracking on the Opportunity object for Amount, Stage, and Close Date. During quarterly business reviews, sales VPs pull reports showing how many times each rep's deals changed close date, identifying reps who consistently push deals and need pipeline management coaching.
- Sentinel Healthcare — Sentinel Healthcare tracks changes to the Patient Status, Treatment Plan, and Assigned Provider fields on their custom Patient Record object. When a regulatory audit requires proof of treatment plan modifications, the compliance team generates a Field History report showing every change with timestamps and user names.
- Apex Legal Group — Apex Legal Group uses Field History Tracking on their Contract object to track changes to Contract Value, Terms, and Expiration Date. When a client disputes a contract modification, the legal team pulls the Field History related list to show exactly when the change was made and by whom, resolving disputes with documented evidence.