OneDrive Admin Checklist: shared library sync stays pending for department migrations

When you migrate department data between SharePoint sites or OneDrive accounts, shared library sync often stays in a pending state. Users see the sync icon spinning or showing a clock symbol for hours. This happens because the sync client must re-index the library after the migration changes the file location or metadata. This article explains why shared library sync gets stuck, lists the exact checks an admin must run, and provides the steps to force sync completion without data loss.

Why Shared Library Sync Gets Stuck After Department Migration

When you move a department from one SharePoint site to another, the OneDrive sync client does not automatically know the new location. The client tries to sync files based on the old site URL and GUID. If the old site no longer exists or the permissions changed, the sync engine marks the library as pending and never completes.

Root Cause: Stale Sync Metadata

The OneDrive sync client stores a local database of file paths, site IDs, and sync tokens. After migration, the token for the old library becomes invalid. The client sends a request to SharePoint but receives an error or a redirect. Instead of updating the path, the client enters a retry loop. This loop shows the pending state indefinitely.

Root Cause: Permission Mismatch

Department migrations often involve re-creating security groups or updating Azure AD group memberships. If the user’s account does not have explicit access to the new library, the sync client cannot download the file list. The client shows pending because it cannot enumerate the items.

Root Cause: File Name or Path Length Limits

Migrated files sometimes have names that exceed 400 characters or contain characters that SharePoint blocks. The sync client detects the invalid file, stops processing the entire library, and shows pending for all remaining files.

Admin Checklist to Fix Pending Shared Library Sync

Complete these checks in the order listed. Do not skip any step. Each check addresses one of the root causes described above.

Step 1: Verify User Permissions on the Target Library

1. Open the SharePoint admin center
   Go to Admin centers > SharePoint. Select Active sites and find the site that contains the migrated library.
2. Check library permissions
   Select the site, then choose Site permissions. Click Advanced permissions settings. Confirm the user or their security group appears in the list with at least Read access.
3. Test access from a private browser window
   Open InPrivate or Incognito mode, sign in as the affected user, and navigate directly to the library URL. If the user sees an access denied error, add them to the site members group.

Step 2: Reset the Sync Relationship for the Migrated Library

1. Stop sync for the old library
   On the user’s computer, right-click the OneDrive cloud icon in the system tray. Select Settings > Account. Under Choose folders, find the old library name and click Stop sync.
2. Remove cached files from the old path
   Open File Explorer and navigate to C:\Users\[username]\SharePoint. Delete any folder that matches the old site name. Do not delete files from the user’s Documents or Desktop folders.
3. Sync the new library
   In a web browser, open the new library. Click the Sync button. In the dialog, click Sync now. The client will create a new sync relationship with the correct URL.

Step 3: Run the OneDrive Sync Troubleshooter

1. Download and run the Microsoft Support and Recovery Assistant
   Go to aka.ms/SaRA. Select OneDrive for Business and then Sync issues. The tool checks for file name violations, permission errors, and sync metadata corruption.
2. Review the generated report
   If the tool finds blocked file names, note the exact file paths. Rename those files on the SharePoint site to remove special characters or shorten the path to under 400 characters.

Step 4: Force a Full Resync Using Registry Edit

1. Close OneDrive completely
   Right-click the OneDrive icon and select Quit OneDrive. Confirm that no OneDrive.exe process remains in Task Manager.
2. Open Registry Editor
   Press Windows + R, type regedit, and press Enter. Navigate to HKEY_CURRENT_USER\Software\Microsoft\OneDrive\Accounts\Business1.
3. Delete the TenantId and SharePointUrl values
   Right-click TenantId and choose Delete. Do the same for SharePointUrl. Close Registry Editor.
4. Restart OneDrive
   Press Windows + R, type onedrive, and press Enter. The client will re-authenticate and rebuild the sync database from scratch.

If OneDrive Still Shows Pending After the Main Fix

OneDrive shows pending only for specific file types like .pst or .ost

Outlook data files are blocked by default in SharePoint libraries. Go to SharePoint admin center > Settings > OneDrive > Sync. Under Block syncing specific file types, check if .pst or .ost appear in the list. Remove those entries if your migration requires these files to sync.

Pending state appears on a library that was synced before migration

The old sync token is cached in the user’s local OneDrive database. Use the Reset OneDrive command. Open a Run dialog with Windows + R, type onedrive.exe /reset, and press Enter. Wait two minutes. If sync does not start, type onedrive.exe in the same dialog to relaunch the client.

Multiple users in the same department see pending sync at the same time

This indicates a tenant-level issue. Check the Microsoft 365 admin center > Health > Service health. Look for advisory ID SP#### or OD#### related to SharePoint migration or OneDrive sync. If a service incident exists, wait for the resolution before continuing. Do not run the registry reset on all machines until the incident is closed.

Shared Library Sync Methods After Migration: Comparison

Item	Stop and Re-Sync	Registry Reset
Description	Removes old sync relationship and adds new library	Deletes cached tenant and site URLs to force full rebuild
User data loss risk	None; local files remain in SharePoint folder	None; only sync metadata is cleared
Time to complete	5 to 10 minutes per machine	2 to 5 minutes per machine
Requires admin rights	No	Yes, to edit the registry
Best for	Single library migration with one or two users	Bulk migration where many users have stale tokens

Use the stop-and-re-sync method when only a few users are affected. Use the registry reset method when the migration affected an entire department and you need to clear stale tokens on many machines quickly.

You now have a checklist that covers permissions, sync relationship reset, file name validation, and tenant-level health checks. Run the checks in order and test sync on one pilot user before deploying to the full department. For future migrations, enable the SharePoint Migration Tool (SPMT) with the Preserve file IDs option to reduce the number of pending sync states.