How to Export Complete SharePoint List Data When Excel Misses Rows

SharePoint Export to Excel uses an .iqy live connection that can return stale or incomplete columns, while CSV creates a full static snapshot.

What the export failure looks like

Excel export completes with missing data

The SharePoint list does export, but not every expected row or column appears in Excel. The result does not match the active list view.

Repeated memory warnings appear

Excel shows “There isn't enough memory to complete this action” many times during the export. Dismissing the alert may let the process continue, but the final data is still incomplete.

CSV export works normally

The same list exports to CSV without the memory error. That output appears complete, which strongly suggests the issue is specific to the Excel export mechanism.

Why this matters before you troubleshoot

• If CSV is complete but Excel is not, the SharePoint list itself is likely intact.
• The failure points to the Excel export path, not a universal list corruption problem.
• This also explains why one list may fail while another list on the same site still exports correctly.

How Excel export differs from CSV

The two export options do not use the same mechanism, so they can behave very differently with the same SharePoint list.

The Excel route depends on a live pull from SharePoint through the query file, so stale or incorrect column retrieval can happen if that connection misbehaves.

Static snapshot behavior

CSV writes the data as it exists at export time, which avoids the same refresh and memory path used by the Excel query file.

If Excel returns columns from an older or deleted query view, the problem is likely in the query connection rather than the current SharePoint view settings.

Checks to run before escalating

These are the exact source-backed checks to confirm whether the Excel export path is the failing component.

Close Excel workbooks and other running apps

Before exporting, close open Excel files and other applications to reduce memory pressure. Then run SharePoint Export to Excel again and note whether the memory warning still appears.

Expected result: if memory pressure was the trigger, the repeated “There isn't enough memory to complete this action” message should stop or appear less often.

Export a smaller list or a simplified view

Reduce the number of selected columns temporarily, or test with a smaller SharePoint list. This checks whether list size or view complexity is contributing to the Excel export failure.

Expected result: a simpler export should complete with the correct column set if the original view was too heavy for the query-based Excel path.

Create a new view and compare the exported columns

Build a fresh SharePoint view with only the columns you need, then export that view to Excel. Compare the exported columns with the columns selected in the active view.

Expected result: the Excel output should match the active view. If it still returns columns from a previous query, the issue is not just the current view configuration.

Verify with CSV as the control test

Export the same SharePoint list to CSV immediately after the Excel test. Use the CSV output as the baseline to confirm whether all expected rows and columns are present.

Final verification: if CSV is complete and Excel is not, the evidence supports an Excel query connection problem rather than missing SharePoint list data.

What the additional testing confirms

The follow-up checks narrow the problem to the Excel query path rather than a simple local memory shortage.

Closing programs did not resolve the export

The same result occurred even with nothing else open and even with a smaller list. That weakens the idea that ordinary desktop memory usage is the only cause.

The exported columns can come from the wrong query

A view with many columns exported the three-column set from a different query, even after that second query had been deleted. This is a strong sign of stale or incorrect query behavior.

Another list on the same site exports correctly

Because a different SharePoint list exported to Excel without warnings and with all selected columns, the problem is not a blanket site-wide export outage.

Most likely cause of the mismatch

the documented behavior points to a backend connection issue between the .iqy file and the SharePoint server.

What is supported by the evidence

• Excel export uses a live query file rather than a simple static dump.
• The query can return incomplete or wrong columns when the connection behaves unexpectedly.
• Repeated memory alerts can appear even when CSV export remains complete.

What is not established here

• No source-backed SharePoint setting is identified that directly repairs the .iqy backend connection.
• No exact Excel command is provided in the source to clear the stale query behavior permanently.
• The issue may be list-specific, because another list on the same site exported correctly.

CSV is the reliable short-term answer when SharePoint Excel export returns incomplete data

The evidence here points to the .iqy Excel connection, not missing SharePoint list content. If simplified views and low-memory tests still fail, use CSV for complete exports and have the Microsoft 365 admin escalate the backend query issue.

Use WPS Office as a Free Microsoft Office Alternative

Use Word, Excel, and PPT for FREE

Free Download

Use the stable workaround for immediate results, then escalate through the correct Microsoft path if Excel export is still required.

Use Export to CSV when you need a complete SharePoint list export without the repeated memory warning. This is the source-backed option that consistently returns the full data snapshot.

If your organization must use Excel export, the Microsoft 365 admin should sign in to the Microsoft 365 admin center and go to Support > Help and support, then submit the issue for investigation.

A practical note about local file work

This SharePoint export problem is a Microsoft-side cloud and query-connection issue, so WPS Office cannot repair tenant settings, Microsoft 365 admin controls, or the backend behavior of SharePoint Export to Excel.

Where WPS Office does help is after you already have a local CSV, XLSX, DOCX, PPTX, or PDF file. It is a free, lightweight suite with a familiar interface, PDF tools, and WPS AI features that can help summarize exported sheets, clean up columns, draft follow-up notes, or convert the finished file. Compatibility is strong for common Office formats, but advanced Microsoft-specific cloud connections and some complex workbook behaviors may differ.

Export Complete SharePoint List Data When Excel Misses Rows FAQs

Why does SharePoint Export to Excel fail while Export to CSV works?

Export to Excel uses an .iqy live query connection to SharePoint, while CSV creates a static snapshot. If the query connection misbehaves, Excel can show memory warnings or return incomplete columns even though CSV remains complete.

What does it mean if Excel exports columns from an older or deleted view?

That symptom points to stale or incorrect query behavior in the Excel export path. It suggests the active SharePoint view is not the only factor, because the query connection may still be pulling an outdated column set.

When should the Microsoft 365 admin open a support request?

Open a request when CSV is complete, Excel still shows repeated memory alerts, and tests with smaller lists or simplified views do not correct the export. The admin path in the source is Microsoft 365 admin center > Support > Help and support.

What does it mean if Excel exports the columns from an old SharePoint view?

It suggests the Excel export is pulling the wrong query state or cached connection behavior. If the active view and exported columns do not match, the .iqy connection is not reliably reflecting the current SharePoint view.