Connect Zoho CRM to Looker Studio: Sheets Guide

See your Zoho CRM sales pipeline in Looker Studio with a total you can compare with the selected CRM records. For a first report, export the agreed Deals fields, load them into a private Google Sheet and connect that worksheet. For recurring reporting, assess a suitable connector or an owned API extraction against the same requirements.

Google's current documentation calls the reporting product Data Studio. This guide uses Looker Studio, the name many teams still search for. Google's separate Looker BI platform and Zoho Analytics have different connection routes.

The downloadable example contains six fictional deals and shows £30,000 of open pipeline. You can inspect the source columns, reporting rows and expected results before arranging access to your own accounts.

Choose the route that fits the update you need

Google's connector directory lists Sheets and BigQuery, but does not list a Google-built Zoho CRM connector. A community connector can connect an external API; assess the specific provider's modules, field types, permissions, retained history, charges and update behaviour. Zoho Marketplace also lists a third-party Looker Studio connector for Zoho CRM, developed by Jivrus Technologies. A listing alone does not establish that it covers your reporting scope; confirm the provider's current terms and test the selected records.

Zoho's native CRM-to-Zoho Analytics connector connects those two Zoho products. It does not establish a native CRM-to-Looker Studio connection. For Zoho Analytics, use our separate Zoho CRM to Zoho Analytics guide. For platform selection, read Zoho Analytics vs Looker Studio.

Download the sales pipeline example

Download the complete example ZIP, or inspect the illustrative CRM export, stage mapping, prepared reporting CSV, local normaliser, expected results and README. The files are available without an enquiry.

The fixture represents one invented CRM organisation, one GBP currency and a snapshot at 14 October 2026, 23:59:59 UTC. Its identifiers, export headings, stages and amounts are illustrative. Your CRM's fields and stage definitions need their own mapping.

These are current deal values. They do not establish invoiced revenue, recognised revenue or cash receipts. The closing-date field is retained for inspection; it is not a verified stage-change history.

1. Select and export the CRM records

In your own CRM, agree the organisation, module, included records, currency and cut-off with the sales reporting owner. Begin with Deals. Select a stable deal identifier, name, stage, amount, currency or documented organisation-currency basis, closing date and owner identifier.

Zoho's export instructions cover module exports and selected-record exports. Access requires the profile's Export (Module) permission. Check the selected view, fields and current export limits rather than assuming an export represents every deal your team can report on.

Keep IDs as text, especially long numeric CRM identifiers. Use one row per deal in the selected snapshot. Keep stage labels in a mapping owned by your sales team: the example maps Qualification, Proposal and Negotiation to open, and two illustrative closing stages to won or lost. Those labels are not a universal Zoho configuration.

For the teaching exercise, use looker-studio-deals.csv directly. To reproduce its transformation locally, extract the ZIP, read the normaliser and run:

python3 normalise-zoho-export.py

The script reads the supplied export and stage map, then rewrites the prepared six-row CSV. It rejects repeated or blank deal IDs, unmapped stages, unsupported currencies and invalid amounts or dates. It reads local files only. Adapt the export mapping and currency policy before using another organisation's data.

2. Load one private Google Sheets worksheet

Create a Google Sheet and use File → Import to load looker-studio-deals.csv into a new worksheet. Keep the first row as column headings, one record per row and a consistent type within each column. Omit spreadsheet totals and merged cells from the connected range.

The reporting table contains deal_id, deal_name, stage, deal_status, amount, currency, closing_date, owner_id and snapshot_at. Preserve identifiers as text, amounts as numbers and closing dates as dates. Set the spreadsheet locale to match the file's decimal and date representation, then inspect a sample amount and date.

For a later manual update, replace the previous snapshot rows in the same worksheet and update the recorded cut-off. Appending every export would repeat deals. If you retain multiple snapshots for trends, include the snapshot in the grain and make the report select the intended snapshot.

3. Connect the worksheet to Looker Studio

Following Google's Sheets connection instructions:

1. Open the reporting tool and choose Create → Data Source → Google Sheets.
2. Select the spreadsheet and worksheet. Use the first row as headers, then choose Connect.
3. Review the detected fields. Set identifiers, stage, status, currency and the snapshot label to Text, amount to Number and closing_date to Date.
4. Add a report and a table containing deal_id, stage, deal_status, amount and currency. Confirm the six records before building the headline cards.
5. Set the deal-count metric to Count Distinct of deal_id and the value metric to Sum of amount.

Google's Sheets connector reads a single worksheet per data source. Use additional data sources only when the report needs another worksheet and you have defined how its records relate to Deals. Joining one deal to several activities can repeat its amount.

4. Build the cards and check their filters

Create an open-pipeline count card and value card. Filter each to deal_status = open and currency = GBP. The expected results are 3 deals and £30,000. Create separate won and lost value cards with the corresponding status filters: £15,000 won and £5,000 lost.

Leave date filtering off for the first fixture check. A report date control can otherwise change the compared record set using the current closing-date field. Agree the relevant date before adding monthly reporting.

Compare the six deal IDs and their amounts with the source export. Confirm that all six sum to £50,000, then check each status separately. The all-deal total is a reconciliation control; the open-pipeline card includes only the three open deals.

The sample's current closed-deal win rate is 2 won ÷ (2 won + 1 lost) = 66.67%. Calculate it from the included deal counts, rather than averaging owner or stage percentages. It describes the current statuses in this fixture, not a period-based win rate or a cohort's conversion.

5. Agree freshness, permissions and the live route

Google's data freshness settings govern when the report requests data from its source. They do not export Zoho records or update the Sheet. Record the CRM extraction time, successful Sheet update and displayed snapshot together so your team can assess how current the report is.

Choose owner or viewer credentials and restrict the Sheet and report to the intended audience. Owner credentials can let a report viewer see data without direct access to the underlying Sheet. Check the report using the intended viewer account before sharing it more widely.

For a recurring API route, use Zoho CRM's v8 Get Records API with authorised read access, the actual field API names and complete pagination. Its maximum is 200 records per page; a first successful response is not proof of a complete extract. Use the api_domain returned by Zoho's OAuth flow for the correct environment and data centre. Keep credentials in the extraction service, outside the Sheet and shared report.

Stage the agreed records in a supported source, such as BigQuery, when volume, retained snapshots or reuse justify it. Agree incremental updates, deletion handling, currency rules, ownership and monitoring before scheduling the report. Our data integration service describes that delivery scope.

Discuss your Zoho CRM reporting

Tell us about your Zoho CRM reporting: your CRM organisation and modules, the Looker Studio report you need, currencies, existing Google setup and update frequency. The link opens an editable integration enquiry.

See our published BI pricing for delivery bands. If you are still deciding on the reporting destination, keep that decision separate from this connection walkthrough and use the platform comparison.

Technical sources checked on 17 October 2026. The downloadable fixture and local transformation are validated separately from authenticated CRM extraction, Google chart execution, permissions and scheduled updates, which require testing in your own accounts.