Power Query in Google Sheets: What You Can Do Instead

No—Google Sheets does not include Microsoft Excel’s Power Query editor, and it cannot run Power Query’s M language natively. You can still import, clean, combine, and summarize data in Sheets using tools such as QUERY, import functions, connected data sources, and Apps Script; the best substitute depends on where your data comes from and how often it changes.

What Power Query Does—and Why the Difference Matters

Power Query is Microsoft’s data-import and transformation tool, available in Excel and other Microsoft products. In Excel for Microsoft 365 on Windows, you can use the Power Query experience through Data > Get Data. It helps you connect to sources such as files and databases, apply repeatable transformation steps, and load the resulting data into a worksheet or data model. Its transformation language is called M.

Google Sheets has no built-in Power Query editor, no native way to execute M queries, and no direct equivalent to Power Query’s recorded transformation steps. A workbook containing queries does not become a refreshable Power Query project just because it is opened or imported in Sheets. Excel-specific queries and connections generally need to be managed in Excel; do not assume that Google Sheets will preserve their behavior or refresh them.

That distinction is important if you are following an Excel tutorial or collaborating with someone who uses both products. Sheets can perform many of the same everyday jobs, but usually through a different combination of formulas, menus, connectors, or code. The practical question is therefore not whether Sheets has Power Query under another name, but which Sheets workflow can handle your particular data process.

Google Sheets Tools for Importing and Cleaning Data

For a one-time file import, use File > Import and choose the file and import options that suit your spreadsheet. Sheets can also open many Excel files, but opening an Excel workbook in Sheets is not the same as running Excel’s Power Query engine. For web-based sources, several built-in functions can pull in data: IMPORTDATA for CSV or TSV files, IMPORTHTML for tables or lists on a web page, IMPORTXML for selected XML or HTML content, IMPORTFEED for feeds, and IMPORTRANGE for a range in another Google Sheets file.

Once data is in the sheet, built-in cleanup options can handle common tasks. Data > Data cleanup includes tools such as Remove duplicates and Trim whitespace. Data > Split text to columns can separate delimited text, while filters and sorting help inspect or arrange records. Pivot tables are useful for grouping and aggregating a table without writing a formula. These features are helpful, but they do not provide a single Power Query-style editor where a sequence of transformations is saved as a reusable query.

For transformations expressed as formulas, QUERY is especially useful. It accepts a range and a query string using a Google Visualization API query language. That language resembles a limited form of SQL, but it is not M and is not full SQL. QUERY can select columns, filter rows, sort, group, and aggregate data; it does not reproduce every operation or connector available in Power Query.

Example: Summarize Imported Sales Data with QUERY

Suppose a sheet has headers in row 1 and sales records in A1:D1000: column A contains the date, B the region, C the product, and D numeric revenue. To total revenue by region, enter this in an empty cell:

=QUERY(A1:D1000, "select B, sum(D) where B is not null group by B label sum(D) 'Total revenue'", 1)

The final argument, 1, tells QUERY that the first row contains a header. The query selects the region and the sum of revenue, ignores rows without a region, groups matching regions, and labels the calculated column. If the data rows contain East revenues of 120 and 80 and a West revenue of 150, the result is East 200 and West 150. Keep the revenue column numeric; values stored as text may not aggregate as expected.

This approach is convenient when the source table is already in Sheets and the summary should update as source records change. It is less suited to complicated pipelines involving multiple file formats, complex type conversion, or many dependent transformation steps. In those cases, a formula may become difficult to read and maintain, and a script or external transformation process may be clearer.

Choose a Workflow Based on the Source and Refresh Needs

Before choosing a substitute, identify the source, the transformation, and the refresh expectation. A one-off CSV cleanup has different needs from a daily database feed. Consider these common situations:

One-time file or export: Import the CSV or Excel file with File > Import, then use cleanup tools, formulas, or a pivot table. This is straightforward when a person can repeat the import as needed.
Data already in another Google Sheet: IMPORTRANGE can bring in a source range, and QUERY or other formulas can shape it. The first connection requires authorization, and the source spreadsheet must remain accessible.
Public web data: Try an appropriate IMPORT function if the page or file exposes data in a supported format. Web page structure and access rules can change, so a formula-based import may need maintenance.
Large or business-critical data source: Check whether an approved connector or a database workflow is available. A connector may require a particular Google Workspace edition, permissions, or administrator setup.
Repeatable, complex transformation: Consider Apps Script, a purpose-built connector, or transforming the data in Excel or another data platform before sending a clean result to Sheets.

For example, an analyst who receives a weekly sales CSV may import it and apply a saved set of formulas or a pivot table. If the file is generated consistently and the process must run unattended, a script or managed data pipeline may be more reliable than manually replacing the source data. The right choice depends on the cost of a missed refresh and the amount of maintenance the team can support.

Connected Sheets, BigQuery, and Automated Data

For organizations using BigQuery, Google Sheets offers Connected Sheets, which can let users analyze BigQuery data from a spreadsheet without first copying an ordinary static table into it. It is a connection to a supported data platform, not a general-purpose replacement for Power Query. Availability and capabilities can depend on account type, Google Workspace settings, access permissions, and the specific source, so check the organization’s configuration and Google’s current product documentation.

Apps Script is another option when a workflow needs custom logic. It uses JavaScript and can read and write spreadsheet ranges, call permitted services, and automate tasks. A script can, for instance, take records from a configured source, standardize selected fields, and write a clean table to a sheet. But a script is not automatically a Power Query conversion: someone must design, authorize, document, and maintain it. External-service permissions, quotas, and changes to the source can also affect whether it continues to work.

Built-in import formulas are easier to start with, but they are not a promise of precise, instant refresh. Their results depend on the source being reachable, compatible, and permitted to serve the content. For important reporting, document the source and update process, check that the latest data arrived, and avoid treating a spreadsheet display as proof that a source system is current.

Moving a Power Query Workflow Between Excel and Sheets

If a process already runs in Excel Power Query, the least disruptive approach is often to keep the query in Excel and export its finished output for Sheets to consume. For example, refresh the query in Excel, load its result to a worksheet, save or export the result in a format Sheets can import, and then use that clean output for collaboration or presentation. This preserves the transformation in the tool that supports it, though it adds a handoff and may require a person or automation to refresh and publish the result.

For a migration, list each query’s inputs, steps, outputs, and refresh schedule before rebuilding anything. Simple steps such as filtering rows, renaming columns, or grouping totals may translate to Sheets formulas or menu actions. More involved operations—such as combining many files, handling inconsistent schemas, or applying a long chain of type and text transformations—may be cumbersome to reproduce in a spreadsheet. Validate a sample of the rebuilt output against the Excel result, including row counts, missing values, dates, and totals.

There is also a collaboration consideration: people who need to edit the transformation should know which application owns it. If the underlying query is in Excel, changing a displayed result in Sheets will not change the M steps. If Sheets is the system of record, document the formulas, script, or connector that creates the output so colleagues can troubleshoot and update the process safely.

Common Limitations and Misconceptions

A frequent misconception is that Sheets’ QUERY function is simply Power Query under a different label. They solve overlapping but different problems. QUERY is a spreadsheet formula for querying a supplied range; Power Query is a broader data acquisition and transformation environment with its own connectors, editor, step history, and M language. A QUERY formula does not automatically connect to every data source that Power Query supports.

Another common assumption is that an Excel file containing Power Query connections will refresh those connections in Sheets. It should not be relied on to do so. If someone needs the result in Sheets, provide a refreshed output or rebuild the process using a supported Sheets method. Also check how imported values are represented: dates, decimal separators, blank cells, and numbers stored as text can produce differences in calculations.

Finally, external data imports have access and reliability implications. Do not paste credentials or confidential data into a public URL or an unreviewed add-on. Use only connectors approved for the data, grant the minimum necessary access, and verify the sharing settings of both the spreadsheet and its source. A convenient import mechanism is not a substitute for an organization’s security and privacy requirements.

Frequently Asked Questions

Can I install Power Query as an add-on in Google Sheets?
No native Google Sheets add-on turns Sheets into Excel Power Query or runs M queries within it. Third-party products may offer data import or transformation services, but their features, permissions, and pricing vary; review them before connecting sensitive information.

Does Google Sheets have a function like Power Query?
There is no single equivalent. QUERY can filter, group, sort, and aggregate a range, while import functions, cleanup tools, pivot tables, connectors, and Apps Script cover other parts of a data workflow.

Can Google Sheets refresh Power Query data from an Excel file?
Do not expect Sheets to refresh the Excel query. Refresh it in an application that supports that Power Query workflow, then transfer the resulting data, or rebuild the transformation using tools supported by Sheets.

Is QUERY the same as SQL or Power Query?
No. Google Sheets QUERY uses a SQL-like query language for a range of spreadsheet data. It is distinct from SQL and from Power Query’s M language, and its available operations and sources differ.

What is the closest option for automated data in Sheets?
It depends on the source. A built-in import function may suit a compatible web source, Connected Sheets may suit an authorized BigQuery workflow, and Apps Script or a managed connector may suit custom automation. Test refresh behavior and access requirements before relying on it for reporting.

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.