Migration evaluations almost always stall at the exact same roadblock. After the IT team or responsible executive progresses to the point of securing Google Workspace quotes, they upload a single performance-tracking file from accounting as a trial. Upon opening it, the pivot table has turned into an unresponsive, static table of numbers. The dropdowns used to switch aggregation dimensions have vanished as well.
At this stage, leadership concludes, "We cannot migrate our company's Excel assets," and the initiative gets shelved indefinitely. That decision was not incorrect at the time, because that was genuinely how the software behaved. Excel tables were not treated as native tables on the Google Sheets side, and pivot tables tied to those tables were flattened into static grids.
With updates rolling out gradually starting August 11, 2026, both of these behaviors have changed. If the reason your organization halted migration was "the sheer volume of rebuilding required," it is well worth reassessing.
What now migrates automatically
What has changed is the import fidelity when converting files.
- Excel tables import as Google Sheets tables. Previously, these were converted into plain cell ranges, immediately stripping away the structural and formatting advantages native tables provide.
- Pivot tables based on table ranges import as native pivot tables. They are no longer replaced with static grids.
The update started rolling out gradually on August 11, 2026, taking up to 15 days for visibility. It applies to both Rapid Release and Scheduled Release domains, and covers all Google Workspace editions as well as personal Google accounts. Purchasing additional licenses is not required.
In other words, even if a file failed conversion in the past, converting that exact same file today might produce a completely different outcome. The practical significance of this update is that the basis for previously passing on migration may now be outdated.
What still requires an audit
If you gloss over this nuance and announce internally that "everything can migrate," conflict will inevitably arise later. This update addresses importing tables and pivot tables; it does not encompass every single component of an Excel file.
You must audit and catalogue items that remain unsupported prior to migration.
| Persistent assets | Handling during migration |
|---|---|
| Pivot tables not based on table ranges | This update covers items "based on table ranges." Pivot tables constructed from raw cell ranges are handled separately. |
| Macros / VBA | Requires determining whether to rewrite functionality into Google Apps Script on the Google Sheets side |
| External data connections / add-ins | Alternative methods must be determined for each connection target. Estimating effort here is the most unpredictable. |
Practically speaking, the third item is the most difficult. Spreadsheets that pull CSVs from core systems or depend on specific business add-ins represent business process issues rather than file format issues, and cannot be solved by conversion tools. The decision framework detailed in When to transition from Excel workflows to dedicated systems applies directly to establishing this boundary.
How choosing test files changes the conclusion
When conducting trial conversions to assess migration feasibility, selecting the wrong files will lead to incorrect conclusions.
A common mistake is testing only the single most complex file in the company. The thinking goes, "If this passes, everything passes," but because the most atypical file rarely represents the overall picture, it often leads to the overly pessimistic conclusion that "migration is impossible."
Expanding your sample in the following sequence yields far greater accuracy:
- Select 3 to 5 files actually in daily or weekly use. The higher the usage frequency, the greater the post-migration impact.
- Mix files that contain pivot tables with those that do not. Since this update primarily benefits pivot tables, you cannot evaluate effectiveness without separating the two.
- After conversion, test functionality by actively changing aggregation dimensions. Just looking at the initial view upon opening will not reveal whether it is functioning as a live pivot table or a static table.
- For failed files, categorize the exact root cause of failure. Determine whether it stems from macros, external connections, or how pivot tables were built. Without this breakdown, estimating labor hours is impossible.
With the categorization in Step 4 complete, discussions can take place at a granular level: rather than "everything is impossible," you can say, "80% converts cleanly as is, while the remaining 20% requires macro rewrites." What executive decision-making requires is not a binary yes/no, but this specific breakdown.
Differences that make an impact after migration
While attention tends to focus purely on rebuilding costs, that was never the true motivation for evaluating a migration in the first place.
When running operations on Excel, the same file branches into multiple versions, requiring people to constantly manage which one is current. The practical benefit of shifting to Google Sheets is that you can offload this management to the system itself. We have compiled details on automating calculations and data copying in Automating Operations with Google Sheets.
If your data volume is growing and approaching spreadsheet limits, another option is to use Google Sheets as the frontend and place BigQuery on the backend. We cover this architecture in Connected Sheets List Parameters.
If you are debating whether to use Google Workspace alongside Microsoft 365 or standardize on one, reading the feature-by-feature breakdown in Comparing Google Workspace and Microsoft 365 and the cost reevaluation in Migration Comparison Considering M365 Price Hikes first will help you separate the pros and cons of migrating from tool selection.
What to do next
First, try converting one file that was previously written off because "it broke when converted." That alone will show you whether the assumptions behind that decision have changed.
Next, count how many files remaining out of scope (macros, external connections) exist in your company. The workload of a migration is determined not by the number of files you can move, but by the contents of the files you cannot move.
GleamHub provides support for auditing migration candidates and scoping macro replacements with Google Apps Script through our free IT and Google Workspace consultations. Since the right approach varies based on your file structure and operational dependencies, please consult with us individually. Feel free to reach out via Contact Us.
Sources
- Improved file importing in Google Sheets with tables and linked pivot tables — Google Workspace Updates
- Google Sheets Now Imports Excel Pivot Tables Without Breaking — TechJuice
- Google Sheets makes it less of a headache to import Excel files — Android Authority
- Convert Microsoft Excel files to Google Sheets — Google Docs Editors Help
