Google Sheets

Google Sheets has a hard, documented ceiling of 10 million cells per spreadsheet (as of current limits; Google has raised this over time, so check current documentation), and in practice performance degrades well before hitting that number -- heavy use of volatile functions (NOW(), TODAY(), RAND()) or array formulas spanning large ranges forces a full recalculation on every edit, which is usually what makes a "large" sheet feel sluggish rather than raw row count alone.

Practical Details

For genuinely large datasets, Connected Sheets lets you query a BigQuery table directly from within a sheet without importing the data at all, which is the real scaling path once a dataset is too big to live in Sheets natively. Splitting data across multiple linked spreadsheets with IMPORTRANGE, rather than one sprawling sheet with dozens of tabs, is the more common practical workaround for teams not on BigQuery.

Actionable considerations

1. Check your sheet's cell count against current documented limits before assuming a slowdown is a bug rather than approaching a real ceiling.
2. Audit for volatile functions (NOW, TODAY, RAND) and large array formulas if a sheet feels sluggish, since these force full recalculation on every edit.
3. Use Connected Sheets to query BigQuery directly, or split data across linked sheets with IMPORTRANGE, rather than growing one sheet indefinitely.

Moving into Google Sheets from another spreadsheet tool is mostly a file-open operation — Sheets can open .xlsx files directly and convert them, or you can import CSVs. Since Sheets lives in Drive, setup is really about organizing files into Drive folders and deciding who gets edit, comment, or view access; there's no separate admin console step for the spreadsheet itself. For pulling in data still live in other sheets, IMPORTRANGE keeps values synced instead of copy-pasting.

Practical Details

If the incoming workbook relies on VBA macros, those won't run in Sheets — they need to be rebuilt in Apps Script, which uses JavaScript instead. Formulas mostly carry over cleanly on import, though some Excel-specific functions may need adjusting. For migrating large tables or reports, QUERY and pivot tables usually replace whatever aggregation the old workbook was doing with static formulas.

Actionable Considerations

1. Import the existing file directly into Sheets rather than rebuilding it from scratch
2. Rewrite any VBA macros as Apps Script, since the two aren't compatible
3. Use IMPORTRANGE to keep linked data current instead of manually re-pasting it after migration

Sharing and access control for a spreadsheet run entirely through Drive's permission model (Viewer, Commenter, Editor, or link-based sharing) -- there's no separate, Sheets-specific security layer sitting on top of that. Within a file, Protected ranges and sheets let you lock specific tabs or cell ranges so only designated people can edit them, even for collaborators who otherwise have Editor access to the rest of the file.

Practical Details

Workspace admins control organization-wide external sharing defaults (whether files can be shared outside the domain at all) from the Admin console, separate from what any individual user configures on their own files -- getting this domain default wrong is a common source of accidental over-sharing. Version History (File > Version history) shows exactly who changed what and when, which is the practical first stop for investigating unexpected changes rather than restoring a full backup.

Actionable considerations

1. Use Protected ranges for sensitive tabs or cells rather than relying on file-level sharing alone to control who can edit what.
2. Check the domain-wide external sharing default in the Admin console, since it governs whether sheets can be shared outside your organization at all.
3. Check Version History before assuming data loss or unexpected changes require restoring from a separate backup.

Google Forms responses flow directly into a linked Sheets response tab automatically, and Looker Studio (formerly Data Studio) reads Sheets natively as a data source for dashboards -- both native Google Workspace connections requiring no setup beyond linking the two. Beyond native connections, Apps Script (Google's JavaScript-based scripting layer) handles custom code-driven integrations, like calling an external API and writing the result into cells, while Zapier and Make cover no-code connections to non-Google tools.

Practical Details

Built-in import functions -- IMPORTRANGE (pulling a range from another spreadsheet), IMPORTDATA, IMPORTXML, and IMPORTHTML (pulling from public web sources) -- handle a surprising amount of integration without any external tool or script at all, though IMPORTRANGE specifically requires a one-time manual access grant the first time it references a new source spreadsheet. For anything needing scheduled, unattended execution (a nightly data pull, for example), Apps Script's time-based triggers are the native mechanism, distinct from manually running a script on demand.

Actionable considerations

1. Use native Forms-to-Sheets linking and Looker Studio connections before reaching for a third-party tool for Google-to-Google workflows.
2. Try built-in IMPORTRANGE/IMPORTDATA/IMPORTXML/IMPORTHTML functions for simple data pulls before writing custom Apps Script.
3. Use Apps Script time-based triggers for anything needing scheduled, unattended automation rather than manually running scripts.

Gemini in Sheets, a paid add-on tied to Workspace licensing rather than a default feature, can generate a formula from a plain-language description, summarize or categorize the contents of a column, and build charts or pivot tables from a natural-language prompt rather than manual configuration. This is distinct from the long-standing, non-AI Explore panel (bottom-right corner of any sheet), which has for years surfaced suggested charts, pivot tables, and basic formula answers directly from your data without requiring any AI licensing at all.

Practical Details

Gemini-generated formulas and summaries should be checked against the actual data before being trusted for anything consequential, the same as any AI-generated output -- it's a drafting aid, not a substitute for verifying the underlying calculation is correct. Because Gemini access depends on specific Workspace licensing, confirm current availability for your organization rather than assuming every account has it.

Actionable considerations

1. Try the free, built-in Explore panel first for basic chart and formula suggestions before assuming you need a paid AI add-on.
2. Verify Gemini-generated formulas against the actual data before relying on them for anything consequential.
3. Confirm your organization's specific Workspace licensing includes Gemini in Sheets before building a workflow that depends on it.

Because Sheets syncs in real time with no separate save step, most teams already get some baseline benefit from collaboration without any process change -- but the real gain, avoiding "which version is correct" confusion, depends on whether a sheet actually uses structured features (named ranges, data validation dropdowns, protected ranges) rather than being treated as unstructured free text that multiple people edit inconsistently.

Practical Details

Comments and the @mention feature (assigning an action item to a specific person directly on a cell, which notifies them by email) are a concrete, underused mechanism for keeping discussion attached to the actual data point in question, rather than happening in a separate chat thread disconnected from the sheet itself. Data validation dropdowns, restricting a cell to a defined list of values, meaningfully cut down on the inconsistent free-text entries (three different spellings of the same status) that erode trust in a shared sheet over time.

Actionable considerations

1. Use @mentions in comments to assign action items directly on the relevant cell, instead of a disconnected chat thread.
2. Add data validation dropdowns for any field where free-text entry has historically caused inconsistent spelling or values.
3. Set up named ranges and protected ranges for a sheet's key inputs, since unstructured, all-editable sheets are what erode trust in shared data over time.

Google Sheets carries no standalone per-seat price -- it's bundled into every Google Workspace plan (Business Starter through Enterprise) and free with any personal Google account. The cost lever that actually matters is which Workspace tier you're on, since that governs storage pooling, admin console controls, and support access, not spreadsheet functionality itself, which is largely identical across tiers.

Practical Details

Connected Sheets, querying a BigQuery table directly from a spreadsheet, depends on BigQuery itself being provisioned and billed separately through Google Cloud, which is a real cost outside the Workspace subscription if a team wants to use it at scale. Add-ons from Google Workspace Marketplace can carry their own separate pricing as well, so a "free" spreadsheet workflow can pick up real costs once BigQuery or paid add-ons enter the picture.

Actionable considerations

1. Don't budget for a separate Sheets license -- confirm which Workspace tier you actually need based on storage and admin controls, not spreadsheet features.
2. Factor in separate Google Cloud/BigQuery billing if the team plans to use Connected Sheets at real scale.
3. Check pricing on any Marketplace add-on before rolling it out broadly, since these aren't covered by the base Workspace subscription.

Google Sheets is the spreadsheet app in Google Workspace, built around real-time multi-user co-editing rather than file-locking or check-in/check-out. Multiple people can work the same sheet at once, see each other's cursors, and changes save automatically to Drive — there's no separate save step and no merge conflicts to resolve. Sharing and access control run through Drive's permission model (viewer, commenter, editor, or link-based sharing), not a standalone permissions system layered on top of the spreadsheet.

Practical Details

Beyond basic formulas, Sheets has Apps Script, a JavaScript-based scripting layer for custom functions, macros, and automation (Google's equivalent to Excel's VBA, though the language and APIs are different). The QUERY function lets you run SQL-like statements against a range, and pivot tables handle the same kind of aggregation without writing formulas. IMPORTRANGE pulls data from other spreadsheets, and Connected Sheets lets you query BigQuery datasets directly from a sheet when the data is too large to import normally.

Actionable Considerations

• Set sharing at the Drive file or folder level — Sheets doesn't have its own separate permission system
• Use Apps Script for repetitive tasks or custom functions instead of chaining complex formulas
• For datasets too large to paste in, connect via IMPORTRANGE or Connected Sheets to BigQuery rather than duplicating data