> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/crm/zoho-crm/best-practices.md).

# Best Practices

## Recommended setup

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Start with a single module</strong></td><td>Test your connection with just Leads or Contacts first. Once it works, add more modules. This helps you catch configuration issues early and makes troubleshooting easier if something breaks.</td></tr><tr><td><strong>Set a start date to limit initial sync</strong></td><td>If you have years of CRM data, sync the last 30–90 days first. This avoids timeout and lets you verify the data looks right before pulling everything.</td></tr><tr><td><strong>Use Join transformations for related data</strong></td><td>Deals are most useful when linked to Account names and owner info. Set up a Join in Coupler.io to merge Deals with Accounts so you see full context in your destination.</td></tr><tr><td><strong>Match your edition to your plan</strong></td><td>When creating the data flow, select your actual Zoho CRM edition (Free, Standard, Professional, etc.). This ensures Coupler.io respects your API rate limits and doesn't over-request.</td></tr></tbody></table>

## Data refresh and scheduling

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Schedule syncs during off-peak hours</strong></td><td>Run data flows early morning or late evening to avoid competing with your team's manual Zoho CRM usage. This reduces timeout risk and keeps API quota available for salespeople's live work.</td></tr><tr><td><strong>Use daily or every-6-hours refresh for active pipelines</strong></td><td>If Deals and Contacts change frequently, daily or every-6-hour syncs keep your destination fresh without hammering the API. Hourly syncs are risky for Free/Standard editions with lower quotas.</td></tr></tbody></table>

## Performance optimization

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Filter to essential fields only</strong></td><td>Syncing 50+ fields per module slows the export. Identify which columns your dashboard or report actually needs and exclude the rest. Fewer fields = faster syncs and smaller file sizes.</td></tr><tr><td><strong>Use Replace mode for module snapshots</strong></td><td>If you're syncing Deals or Accounts as a daily snapshot (not a log of changes), set the data flow to "Replace" mode. This overwrites old data instead of appending, keeping your destination clean and query-fast.</td></tr></tbody></table>

## Common pitfalls

{% columns %}
{% column %}
**Do**

* Test a new data flow with a manual run before scheduling it
* Keep API tokens secure and rotate them every 6 months
* Use the Sandbox environment to test field changes before syncing to Production
* Set a start date on the first sync to avoid pulling all historical data
* Split large modules (1M+ records) into multiple data flows or time windows
  {% endcolumn %}

{% column %}
**Don't**

* Share your Zoho CRM API token with team members; use separate tokens per integration
* Sync every field if you only need a few; this wastes API quota
* Schedule data flows for the same minute across multiple sources; stagger them by 10 minutes
* Change your Zoho edition and forget to update it in Coupler.io; this causes rate limit mismatches
* Assume custom fields are included; verify your admin has enabled API access for them
  {% endcolumn %}
  {% endcolumns %}

{% hint style="danger" %}
**Critical: Never store API tokens in spreadsheets or shared documents.** Zoho CRM API tokens grant full read access to your CRM data. Keep them in Coupler.io's vault and rotate them if you suspect exposure.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/crm/zoho-crm/best-practices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.