SharePoint Search Not Working

You finish the move, open the new site and type a file name you know is there. Search returns nothing. Users start sending messages, and the first guess is that the migration lost files.

I see this after almost every SharePoint move. Files are almost always fine. This guide explains why SharePoint search is not working after a migration, how to find the real cause and how to fix it with steps from Microsoft.

Why is SharePoint Search Not Working After a Migration?

Search does not read your files live. It reads an index, and the index is built by a crawler. Microsoft's page on making sure content can be found says SharePoint crawls content on a defined schedule and the crawler collects content that changed since the last crawl. A freshly migrated site is all new content, so it waits in line.

Three other causes show up often. A search setting may exclude the site or a library. A person may lack access, because Microsoft says users only see search results for content they can open. And a subsite that does not inherit permissions can leave its pages out of results.

Microsoft's troubleshooting page for missing search results in SharePoint Online says missing results come from crawl latency or SharePoint Online settings, even when the site was crawled and the user has permission. It gives no fixed crawl time, so I never promise one to a client.

Which Cause Fits Your Symptom?

Match what you see to the likely cause before you change anything.

How do You Fix SharePoint Search Not Working After Migration?

Work through these steps in order. They go from the cheapest check to the heaviest one.

1. Test with a known item. Search for one exact file name that you know is in the new site. Repeat the search later, because the crawler works on a schedule.
2. Check the site setting. Open the site, select Settings, then Site settings. Under Search, select Search and offline availability. Set Allow this site to appear in Search results to Yes.
3. Check the library setting. Open the library, select Settings, then Library Settings and Advanced settings. Set Allow items from this document library to appear in search results to Yes.
4. Check permissions. Ask a user who sees nothing to open the file directly. If they cannot open it, search will hide it too. Compare their access with a user who sees results.
5. Check subsites. If site pages are missing, open the search visibility page at your site address followed by /_layouts/srchvis.aspx. Select Always index all Web Parts on this site, or set the subsite to inherit permissions from its parent.
6. Request a reindex. Use the steps in the next section when the settings are right and results still do not appear.
7. Test again as a normal user. Use an account that is not a site owner, so you see what people see.

How do You Request a Reindex for a SharePoint Site, Library or List?

Microsoft documents this on its page about manually requesting crawling and reindexing of a site, a library or a list. For an entire site, follow this order.

1. Open Site settings. Select Settings, then Site settings. If you do not see it, select Site information and then View all site settings.
2. Open the search page. Under Search, select Search and offline availability.
3. Start the request. In the Reindex site section, select Reindex site.
4. Confirm. Select the check box that confirms the statement, then select Reindex site again.

For one library or list, open Settings, then Library Settings or List Settings, then Advanced settings. Scroll to Reindex Document Library or Reindex List, select the button and confirm.

Microsoft says this marks all content in the site, library or list as changed. The content is then crawled and reindexed during the next scheduled crawl. The page gives no completion time.

When should You Avoid Reindexing?

Microsoft warns that reindexing a site can place a massive load on the search system, and says to reindex only when your changes require all items to be reindexed. So do not start a reindex on every site after a move. Wait for the crawl, check the settings and reindex the few places that still fail.

Microsoft also says a change to managed properties, or to the mapping between crawled and managed properties, does not trigger a reindex on its own. If you change the search schema, the site must be reindexed before the change shows in results.

Which Migration Choices Cause Search Problems Later?

Some search problems start in the migration plan, not in SharePoint. Permissions come first. If users and groups are not mapped, people lose access and search hides the items from them. I explain the order of work in how to migrate SharePoint permissions to another tenant, and level names in SharePoint permission levels explained.

Columns come second. Search refiners and views use columns, so a list that arrives without them looks empty or wrong. See how to migrate SharePoint list columns for what carries over and what does not.

Timing comes third. A delta pass on cutover day adds new items that also wait for a crawl, so tell users to expect a short delay. I cover planning windows in how long SharePoint migration takes.

RecoveryTools SharePoint Migrator carries permission levels, SharePoint groups and user mappings, keeps content types, site columns and term store values attached to items when managed metadata migration is enabled and writes a report with a status for every item. It cannot change Microsoft's crawl schedule, so a short wait after the move still applies.

What are the Best Practices for Search After a SharePoint Migration?

• Tell users to expect a delay. A short note on cutover day prevents most support tickets.
• Test with known items. Keep a list of five or six files and search for them after the crawl.
• Check search settings on key sites. Confirm the site and library options before the launch.
• Test as a normal user. Site owners see more than everyone else.
• Reindex only where needed. A few targeted requests beat one request for every site.

Which Mistakes Make SharePoint Search Worse After a Move?

Four show up again and again. First, reindexing every site on day one. Second, testing search as an admin and missing permission gaps. Third, forgetting that drafts are not crawled. Fourth, blaming the migration for a delay that the crawl schedule explains.

My Verdict on SharePoint Search After Migration

Most search complaints after a move come from the crawl wait, a search setting or a permission gap. Check them in that order, then reindex the small set of places that still fail.

Give users a clear note on cutover day and keep a list of test files. That habit removes most of the panic I see.

Frequently Asked Questions

Published 16 October 2026. Reindex steps and search settings come from Microsoft's pages on requesting crawling and reindexing, missing search results in SharePoint Online and making content easy to find. Product behavior comes from the RecoveryTools SharePoint Migrator page. Microsoft gives no fixed crawl time, so test with a known item.