File Content Is Not Indexed After Migration: Root Cause and Fix

After migrating files to SharePoint, you may find that search results return only file names but not the text inside documents. This problem occurs because SharePoint needs to crawl and index the content of each file before it becomes searchable. Migration tools copy files but do not trigger a full index update. This article explains why content indexing fails after migration and provides the steps to fix it.

Why SharePoint Stops Indexing File Content After Migration

When you migrate files using a third-party tool or the SharePoint Migration Tool, the file metadata and structure are preserved, but the search index is not automatically updated. SharePoint uses a scheduled crawl to scan file content and add it to the index. If the crawl is configured to run incrementally, it may skip new or modified files until a full crawl is triggered.

Another common cause is that the site or library was set to “Do not index” during migration. This setting prevents the search crawler from reading the file content. Additionally, file types that are not supported by SharePoint search, such as certain compressed or encrypted formats, will not have their content indexed.

How the SharePoint Search Crawl Process Works

SharePoint uses a content processing component that extracts text from files during a crawl. The crawl can be full or incremental. A full crawl reads every file and updates the index completely. An incremental crawl reads only files that have changed since the last crawl. After a migration, many files are marked as new or changed, but the incremental crawl may not process them if the metadata change date is not set correctly.

Common Misconfigurations That Block Indexing

The site collection may have search visibility set to “Do not index items from this site.” This setting is found in Site Settings under Search and offline availability. Libraries can also have a similar setting that prevents their content from being crawled. Another issue is that the file extension is not mapped to a filter pack, so the crawler cannot parse the content.

Steps to Force File Content Indexing After Migration

1. Check site search visibility
   Go to the site collection. Click the gear icon and select Site settings. Under Search, click Search and offline availability. Ensure that Allow indexing of this site is selected. If it is set to Do not index items from this site, change it and click OK.
2. Check library search visibility
   Navigate to the document library where the files were migrated. Click the gear icon and select Library settings. Under General settings, click Advanced settings. Scroll to Search and verify that Allow items from this document library to appear in search results is set to Yes. Click OK to save.
3. Request a full re-index of the site
   In the site collection, go to Site settings > Search and offline availability. Under Re-index site, click Re-index. A confirmation message will appear. Click OK. This forces SharePoint to schedule a full crawl for this site.
4. Request a full re-index of the library
   If only one library is affected, open the library. Click the gear icon and select Library settings. Under General settings, click Advanced settings. Scroll to Re-index document library and click Re-index library. Click OK.
5. Verify the managed property mapping
   In the SharePoint admin center, expand Search and click Manage Search Schema. In the Crawled properties section, search for Office or Document. Find the crawled property named Office:12 or similar. Click it and check that it is mapped to the managed property Title or Body. If not, add the mapping and click OK.
6. Check the crawl log for errors
   In the SharePoint admin center, go to Search > Search Administration. Click Crawl log. Look for entries related to your site or library. If errors appear, note the error code and search for solutions. Common errors include Access Denied or File type not supported.
7. Run a full crawl from the Search Service Application
   If you have access to Central Administration, go to Application Management > Manage service applications. Click the Search Service Application. In the left navigation, click Content Sources. Select the content source that includes your site and click Start Full Crawl. This may take several hours depending on the amount of content.

If SharePoint Still Does Not Index File Content After the Fix

SharePoint search returns only file names, not file content

This usually means the crawl ran but did not extract text. Check that the file type is supported. Supported formats include .docx, .pptx, .xlsx, .pdf, and .txt. If the file is a .zip or .rar, its content will not be indexed. Convert unsupported files to a supported format and re-upload them.

Search results show no content after a full crawl completes

The managed property mapping may be missing. In the Search Schema, ensure the crawled property Office:12 (which stores file content) is mapped to the managed property Body. If the mapping exists, check that the managed property is set to Searchable and Queryable.

Re-index option is grayed out or not available

This occurs when the user does not have site collection administrator permissions. Ask your SharePoint admin to grant you the necessary permissions or perform the re-index step for you. The admin can also use PowerShell to force a re-index with the Request-SPOReindex command.

Search Behavior: Before and After Re-index

Item	Before Re-index	After Re-index
Search results show file names	Yes	Yes
Search results show file content	No	Yes
Time to complete	Immediate	Hours to days
User impact	Cannot find documents by text	Full text search works

You can now force a full re-index of the migrated site or library to restore file content in search results. Start by checking the site and library search visibility settings. If the problem persists, verify the managed property mapping in the Search Schema. Consider running a full crawl from the Search Service Application to ensure all files are processed.