Blog

Google Sheets as a lead CRM: keep it fast and under the cell limit

· SyncYak team

  • sheets-automation
  • google-sheets
  • lead-tracking

Plenty of solo agents and small teams run their leads out of a Google Sheet. It is free, everyone already knows it, and you can sort, filter and color rows the way you think. It works well until the sheet gets slow, a tab fills with duplicate rows, or someone pastes over a column of phone numbers.

This post covers how to set a lead sheet up so it stays fast, where the hard limit is, and which parts you should automate instead of typing.

The limit you will eventually hit

Google caps a single spreadsheet at 10 million cells. Google's Workspace Updates blog announced the increase from 5 million in March 2022, and the cap counts the whole file, including blank cells and every tab.

Ten million sounds like more than a lead tracker could ever use. The math says otherwise once you stop thinking in rows:

  • A lead tab with 40 columns costs 40 cells per lead. A sheet that holds 100,000 leads is already at 4 million cells.
  • Google Sheets allocates cells in a grid. A tab created with 1,000 rows and 26 columns takes 26,000 cells even when it is empty, so extra blank rows and columns count against the cap.
  • Every extra tab with copied data, "working" versions and old exports adds up.

In practice you feel slowness well before the cap: large formulas that recalculate on every edit, VLOOKUP over whole columns, and filter views over tens of thousands of rows all drag. The cell limit is the wall, but the slowdown is what makes people abandon the sheet.

Design the sheet for one row per lead

The structure of the sheet decides how long it lasts. Use these rules:

  1. One row per lead, one tab per kind of record. Leads on one tab, deals on another, tasks on a third. Do not put a lead's notes in a second row of the leads tab.
  2. A stable ID column. Use the ID your CRM or lead source gives each lead, not the name. Names change, phone numbers get reformatted, and two people share an email address. An ID does not change.
  3. Fixed columns for facts, your own columns for opinions. Name, email, phone, source and stage are facts. Score, "call tomorrow" and notes are yours. Keep them side by side, but know which are which.
  4. No blank padding. Delete the empty rows and columns you do not use. In Sheets, select the unused rows, right-click and delete them; the cell count drops immediately.
  5. Archive on a schedule. Once a lead is closed or dead for six months, move the row to an archive file. Your working sheet should hold only the leads someone will still act on.

Replace lookups over whole columns with ID matches

The most common reason a lead sheet crawls is formulas that scan more than they need to. A few changes help a lot:

Slow, scans the whole column on every recalculation:
=VLOOKUP(A2, Agents!A:F, 3, FALSE)

Better, bounded range and exact match:
=INDEX(Agents!$C$2:$C$500, MATCH($A2, Agents!$A$2:$A$500, 0))

Bound every range to the rows you really have. Avoid volatile functions such as NOW() and INDIRECT() in per-lead columns. And do not compute the same value in 40,000 rows if one lookup table could hold it.

For enrichment, such as the agent who covers a zip code, the loan officer for a listing or a campaign name for a source, put the reference data on its own small tab keyed by that value. A roster of a few hundred rows is cheap. Repeating the roster inside every lead row is not.

Stop typing leads into the sheet

Manual entry is where duplicates and typos come from. The two sources of leads are your inbox and your CRM, and both can write to the sheet for you.

From lead emails

If your leads arrive as emails from Zillow, Realtor.com or your own website forms, you can forward them to an inbox that reads the name, phone, email and property out of the message and adds one row per lead. SyncYak Parse does this: you share the destination sheet with SyncYak's address, paste its link, pick the tab, and each parsed email adds one row. The free plan covers 100 emails a month, and the plans are listed on the pricing page.

Before a row is written, a Google Sheets lookup can match a parsed field to a row of a second sheet and copy the columns you pick into the lead. That is how a lead for zip code 78704 arrives already carrying the agent's name and phone. Lookups start on the Hobby plan. If no row matches, you choose whether to deliver the lead without those columns or hold it until someone replays it.

From your CRM

If your leads already live in Follow Up Boss, Lofty, HighLevel or Cloze, you do not need to export CSV files and paste them in. The CRM module copies leads into a Google Sheet on every plan: one tab per object, one row per lead, updated by the CRM's own lead ID, with deleted leads marked and your own columns left alone. See CRM to Google Sheets for the details.

That last point matters for the design above. Because the sync matches on the ID, it updates the row it already wrote instead of adding a duplicate, and the columns you added for scores and notes are not overwritten.

Write enrichment back instead of copying it by hand

A sheet is a good place to compute things: a lead score, a persona, a pre-approval status. The weak spot is copying those values back into the CRM, where your agents actually work.

With field mapping, the sheet becomes the source. Keep one row per lead keyed by the CRM lead ID, and map each column header to a CRM custom field. When a row is added or changed, SyncYak writes the values into the lead. An empty value never clears a field, so a half-filled row cannot wipe out data an agent entered. Writing back to the CRM is available from the Hobby plan. The lead enrichment from Google Sheets page walks through both directions.

A maintenance routine that takes ten minutes a month

Even a well-built sheet needs a little upkeep. Put this on the calendar:

  1. Look through the tab list for stray copies and delete the ones nobody uses.
  2. Trim blank rows and columns from each tab.
  3. Move closed and dead leads older than your cutoff to an archive file.
  4. Open the slowest tab and replace any whole-column formula with a bounded one.
  5. Confirm the ID column has no blanks. A row without an ID cannot be matched on the next sync.

When to move to a database

A sheet is the right tool while one person can read the whole table. If you are past 100,000 leads, running reports across several CRMs, or joining leads to transactions, a real database makes more sense. The same CRM sync can send leads to your own Postgres or MySQL instead, so you can start with a sheet and change the destination later without losing history.

How SyncYak helps

SyncYak keeps the sheet current so you do not have to. Parse turns lead emails into rows, with lookups that add the right agent before the row is written. The CRM module keeps one row per lead up to date by ID and writes your enrichment back to the CRM. You keep the sheet; SyncYak does the typing and the matching.

Start with one inbox or one CRM connection on the free plan: create your account and point your next lead at a clean row.

Start free with SyncYak · All posts