SharePoint Slow After Migration

You moved the sites on schedule. Then the calls start. Pages take ten seconds to open, search finds nothing and the team thinks the move broke something.

I hear this after almost every SharePoint project. This guide explains why SharePoint Online is slow after migration, how to tell a throttled copy from a slow site and how to fix both, using facts from Microsoft's own pages.

Why is SharePoint Online so Slow After Migration?

There are two kinds of slow. The first is a slow migration. The copy crawls, jobs retry and the plan slips. The second is a slow site. The data arrived, but pages, lists or search feel heavy.

Microsoft's page on SharePoint and OneDrive migration speed says throttling protects the reliability and availability of the service. It can start when you migrate all your content in a single task or try to migrate during peak hours.

In my experience, the second kind is more common right after cutover. Old sites carried years of tuning. A new site starts with a fresh search index, rebuilt views and pages that nobody has trimmed yet.

Which Cause Fits What You See?

Match your symptom to a cause before you change a setting.

How do You Fix SharePoint Online Slow After Migration?

Work through these steps in order. They go from the quickest check to the deepest one.

1. Name the kind of slow. If the copy is slow, go to the throttling section below. If the new site is slow, keep going.
2. Test one slow page. Install the Page Diagnostics for SharePoint extension for Edge or Chrome and test the page. Microsoft says it checks modern portal pages against set rules and flags results outside baseline values.
3. Compare with a clean site. Open a fresh out-of-the-box site and compare. In the browser developer tools, check the SPRequestDuration response header. Microsoft says a much higher value on the page points to complex elements.
4. Trim the page. Microsoft recommends 20 or fewer web parts per page, 4 or fewer dynamic web parts and images of 300 KB or smaller.
5. Check navigation and groups. Microsoft recommends fewer than 100 items in site navigation and no more than 20 security groups per site.
6. Check lists and search. Index the columns you filter on, and give the search index time to catch up before you judge results.

Microsoft's page on modern portal limits lists these numbers as recommended maximums, not hard limits. Microsoft's page on diagnosing performance issues with SharePoint also suggests removing customizations and adding them back one at a time.

What Slows a SharePoint Migration Itself?

Microsoft says it applies tighter throttling limits to background apps, including migration, DLP and backup tools, during weekday daytime hours. In the evening and on weekends, the service can handle a higher volume from those apps.

Microsoft's page on avoiding throttling in SharePoint Online explains the signals. A 429 means too many requests and a 503 means Server Too Busy. Both come with a Retry-After header, and Microsoft says ignoring it can cause more throttling. The same page warns that using the OneDrive sync client while migration apps are active can raise request volume enough to trigger throttling.

Microsoft also says throttling rules cannot be disabled or suspended, and opening a support ticket does not lift them. So the answer is timing and method: migrate off-peak, use app-based sign-in, send packages of at least 250 files and keep the job queue under 5,000 requests.

For planning, read how long a SharePoint migration takes and SharePoint migration cost.

What should You Check on the New Site After the Move?

Open the busiest pages first and test them as a normal user. Then check the lists people use daily and the search box. If search is the problem, read SharePoint search not working after migration. If a list looks short or slow, read SharePoint list not showing all items.

RecoveryTools SharePoint Migrator can start a job once or on a daily, weekly or monthly schedule and works unattended through nights and weekends. It also copies changes made during the move in a delta pass. For the full process, see how to migrate a SharePoint site to another tenant.

What are the Best Practices for a Fast SharePoint Site After Migration?

• Migrate in off-peak hours. Nights and weekends in your region give the service more room.
• Pause other heavy apps. Sync clients and backup tools share the same limits.
• Test key pages before launch. Use Page Diagnostics on your top ten pages.
• Index list columns early. Do it before users start filtering large lists.
• Plan for the search index. Tell users that search results can lag for a while.

Which Mistakes Make SharePoint Slower After a Move?

Four come up often. First, starting a huge copy at 10 in the morning. Second, leaving sync clients and backup jobs active during the copy. Third, rebuilding old pages with the same long list of web parts. Fourth, blaming the migration for slowness that the old site already had.

My Verdict on SharePoint Online Slow After Migration

Slow is not one problem. A slow copy is a timing and throttling problem. A slow site is a page, list or search problem.

Name the kind first. Then fix timing for the copy, or trim pages and index lists for the site.

Frequently Asked Questions

Published 17 October 2026. Limits and guidance come from Microsoft's pages on migration speed, avoiding throttling and modern portal limits. Product behavior comes from the RecoveryTools SharePoint Migrator page. Microsoft can change these limits, so check them before you plan.