Yes—Excel Tables Now Arrive as Native Sheets Tables

Yes. Google Sheets now imports Excel tables as native Sheets tables. It can also preserve the source relationship for an imported Excel pivot table when that pivot is backed by a table range. This improves structural fidelity, but it does not guarantee identical behavior for every formula, table feature, chart, format, macro, pivot configuration, or external connection. Choose the appropriate workflow, keep the original XLSX, and validate the converted data before sharing or publishing it.

The short answer: yes, with defined limits

Google announced native Excel table import on August 11, 2026. Table import was available immediately. Import support for Excel pivot tables backed by table ranges began rolling out that day and could take up to 15 days. Previously, those table-backed pivots were replaced with static grids; the update allows the imported pivot to retain its relationship to the source table. The change applies to Google Workspace customers and personal Google accounts, according to the Google Workspace update on tables and linked pivot tables.

The pivot support has a defined scope: Excel pivot tables backed by table ranges. Do not generalize it to every pivot source, calculated field, slicer, filter, data model, or external connection.

Likewise, “native table” describes the imported structure. It does not establish universal compatibility for structured-reference formulas such as Table1[Column], table styles, calculated columns, total rows, automatic expansion, charts, or automation. Test those elements against the Excel original.

Choose the right Excel-to-Sheets workflow

Opening, importing, and converting an Excel workbook produce different results:

Workflow	Best when	Result
Edit the XLSX in Sheets	The file must remain in Excel format	Changes are saved to the Excel-format file
File > Import	You want Excel data in a new or existing Google Sheet	Creates or updates a Sheets file without changing the XLSX
Save as Google Sheets	You want a separate native Sheets version	Creates a Google Sheets copy and retains the Excel original

Edit the XLSX in place when colleagues or downstream systems still require an Excel file. Google labels its documented in-place editing workflow as Chrome-only.

Use File > Import to bring the workbook into a new spreadsheet or insert it into an existing one. Use File > Save as Google Sheets after opening the Excel file when you want a separate native copy for ongoing collaboration. Importing or saving a Sheets copy does not alter the original workbook.

Google recommends considering conversion for collaboration when a dataset contains 10 million cells or fewer, while suggesting continued Excel use for larger datasets and certain Excel-specific features. The figure is conversion guidance, not a universal import limit. These distinctions are documented in Google’s official Excel and Sheets guidance.

How to import an Excel table into Google Sheets

Google documents the following procedure:

1. Open a new or existing Google Sheet.
2. Select File > Import.
3. Choose the Excel file and click Select.
4. Select an import option.
5. Click Import data.
6. If prompted, click Open now.

The documented Excel workflow provides three destination options:

• Create new spreadsheet: Creates a separate spreadsheet containing the imported workbook data.
• Insert new sheet(s): Adds the imported content as new tabs in the spreadsheet you have open.
• Replace spreadsheet: Replaces the contents of the current spreadsheet with the imported workbook.

Choose Insert new sheet(s) when adding Excel content to an existing Google Sheet without replacing its current tabs. Use Replace spreadsheet only when replacing the entire destination file is intentional.

Google’s documented Excel workflow does not offer Replace current sheet, Append to current sheet, or Replace data at selected cell. Instructions listing those choices may refer to a different import context or an older interface.

If the workbook supports an important reporting, operational, or publishing process, conduct the import on a separate working copy. The untouched XLSX will serve as the reference during validation.

What is preserved—and what still needs checking

Native-table import confirms more structural support, but workbook details still determine whether the converted file behaves as expected.

Status	Workbook elements	Recommended action
Confirmed	Native Excel table structure; pivot relationship when backed by a table range	Confirm that the objects exist and use the intended source
Requires validation	Formulas, dates, numeric types, formatting, charts, pivot filters, calculated results	Reconcile with known Excel results
Does not transfer directly	Excel VBA automation	Rewrite or retain the process in Excel
Undocumented	Structured references, total rows, calculated columns, automatic expansion, other table-specific behavior	Test after import without assuming success or failure

A table can appear intact while returning different results. Numbers stored as text may aggregate differently from numeric values, while differences in date parsing can affect grouping, comparisons, and formulas.

Google Sheets does not run Excel VBA. A third-party migration guide advises rewriting VBA automation in Apps Script or retaining that process in Excel. It also warns that Power Query workflows and external integrations may require redesign, an external data pipeline, or a hybrid workflow in which Excel performs preprocessing and Sheets receives the cleaned output. Treat these as migration risks to investigate rather than proof that every such workflow will fail.

Chart compatibility is also improving feature by feature. For example, Google added support for importing 3D bar charts without displaying them as 2D charts. That specific 3D bar-chart import improvement does not show that every chart type, series, label, axis, or formatting choice will transfer unchanged.

Validate the imported table before sharing it

Use the untouched XLSX as the comparison and rollback file. Then reconcile the imported version systematically:

• Confirm the header row and column names.
• Check the table’s first and last rows and columns.
• Compare row counts, including blank or filtered records.
• Test dates, timestamps, percentages, currencies, identifiers, and leading zeros.
• Find numbers stored as text and text values parsed as numbers.
• Compare blank cells, empty strings, errors, and null-like labels.
• Inspect formulas and references, not just displayed values.
• Recalculate known totals, subtotals, and representative records.
• Test table and pivot filters.
• Inspect number formats, conditional formatting, and named ranges.
• Compare chart series, labels, and axes where used.
• Review external references and integrations.

For a table-backed pivot, confirm that its source is the imported table or intended range. Apply a known filter and compare at least one subtotal with the Excel version. Also inspect formulas feeding the pivot or displayed table: a plausible number may be stale or based on a broken reference.

Visual similarity is useful, but it is not reconciliation. A converted workbook is ready to share only after its structure, values, calculations, and relevant presentation elements have been checked against known results.

Prepare a safe copy for public publication

Treat conversion as a staging step rather than the publication event:

1. Retain the original XLSX unchanged.
2. Import or convert a separate working copy.
3. Reconcile the table and any table-backed pivot.
4. Extract only the table intended for publication.
5. Remove sensitive, personal, confidential, and operational material.
6. Publish only the cleaned and verified output.

For a concrete test, create a synthetic workbook with a six-row table named SalesData. Give it four columns: Month, Region, Product, and Units.

Use these fictional records:

Month	Region	Product	Units
January	North	Alpha	1,200
January	South	Alpha	900
February	North	Alpha	1,100
February	South	Alpha	1,000
March	North	Alpha	1,300
March	South	Alpha	950

The known total is 6,450 units. A pivot grouped by Region should show 3,600 for North and 2,850 for South.

Import the workbook and confirm that:

• SalesData contains six data rows.
• The four headers remain intact.
• The total is still 6,450.
• The pivot points to the imported table or intended range.
• North and South retain their known subtotals.
• Filtering the pivot to North returns 3,600.
• No working tabs or operational formulas remain in the publication copy.

This synthetic example provides specific expected results without exposing private data. A real publication workflow should follow the same pattern using a small public dataset or a sanitized extract.

TablePage describes its service as turning a spreadsheet into a public, interactive data page. Because the resulting dataset is public, it is appropriate for finished, nonsensitive information that readers can explore—not for an operational workbook containing private source tabs, credentials, internal calculations, or personal information.

Frequently asked questions

Can I import an Excel table into an existing Google Sheet without replacing it?

Yes. Open the destination Google Sheet, choose File > Import, select the Excel file, and choose Insert new sheet(s). The imported content will be added as new tabs without replacing the spreadsheet’s existing sheets.

Does Google Sheets change the original Excel file when I import or convert it?

No. Importing Excel data into a Sheets file does not change the original workbook. Choosing Save as Google Sheets creates a separate native Sheets copy while retaining the Excel file. Editing the XLSX in place is different because those changes are saved in Excel format.

Will Excel macros and Power Query work after import?

Not directly in their original Excel form. Google Sheets does not run Excel VBA, so VBA automation must be rewritten in Apps Script or retained in Excel. Power Query processes and connected workflows may need redesign, an external pipeline, or a hybrid setup. For public-data publishing, one practical approach is to keep preprocessing in Excel and send only a cleaned, validated table to Sheets.