Audit log or field history in Zoho CRM: which one answers which question
Use the audit log when you need to know who changed what across your whole Zoho CRM account. Use field history when you need the sequence of values on one record. The audit log and field history in Zoho CRM do different jobs. The log covers every record and can be exported. Field history sits on the record and shows how it got to its current state.
The audit log is a chronological sequence of entries, each one resulting from an action a user performed in Zoho CRM. Zoho also calls it an audit trail. Field history is the record-level trail of changes. In Zoho CRM it comes in two forms.
The Timeline shows the actions performed on a single record. Picklist history tracking records each change to the values of one chosen picklist field.
This guide explains what each tool records and who can see it. It shows you how to settle a dispute with them. It also lists the fields to track before go-live, because history you never switched on cannot be recovered later. If you are new to the product, the basics of Zoho CRM cover the modules and records this post refers to.
What the Zoho CRM audit log records, and what it leaves out
The Zoho CRM audit log records every time a record is created, edited, updated, deleted or imported. It also captures account setup actions. According to Zoho's audit log FAQs, the log covers bulk actions as well.
These are the bulk actions Zoho lists as captured in the audit log:
- Mass update
- Mass delete
- Import
- Export
- Restoring records from the recycle bin
Workflow changes are logged in detail. Each entry shows who made the change, when they made it, which workflow they changed and the name of the rule. Zoho's help page on monitoring the log adds actions such as locking a rule or adding an action to it. When an automation suddenly starts behaving differently, this is usually where you find the cause.
The audit log does not record logins. Zoho states that login history is captured in Zoho Directory instead. If your question is "who signed in on Tuesday evening", you are looking in the wrong place.
The log also does not show you a tidy story for one record. It lists actions across all records in time order. That makes it strong for "what did this user do last week" and weak for "how did this deal's value change over three months". For the second question you need field history.
Who can see the Zoho CRM audit log, and where to find it
Access to the Zoho CRM audit log follows your role hierarchy. Zoho's help page states that no specific permission is needed to open the feature. However, users see only their own entries and those of their subordinates. Zoho's pages say the CEO role and the CRM account administrator can see everyone's entries.
The role hierarchy matters here. A sales rep who opens the log sees their own work. A team manager sees their team. If you need a view across departments, ask an administrator, or someone in the CEO role, to run the search.
To open the log, go to Setup > Security Control > Audit Log. The page shows all actions by all users over the last three years. From there you filter by four things:
- Entity: a module, setup or analytics
- User: the person who acted
- Action: Added, Updated or Deleted
- Time: a selected date range
Zoho One also has its own audit logs for organisation-wide activity. Examples are adding an application or importing users in bulk. Viewing those needs the Organization Owner or Organization Admin role. The steps vary between the three user interface versions Zoho One supports. For changes to CRM records, the CRM audit log is the one you want.
If your role hierarchy is still loose, fix it first. A log that the wrong people can read, or the right people cannot, is little use in a dispute. Territory management in Zoho CRM covers how visibility and ownership interact.
Field history in Zoho CRM: the Timeline and picklist history tracking
Field history in Zoho CRM means two features: the Timeline, which every record has, and picklist history tracking, which you switch on per field. They answer different questions about the same record.
The Timeline
The Timeline is a record-specific history of the actions performed on that record. A Zoho community post notes that it shows when a lead moves from one user to another. That is useful for ownership disputes. The limit is in Zoho's FAQs: a Timeline can only be viewed within the record. It cannot be downloaded or exported.
Picklist history tracking
Picklist history tracking records each time the value of a picklist field changes. A picklist is a drop-down field with fixed values, such as Lead Status. The history appears as a related list on the record. Managers can use it to see how long a record spent in each status.
Picklist history tracking has firm limits you should know before you plan:
- You can track one picklist field per module.
- Once enabled, tracking applies across all layouts.
- It is not available for picklist fields in Tasks, Calls or Meetings.
- If you disable tracking or delete the field, all tracked data is lost permanently.
- Creating a field with the "Also create for" option does not enable tracking. You must enable it on the actual field.
You can also choose a related field to record alongside the picklist. Pairing Quote Stage with Amount, for example, shows how a quote's total varied across its stages.
Audit log, Timeline or picklist history: a decision table
The right tool for tracing a change in Zoho CRM depends on the question, the audience and how long you need the answer. The table compares the three tools on the points that matter in a dispute.
| Question | Audit log | Timeline | Picklist history |
|---|---|---|---|
| Scope | All records and setup actions | One record | One picklist field per module |
| Best for | Who did what, across the account | What happened to this record | How long a record sat in each value |
| Setup needed | None, on by default | None, on by default | Enable per field before data arrives |
| Can you export it? | Yes, as CSV | No | Shown as a related list on the record |
| How long it lasts | Last 3 years, then deleted | Not stated in Zoho's help pages | Lost if tracking is disabled or the field deleted |
| Who can see it | Own and subordinates; administrator and CEO see all | Anyone who can open the record | Anyone who can open the record |
Read the table as a sequence. Start with the Timeline for a single record because it is quickest. Move to picklist history when the dispute is about status or stage. Go to the audit log when you need evidence you can export and hand to someone else.
Standard reports do not replace any of these. A Zoho community user found that reports could only filter by a record's last modification. That filter also catches records where any other field changed.
Worked example: proving when a lead moved from Open Lead to Contacting
This worked example traces one status change in Zoho CRM with all three tools. It is based on a setup a user described in the Zoho community. Every new lead gets the Lead Status "Open Lead". A rep changes it to "Contacting" once they call, email or message the lead.
Suppose two reps both claim they contacted the same lead first, and commission depends on it. Here is how you settle it.
- Open the lead and read the Timeline. It shows the actions on that record, including any change of owner. You now know who owned the lead and when.
- Check the picklist history related list. If you enabled tracking on Lead Status before go-live, you see each value change in order. The move from Open Lead to Contacting has a time against it.
- Confirm in the audit log. Go to Setup > Security Control > Audit Log. Filter Entity to Leads, Action to Updated, then each rep in turn under User, with a date range around the change.
- Export the evidence. Click Export Audit Log. Because you applied Entity, User or Action filters, include a time filter within a 180-day range. You get a CSV file you can share.
The same user wanted a report counting how many leads each rep moved from Open Lead to Contacting in a week or month. Reports on last modification could not do it. Picklist history tracking on Lead Status gives you the record of each move. Without it, the audit log is your fallback, filtered per user and period.
Which fields to track in Zoho CRM before go-live
Decide which fields to track before you import data, because picklist history tracking only allows one picklist per module. Disabling it later deletes everything it recorded. Pick the field that drives money or accountability in each module.
These are sensible first choices for most sales teams:
- Leads: Lead Status, so you can see time spent in each status and who moved it.
- Quotes: Quote Stage, with Amount as the related field, so changes in value show against each stage.
- Deals: check what the Stage History list already shows before you spend your one tracked picklist. One community user found their custom fields were not available when customising that view.
- Your own modules: whichever picklist a customer or colleague is most likely to dispute.
Fields that are not picklists, such as owner or a value field, still appear in the audit log as updates. Ownership changes also show in the Timeline. You do not need to track everything. You need to track the field you will be asked about.
At Svennis we agree the tracked field for each module with the client during the build and switch tracking on before the first import. We then put a recurring audit log export in the administrator's calendar, so the first one is not left until someone asks for it. If the field design is still moving, settle it first; how to customise your CRM covers that work.
Audit log retention: three years, then the entries are gone
Zoho CRM keeps audit log actions from the last three years and permanently deletes anything older. The FAQ is direct about it: any action before that period is gone. If a dispute concerns a contract signed four years ago, the CRM log will not help you unless you saved it.
For that reason Zoho recommends exporting your audit logs periodically. An export is a CSV file you store yourself. It keeps its contents for as long as you keep the file.
Deleted records have a shorter window. Zoho's help pages state that records deleted within the last 60 days can be retrieved from the Recycle Bin. After that, the audit log entry shows that a deletion happened, but the record itself is no longer there to restore.
Backups follow a similar pattern. A community user reported that Zoho CRM's automatic backups still have to be downloaded and stored by the customer. Treat the audit log the same way. The data exists inside Zoho for a fixed period. Long-term custody is your job.
Field history has its own risk. Picklist history is lost if someone disables tracking or deletes the field. Limit who can edit field properties in your administrator profiles, and write the tracked fields into your admin notes so nobody switches one off by accident.
Exporting the Zoho CRM audit log, by hand or through the API
You export the Zoho CRM audit log as a CSV file from Setup > Security Control > Audit Log, using the Export Audit Log option on the right-hand side. You must be logged in with Administrator privilege.
The export has two modes, and the limits differ:
- Unfiltered: up to the last three years, or up to one million entries.
- Filtered: if you apply an Entity, User or Action filter, you must include a time filter within a 180-day range.
In practice, a full unfiltered export is the simplest periodic routine. Run it, name the file with the date, and store it somewhere access-controlled. Use filtered exports for specific investigations, such as the lead example earlier in this guide.
Some teams want the export automated. A Zoho community user reported that, according to the Zoho CRM API v7 documentation, creating an audit log export needs the scope ZohoCRM.settings.audit_logs.CREATE. A scope is a permission string an API client requests. The same user got an "Invalid Scope" error when generating a code for a Self Client app, on a newly created trial account. If you plan to automate, test the scope on your own paid account before you build around it.
Whichever route you choose, check the first export. Open the CSV and confirm it contains the modules and users you expect. Do this before you need the file in a dispute.
What audit logs and field history mean for a UK company
For a UK company, the audit log and field history in Zoho CRM are your evidence when someone questions how customer data changed. That person might be a customer, a director, an auditor or a rep chasing commission. The tools are only useful if they were switched on and the exports kept.
Three situations come up often:
- Commission and target disputes: picklist history on the status or stage field settles who moved a record and when.
- Customer questions about their own data: when you respond to a subject access request under UK GDPR, a filtered audit log export helps you find what changed on that person's records. Check any entries about colleagues or other customers before you send it, and redact them unless those people agree or it is reasonable to disclose.
- Unexplained automation changes: the audit log names who edited a workflow rule and which rule it was.
Check your own record-keeping policy against Zoho's limits. The CRM keeps audit entries for three years. If your policy says longer, the periodic CSV export is how you meet it. Remember that login history is not in the CRM audit log; it sits in Zoho Directory.
People matter as much as settings. Tell your team that changes are logged, and explain why. That reduces arguments before they start. The change management glossary entry covers how to introduce rules like this without resistance.
Next steps: switch on tracking and set an export routine
You can set up the audit log and field history in Zoho CRM in an afternoon. Work through these steps in order.
- Open Setup > Security Control > Audit Log and confirm you can see entries for all users. If not, check your role.
- List the modules you use. For each, choose the one picklist you are most likely to be asked about.
- Enable history tracking on each chosen field, from Setup > Customization > Modules and Fields, in the field's Edit Properties.
- Restrict who can edit field properties, so tracking is not disabled by accident.
- Run a full audit log export, open the CSV and check it.
- Put a recurring export in an administrator's calendar, agree where the files are stored and how long you keep them, and delete old exports when that period ends.
- Tell your team what is tracked and why.
If you are past go-live, do the same steps now. History starts from the day you switch it on, so every week you wait is a week with no record. For broader configuration beyond these basics, intermediate Zoho CRM covers the next layer of settings.
If you would rather have the tracked fields, permissions and export routine set up as part of a wider build, see how Svennis approaches Zoho CRM implementation and consulting.
