Load Excel Power Query Into an Existing Table

How-to basics · Updated November 21, 2026

In Excel for Microsoft 365 on Windows, a Power Query can load to an existing worksheet, but it generally cannot use an independently created Excel table as a reusable destination and simply add query results to it. To refresh cleanly, load the query as its own output table; if you need rows from multiple sources in that output, combine them in Power Query before loading.

What “load into an existing table” can mean

The phrase can describe two different tasks. You might want a query’s results to appear on a worksheet that already contains data, or you might want the query to place its rows inside a particular Excel table that already exists. The first is often possible if you choose a suitable empty location. The second is not the normal Power Query loading model: a query creates and manages its own output table rather than treating an arbitrary existing table as a container to append rows into.

There is one important exception in everyday wording: if the existing table is already the output table created by that query, then refreshing the query updates that table. It remains the same query output, with its rows and columns recalculated from the source. This is different from loading a new query into a manually built table that contains unrelated or hand-entered data.

Keeping these cases separate helps prevent accidental replacement of data. Before changing a destination, identify whether the table is query output, a source table, or a manually maintained table intended to collect records.

How Power Query loads and refreshes results

Power Query reads one or more sources, applies steps such as filtering, changing data types, and combining columns, then sends the resulting dataset to a destination. In a worksheet load, Excel normally creates a table for the results. The query retains its transformation steps, and refreshing reruns those steps against the current source.

Refresh is not the same as adding a permanent batch of new rows beneath the previous results. The output represents the current result of the query. If a source record disappears or no longer meets a filter, that record can disappear from the refreshed output too. If more records meet the query conditions, the output table can expand. This behavior is useful for reports and current lists, but not for preserving a growing history of snapshots by repeatedly stacking refreshes.

Excel tables and Power Query output tables are related but distinct. A table created with Insert > Table is a structured range that can have filters, formatting, and structured references. A query-loaded table has those Excel table features as well, while also being linked to a query that controls its contents. Manually typing into a query output table does not turn those entries into durable query data; a refresh can replace the output.

Load a query to an existing worksheet

If the goal is to put results on a worksheet that already has other content, choose an empty destination cell with enough room for the query output. In the Power Query Editor, use Home > Close & Load > Close & Load To. In Excel, you can also open Data > Queries & Connections, right-click the query, and choose Load To. In the Import Data dialog, select Table, select Existing worksheet, and specify the destination cell.

  1. Check the destination sheet and clear any values or objects that would occupy the output area.
  2. Open Load To for the query and choose Table and Existing worksheet.
  3. Enter or select the upper-left destination cell, then confirm the dialog.
  4. Review the loaded table and refresh the query to confirm that its output remains where expected.

This places a query output table at a chosen worksheet location; it does not merge the results into a table already occupying that location. Avoid choosing a cell inside an existing table or in a range where the query output could collide with other content. Excel may reject an overlapping destination, or the placement may interfere with data you intended to preserve. A blank area on the same worksheet is usually safer than trying to make two tables share cells.

If you have already loaded the query and only need to move its output, use Load To again and choose a new, clear destination. Depending on the query and workbook state, you may need to remove or relocate the old output first. Save a copy before making substantial layout changes to a workbook with dependent formulas, charts, or other queries.

Append data before loading when you need one combined table

When the real requirement is one table containing rows from several sources, combine those sources in the query rather than attempting to append them at the worksheet destination. In Power Query, use Home > Append Queries or Home > Append Queries as New. The first adds the append step to a query; the second creates a separate query, which is often easier to audit because the original queries remain unchanged.

For example, suppose a workbook has January and February sales tables with columns named Date, Region, and Amount. Create a query for each source, then append the two queries. The result has the records from both months in one dataset, which you can load as one output table. For a query that combines multiple monthly files from a folder, the folder-combine workflow can be more maintainable than building a separate append step every month.

Append matches fields by column name, not simply by their left-to-right position. If one source calls a field “Amount” and another calls it “Sales,” the result can contain separate columns, with nulls where a source lacks a matching field. Rename columns and align data types before appending when you expect one consistent schema. An append operation also does not automatically preserve a historical copy of each refresh; it combines the records currently available from its inputs.

If you want the records from a manually maintained table included, it can be a source: format that range as a table, then use Data > From Table/Range to create a query from it. Combine that source query with the other source query and load the combined result somewhere else. Do not load the result back over the very table that supplies the source data. A query that reads from and overwrites its own source can cause a circular or destructive workflow.

When you should keep the existing table separate

Sometimes the existing table is a hand-maintained register, while the query is meant to provide a current reference list or calculation. In that situation, keep the tables separate and connect them with a suitable process rather than forcing them into one range. For example, load the query output on a dedicated sheet and use formulas, PivotTables, or charts to present the information alongside the manually maintained data.

That separation makes ownership clear: Power Query owns the query output, while users own the manually maintained table. It also reduces the risk that refresh erases comments, corrections, or fields that do not exist in the source. If users need to add notes to query-derived records, consider storing notes in a separate table keyed by a stable identifier, then joining or looking them up for presentation. Do not rely on row position as the key, because sorting or new source records can change row order.

If a workflow must permanently add each incoming batch to an archive table, a normal query refresh is not an append-only archive mechanism. Consider a proper source system or a deliberately designed automation process that writes new records and checks for duplicates. That design needs clear rules for identifying new rows, handling corrected source records, and preventing repeated imports; simply refreshing a query does not provide those rules.

Preserve formatting, formulas, and dependent reports

Power Query output tables can be formatted with Excel table styles, and worksheets can contain formulas that refer to the table. However, treat query-loaded cells as refresh-controlled output, not as a place for permanent manual edits. Add business logic as query steps when it belongs in the transformation, or keep user-entered annotations in a separate table that can be related to the output.

Before moving or replacing a destination, inspect formulas, charts, PivotTables, and other queries that may depend on the current table name or location. Structured references to a table can be more resilient than references to fixed cell addresses, but deleting and recreating a table may still affect dependent workbook objects. A refresh normally updates the existing query output; deleting the output and loading a replacement can be a more disruptive change.

For a workbook shared with others, document which sheet is the query output, where its source data comes from, and which fields users may safely edit. If you change the query’s columns, test downstream reports because a renamed or removed field can break references even when the query itself refreshes successfully.

Common problems and practical fixes

  • The destination is occupied: Choose a blank upper-left cell and make sure the full output area will not collide with other data or a table.
  • Manual entries disappear: Do not store durable user-entered values inside a query output. Keep them in a separate input table or incorporate them as a genuine query source.
  • Refresh adds no new rows: Check that the source itself contains the new records and that query filters, data types, and source-range boundaries include them.
  • Appended columns do not line up: Standardize column names and types in each source query before appending. Similar-looking headings with different text are separate fields.
  • The output has duplicate records: Appending faithfully combines rows; it does not necessarily identify duplicates. Apply an appropriate deduplication step using the actual key fields, if duplicates should be removed.
  • A formula or report breaks after a change: Check table names, column headings, and references. Restore the original structure or update dependent objects to match the new output.

When diagnosing a refresh, first check Data > Queries & Connections to confirm which query is loaded and whether it is configured as a connection only. Then inspect the query’s source and applied steps. A query that is connection-only will not create a worksheet table until you choose a worksheet load destination; it can still serve as an input to another query.

Excel for Mac and Excel for the web

The instructions above target Excel for Microsoft 365 on Windows. Excel for Mac also supports Power Query, but available connectors and some editing or loading options can differ by Excel version and update channel. If a named command is not present, check that the Mac installation is current and use the query’s available load controls rather than assuming every Windows dialog is identical.

Excel for the web has more limited Power Query authoring and management capabilities than desktop Excel, and the exact ability to create, edit, or refresh a query depends on the feature and source involved. For a workbook where the destination or append logic needs changing, open it in the desktop Excel application and verify the result there. A workbook may display query output in a browser even when the full query-editing workflow is unavailable.

Frequently Asked Questions

Can Power Query append rows to an existing Excel table?
Not as a general refresh destination for an arbitrary table. Append the source queries in Power Query and load the combined result as a query-owned table. A query can refresh its own existing output table, but that is not the same as adding rows to a separate manually maintained table.

Can I load Power Query results onto a worksheet that already has data?
Yes, choose Existing worksheet in Load To and select a clear destination cell. Keep the complete result area free of conflicting data and tables; do not expect the query to merge its output into cells that are already part of another table.

Will refreshing a query keep rows I typed into its output table?
Do not count on it. The query regenerates its output from the source and transformation steps, so manual additions or edits in that output are not a reliable place to store information. Put those entries in a separate source table or another durable data store.

Does Append Queries permanently save earlier refresh results?
No. Append combines the rows present in its input queries when the query runs. If an earlier batch is no longer in the sources, a later refresh does not preserve it merely because it appeared in an earlier result.

How do I load a query as a table instead of a connection?
Open Load To for the query, select Table, and choose a new worksheet or a clear location on an existing worksheet. If the query is currently connection-only, changing its load setting lets Excel create a worksheet output.

Choosing the safest setup

For a current report, load the query to its own table and refresh that output. For one result assembled from multiple tables or files, append or otherwise combine the sources in Power Query before loading. For a manually curated table that must retain user edits, keep it separate from the query output and define an explicit way to relate or archive records. Choosing the destination based on who owns the data is the simplest way to avoid overwriting work or misunderstanding what refresh will do.

Related

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.