How can I export SharePoint Online search results (with file paths) to Excel without the .iqy re-query causing “Out of memory”?

Dear @Jennifer,

Thank you for posting your question in the Microsoft Q&A forum. The issue you're experiencing with the "Export to Excel" feature is a known challenge when working with large SharePoint document libraries. The core problem is that the .iqy file created by SharePoint is a live query, not a static data export. It attempts to load and process the entire library into Excel's memory before applying your search filters, which causes the "Out of memory" error. 

To provide the most accurate guidance, please help us confirm two key details: 

• Approximate total number of items in the est1 document library. 
• Search Scope: When you use the library search box, are you typically selecting "Within this library" or "This site"/"Everything"? 

This information is crucial for determining whether the following structural solution is viable. 

Step 1: Restructure your data 

If your searches are consistently scoped to "Within this library," the most effective long-term solution is to split your large document library into smaller, logical libraries. 

• The .iqy file's behavior is inherent to the feature and cannot be changed to export only filtered results. By reducing the size of the source library, you eliminate the root cause of the memory overload. Exporting from a library with 20,000 items is fundamentally more reliable than from one with over 170,000 items. 
• Action: Plan a migration to divide content by logical criteria such as year, department, or major project phase. This will improve performance for all operations (searching, syncing, loading views) and make the native "Export to Excel" feature functional again for these new, smaller libraries. 

Step 2: Official support path for log analysis 

If the library cannot be restructured and you need a definitive technical investigation into why this worked in August 2025 but fails now, the appropriate step is to open a service request through the Microsoft Unified Support portal. 

• This provides backend engineers access to the necessary service logs for your tenant. They can analyze potential changes in query execution, throttling, or indexing that may have occurred since August, which are not visible from the user interface. 
• When opening the ticket, include all details from your post and the information requested. 

Please note that as a forum moderator, I don’t have access to backend tools or internal systems to investigate further, and certain settings or configurations are managed exclusively by your organization’s administrators, so I’m unable to check or make changes on that side. That said, I truly hope these suggestions help you move forward.  

To proceed, please provide the requested details about your library's size and search scope. This will allow us to refine our recommendation and help you choose the most effective path forward. 

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".   

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Exporting search results from SharePoint Online to Excel can be challenging, especially with the issues you've described regarding the .iqy file causing memory errors. Unfortunately, the default behavior of the Export to Excel feature in SharePoint Online is to create an .iqy file that re-queries the entire library, which can lead to performance issues, especially in large libraries.

Here are some suggestions and alternatives you might consider:

1. Use Power Automate: While you mentioned difficulties with permissions, if you can work with someone who has the necessary access, consider setting up a Power Automate flow that retrieves the search results and exports them to an Excel file. This can bypass the .iqy limitations.
2. Custom Search Results Page: If you have access to a developer or IT resources, creating a custom search results page using SharePoint Framework (SPFx) could allow for more control over the data displayed and how it is exported. This could include a button that exports the visible results to a static Excel or CSV file.
3. Browser Developer Tools: As you noted, using the browser's developer tools to capture the JSON response from the search query could be a viable workaround. If you can get the JSON data, you could potentially transform it into a CSV format using a script or a tool that you have access to.
4. Manual Copy-Paste: Although you mentioned issues with formatting, if the results are manageable, consider copying the search results directly from the browser and pasting them into Excel. This may require some manual formatting but could be a quick solution for smaller result sets.
5. Check for Updates: Ensure that your SharePoint Online and Excel applications are up-to-date, as Microsoft frequently releases updates that may address performance issues or improve functionality.
6. Contact Microsoft Support: Given the complexity of your situation, reaching out to Microsoft Support might provide additional insights or solutions tailored to your specific environment and permissions.

Ultimately, the ability to export search results in a user-friendly manner may depend on the specific configurations and permissions set within your organization. If the .iqy behavior is by design, Microsoft may not have a direct alternative, but exploring custom solutions or leveraging existing tools within your organization could yield better results.

References:

• SharePoint Online doesn't return search results
• Troubleshoot "View in File Explorer" issues in SharePoint Online