Google Sheets Compatibility and Migration Decisions

Quick answer

Decide whether the working master will remain an Excel file or become a native Google Sheets file before inviting edits. Opening an Office file in Sheets and converting it are different workflows. Neither proves that every formula, automation or collaboration requirement has survived.

Scope: Google Sheets in a desktop browser, a rolling web service; first-party documentation checked 21 October 2026. Mobile interfaces and paid Workspace-only capabilities are not assumed. This reference describes an acceptance plan, not a completed conversion or authenticated application test.

Choose one authoritative master

Google distinguishes editing an Excel file in its original Office format from creating a native Sheets copy. Conversion leaves the Excel original unchanged and creates a separate Sheets file. A downloaded Excel copy is another deliverable, not a promise of synchronization. Record the master URL or path and the purpose of each copy so collaborators do not update competing versions. Google’s Excel and Sheets guidance

Use these questions to choose a trial:

• Must the recipient keep an Excel-format deliverable, or can the team adopt a native Sheets master?
• Does the recipient need to change inputs, run automation, refresh data or only read a dated result?
• Which exact browser or receiving spreadsheet application will be used?
• Who is authorized to access the source data and approve a change of storage location?

Do not upload a real workbook merely to discover whether conversion works. Start with a private synthetic copy in an existing authorized account, and stop if access or permissions are unavailable.

Check size and long text before conversion

Google’s Drive file-size reference, checked October 23, 2026, currently lists a ceiling of 20 million cells or 100 MB for spreadsheets created in or converted to Google Sheets. These are the limits stated by that rolling page, not a measured capacity or a guarantee that an arbitrary Excel workbook will convert. The retrieved page does not specify a separate column maximum; do not infer one from the cell total. Connected Sheets has separate limits and is outside this ordinary conversion workflow.

The same reference warns that, during Excel-to-Sheets conversion, cells containing more than 50,000 characters are removed. Inspect long notes, embedded source text and concatenated fields before conversion, preserve the original, and compare the actual strings afterward. A field exactly 50,000 characters long does not exceed that stated threshold; that observation alone is not a verified import result. A 50,001-character field does exceed it.

For a planning example, three rectangular grids of 40,000 rows by 50 columns account for 3 × 40,000 × 50 = 6,000,000 cells. This is an inventory calculation, not a promise of speed or conversion acceptance. Check the complete workbook, including extra tabs and unused grid extents, rather than counting populated values alone. Do not confuse the spreadsheet-specific limit with Drive’s allowance for unrelated file types.

For slow editing below a size ceiling, use diagnose calculation performance. Reducing calculation work and satisfying a conversion limit are different acceptance checks.

Inventory behavior before moving data

List the critical sheets and output cells, then inventory their dependencies: formulas and named ranges, charts and pivots, imported data, automation, access roles and protected inputs. For each, write the required result, where it will be checked and who will check it. Treat a function that produces a plausible cached value differently from one that recalculates correctly after a changed input.

Automation needs a separate decision. Google describes recreating Excel macros using Apps Script; that is implementation work, not automatic VBA preservation by file conversion. List each macro’s inputs, output changes and external dependencies before estimating migration effort. Do not authorize scripts or install add-ons merely because an imported workbook requests them. Google’s macro migration guidance

For a subsequent authorized implementation, the existing script authorization, triggers and quotas guide helps distinguish the code from the permissions and execution conditions it needs.

Define acceptance without repeating the export exercise

Use the existing file-format compatibility exercise for a small conversion/download test. Its arithmetic checks distinguish an unchanged master from an independently edited copy. A return import into Sheets tests that route only; it does not establish that Excel itself calculated the file correctly.

Extend that exercise with an inventory of your actual requirements. A proposed project checklist might include:

1. The designated output formula recalculates after an input changes.
2. A named chart still communicates the intended categories and scale.
3. The authorized recipient can perform the required edit in the selected master.
4. An essential automation has a separately tested replacement, or migration remains blocked.
5. The returned deliverable is opened in the recipient’s actual application.

These are proposed checks, not observations. Record each as documented constraint, observed pass, observed failure or untested, with the file identity and environment beside it. Do not collapse the checklist into a single “compatible” label.

Approve or retain the original workflow

Accept the new master only after required behavior and ownership are agreed. Preserve the source and a dated export until the handoff is verified. If recipients only need a report, agree a snapshot explicitly rather than implying that exported values provide the original automation or sharing setup.

When a requirement fails, isolate whether the problem is file identity, calculation, unsupported behavior or permissions. Start with Sheets troubleshooting. If a critical dependency is still untested, retain the original workflow and document the hold instead of silently replacing it with a simpler workbook.