Monday, May 25, 2026

SP2010 → SPO Migration Troubleshooting Matrix

#	Issue / Category	Symptoms	Root Cause	Resolution / Fix	Validation Step
1	Unsupported Features	Missing pages, web parts, or errors after migration	Deprecated features (e.g., InfoPath, 2010 workflows, sandbox solutions)	Replace with Power Apps / Power Automate / SPFx; rebuild customizations in Modern UI	Verify feature parity and test forms/workflows in SPO
2	Classic Workflow Failure	2010 workflows not triggering	2010 workflows retired in SPO (Aug 2020+)	Recreate workflows in Power Automate or upgrade to 2013 workflows	Trigger and validate each workflow path
3	Large Content Database	Migration fails or times out	SPO 200 GB site collection limit	Split content into smaller sites; archive old data; migrate incrementally	Check migrated site sizes in SharePoint Admin Center
4	File/Path Length Issues	File skipped with “Path too long”	URL > 400 characters in SPO	Shorten folder structure; rename long files	Re-run migration logs → zero “Path too long” errors
5	Unsupported Characters in File Names	File skipped during migration	Invalid characters (# % & { } ~)	Clean up names via PowerShell or pre-migration report	Validate all skipped items remediated
6	Metadata Missing	Created/Modified dates or Authors incorrect	Metadata not mapped or not preserved	Enable “Preserve authorship” in SPMT/ShareGate; run migration with full control	Verify metadata fields in SPO list/library
7	Orphaned Users / Permissions	Access denied or wrong permissions post-migration	Legacy AD users not mapped to Azure AD	Clean up orphaned users; use Azure AD groups	Check “Site Permissions” and confirm role accuracy
8	Custom Master Pages / Branding Broken	Pages look distorted or missing layout	Classic master pages not supported in Modern UI	Convert sites to Modern; apply SPO themes	Open site → Confirm Modern page rendering
9	Custom Solutions (WSP)	Features missing or failing	WSP/Farm solutions not deployable to SPO	Rebuild with SPFx or Power Apps	Validate SPFx deployment on target site
10	BCS or External Content Type Issues	External lists fail to load	On-prem BCS connection not portable to cloud	Use Power Automate or Azure Logic Apps	Validate new data connection in SPO
11	SPMT Authentication Errors	SPMT fails login or “token expired”	MFA/conditional access blocking	Register app in Azure AD; run SPMT with app credentials	SPMT connects successfully and transfers content
12	Throttling / Slow Migration	Migration stops intermittently	Microsoft 365 throttling	Reduce parallel jobs; migrate off-peak; use incremental migration	Monitor migration rate → steady without pauses
13	Search Not Showing New Content	New content not searchable	SPO search index delay	Wait 24–48 hours; reindex site/library	Search new item successfully
14	Broken Links	Internal links point to old SP2010 URLs	Absolute URLs hard-coded	Replace with relative URLs or use link-fix scripts	Validate internal hyperlinks on key pages
15	Navigation / Quick Launch Missing	Navigation links lost after migration	Custom navigation not mapped	Rebuild navigation manually or via PowerShell	Compare with pre-migration navigation
16	User Profile Sync Issues	User data not updated in SPO	Missing or outdated Azure AD sync	Run Azure AD Connect sync; update UPNs	Validate updated profiles in M365 Admin
17	Version History Missing	Documents show only 1 version	Tool settings not preserving versions	Enable “Preserve Version History” in migration tool	Check file → Version History shows all versions
18	Lookup Columns Broken	Lookup fields not resolving	Source/target list IDs changed	Recreate lookup column relationships	Validate field lookup references
19	Custom Scripts Disabled	Scripted pages not functioning	SPO blocks custom scripts by default	Enable custom scripting via PowerShell (if required)	Verify functionality of script-based pages
20	Performance Post-Migration	Pages load slow in SPO	Large lists, legacy web parts	Enable list indexing; convert classic pages	Confirm response time improved (<3s typical)
21	Alerts Not Working	Users not getting notifications	Alerts not recreated post-migration	Recreate alerts manually or via Power Automate	Trigger change → user receives alert
22	Large List (>5,000 items)	List view threshold error	SPO list view threshold limit	Use indexed columns, filters, or modern views	View renders successfully without error
23	Unsupported Web Templates	Site migration fails	Template (e.g., Blog, MySite) not supported	Recreate with modern communication/team site	Migration completes successfully
24	Retired Workflows in Migration Report	Warnings in ShareGate/SPMT logs	Detected 2010 workflows	Rebuild or delete before migration	No workflow-related warnings remain
25	Email-Enabled Libraries Missing	Incoming email feature lost	SPO doesn’t support email-enabled libraries	Use Power Automate with shared mailbox	Verify email → document arrives in library

Recommended Pre-Migration Checks

Check	Tool	Purpose
Pre-migration assessment	SMAT (SharePoint Migration Assessment Tool)	Identify unsupported features, long URLs, large lists
Content inventory	PowerShell / ShareGate	List of sites, libraries, permissions
Permissions cleanup	PowerShell	Remove orphaned AD accounts
Workflow inventory	Nintex / PowerShell	Document all 2010 workflows
File & path validation	PowerShell	Detect long paths or illegal characters

🧰 Recommended Post-Migration Validation

✅ Compare item counts between SP2010 and SPO
✅ Verify permissions for key users/groups
✅ Check version history and metadata preservation
✅ Validate navigation and links
✅ Ensure workflows and alerts are functional
✅ Run PowerShell reports for site health and quota
✅ Reindex sites if search results are incomplete

SharePoint Subscription Edition (SPSE) – Common Errors, Challenges, and Limitations

This is a very common interview topic for SharePoint Administrators, Architects, and Migration Leads.

1. Installation Challenges

Error: Prerequisite Missing

Symptoms

Prerequisite installation failed.
Setup cannot continue.

Root Cause

Missing Windows Features
Missing .NET components
Unsupported OS version

Resolution

Install-WindowsFeature Web-Server
Install-WindowsFeature NET-Framework-Features

Validate all SPSE prerequisites before installation.

2. Configuration Wizard Failures

Error

Failed to create configuration database.

Root Cause

SQL connectivity issues
Farm account permissions missing
SQL aliases incorrectly configured

Required SQL Roles

dbcreator
securityadmin

for the setup account.

3. MinRole Issues

SPSE strongly encourages MinRole deployment.

Common Problems

Server role mismatch detected.

Impact

Health Analyzer warnings
Performance degradation
Unsupported architecture

Example

Application services running on WFE
Search services on wrong server

4. Distributed Cache Challenges

Although SPSE modernized some underlying services, cache-related issues can still occur.

Symptoms

Slow page loads
Authentication delays
Newsfeed issues

Root Causes

Insufficient RAM
Improper service placement
Farm topology issues

5. Search Problems

Common Errors

Crawl Failure

Access is denied

Search Index Not Updating

Fresh content not searchable

Root Causes

Crawl account permissions
Search topology configuration
SQL performance bottlenecks

Real-Time Example

After migration from SP2019:

Search returns zero results

Often resolved by rebuilding the search index.

6. Large Content Database Limitations

Challenge

Organizations frequently maintain:

500 GB
1 TB
2 TB

content databases.

Impact

Slow backup
Slow restore
Extended upgrade windows
Longer maintenance periods

Best Practice

Keep content databases reasonably sized and distribute site collections appropriately.

7. Custom Solution Compatibility

Common Error

Missing Feature
Missing Web Part

Root Cause

Custom WSP solutions from older SharePoint versions.

Real-Time Issue

After migration:

Web Part Error:
Cannot import this web part.

because the assembly is missing or unsupported.

8. Workflow Challenges

Many organizations still use:

SharePoint 2010 Workflows
SharePoint 2013 Workflows
Nintex
K2

Issues

Workflow suspended
Workflow failed

Root Cause

Workflow dependencies not upgraded or migrated correctly.

9. Authentication Challenges

Common Problems

Access Denied
Unexpected Login Prompt
People Picker Failure

Causes

Kerberos misconfiguration
Claims authentication issues
Service Principal Name (SPN) issues

10. SSL Certificate Problems

Symptoms

Certificate Warning
Site Not Secure

Root Cause

Expired certificates
Missing intermediate certificates
IIS binding issues

Real-Time Impact

Users cannot access production portals.

11. SQL Server Dependency

SPSE relies heavily on SQL Server.

Issues

High CPU
Slow Queries
Blocking
Deadlocks

Impact

Slow SharePoint pages
Search delays
Timer job failures

12. User Profile Synchronization Problems

Symptoms

Missing profile photos
Manager hierarchy missing
Audience targeting failures

Root Causes

AD synchronization failures
Permissions issues
Synchronization service misconfiguration

13. Patch and Upgrade Challenges

Issue

All SharePoint servers must remain at the same patch level.

Common Error

Upgrade required.

Scenario

One server patched successfully.

Second server patch failed.

Farm becomes inconsistent.

14. Backup and Restore Challenges

Common Problems

Large backup windows
Storage consumption
Long recovery times

Enterprise Concern

Disaster Recovery (DR) testing often takes many hours.

15. Performance Issues

Symptoms

Slow site collection
Slow document library
Slow search results

Root Causes

Large lists
Missing indexes
SQL bottlenecks
Poor farm design

16. Modern UI Limitations Compared to SharePoint Online

SPSE supports modern experiences, but not all cloud features.

Missing / Limited Features

AI-powered features available in Microsoft 365
Microsoft Copilot capabilities
Viva integrations (limited compared to cloud)
Some cloud-only innovations
Continuous cloud feature rollout

Interview Point

SPSE receives feature updates, but SharePoint Online generally gets new capabilities first.

17. Third-Party Product Compatibility

Examples:

Nintex
AvePoint
Bamboo Solutions
K2

Challenge

Not every version supports SPSE.

Resolution

Verify vendor support matrices before upgrades.

18. High Availability Complexity

Challenge

Designing HA environments requires:

Multiple SharePoint servers
SQL High Availability
Load Balancers
Disaster Recovery Sites

Costs

Infrastructure Cost
Licensing Cost
Operational Cost

can be significant.

19. Licensing Challenges

SPSE uses a subscription-based licensing model.

Common Organizational Concerns

Budget planning
Renewal management
Compliance audits

20. Migration Challenges

Common migration paths:

SharePoint Server 2016 → SharePoint Subscription Edition
SharePoint Server 2019 → SharePoint Subscription Edition

Typical Issues

Missing Features
Customizations
Workflow Failures
Search Reconfiguration
Authentication Changes

Top 10 Real-Time Production Errors

Error	Likely Cause
Configuration Database Creation Failed	SQL permissions
Access Denied	Authentication or permissions
Search Crawl Failed	Crawl account permissions
Timer Job Failed	Service account or SQL issue
Missing Feature	Custom solution missing
Web Part Error	Assembly missing
Distributed Cache Issues	Memory or topology problem
User Profile Sync Failure	AD permissions
Upgrade Required	Patch mismatch
Site Slow Performance	SQL or indexing issues

SharePoint 2019 to SharePoint Subscription Edition (SE) Upgrade – Major Challenges

SharePoint 2019 to SharePoint Subscription Edition (SE)

Upgrade – Major Challenges

First, remember an important interview point:

✅ SharePoint 2019 → SharePoint SE is NOT an in-place upgrade.

✅ Microsoft supports the Database Attach Upgrade method. You build a new SPSE farm, copy databases, and attach them to the new farm. (Microsoft Learn)

High-Level Upgrade Flow

Top 15 Real-Time Challenges

1. Missing Custom Solutions (WSPs)

Problem

Many organizations have:

Custom Web Parts
Custom Features
Custom Site Definitions
Farm Solutions

When content databases are mounted, SPSE expects these components to exist.

If missing:

Test-SPContentDatabase

Shows:

Missing Feature
Missing Setup File
Missing Web Part

This is one of the most common upgrade blockers. Microsoft specifically recommends reinstalling all customizations before attaching content databases. (Microsoft Learn)

Real-Time RCA

Developer left company years ago.

Source code unavailable.

Feature IDs exist in database but solution package no longer exists.

Resolution

Inventory all custom solutions.
Rebuild unsupported code.
Remove orphaned features.

2. Large Content Database Size

Problem

Many environments contain:

500 GB
1 TB
2 TB+

databases.

Upgrade duration becomes very long.

Challenges

SQL backup time
Restore time
Mount time
Validation time

Resolution

Split large databases before migration.

3. Search Service Migration

Problem

Search topology changes.

Search databases cannot simply be copied and assumed healthy.

Common Issues

Crawl failures
Index corruption
Missing content sources

Resolution

Most organizations rebuild Search after migration.

4. Service Application Compatibility

Supported service application databases include:

Managed Metadata
Search
User Profile
Secure Store
BDC

But configuration mismatches can create failures. (Microsoft Learn)

Real-Time Issue

Managed Metadata database attached.

Term Store inaccessible.

Cause:

Service account permission mismatch.

5. Authentication Issues

Problem

Old farms often use:

NTLM
Classic Mode
Kerberos

SPSE primarily uses Claims Authentication.

Symptoms

Login failures
Access denied
Broken People Picker

Resolution

Plan authentication migration carefully.

6. Alternate Access Mapping (AAM) Problems

Problem

URLs change during migration.

Example:

Old:
http://portal.company.com

New:
https://portal.company.com

Impact

Broken bookmarks
Office integration issues
Workflow failures

Microsoft recommends recreating the same URLs whenever possible. (Microsoft Learn)

7. Workflow Failures

Problem

Organizations commonly use:

SharePoint 2010 Workflows
SharePoint 2013 Workflows
Nintex
K2

Issues

After migration:

Workflow Suspended
Workflow Failed
Workflow Not Found

Resolution

Inventory workflows before migration.

8. InfoPath Forms

Problem

Many legacy environments use:

InfoPath Forms

Issues

Missing templates
Missing data connections
Browser form rendering failures

Microsoft specifically highlights migrating InfoPath templates and connections. (Microsoft Learn)

9. SQL Version Challenges

Problem

Old environment may use:

SQL 2016
SQL 2017

New environment:

SQL 2022

Issues

Compatibility mode
Performance changes
Database upgrade warnings

10. User Profile Synchronization

Problem

User Profile Service often breaks.

Common Symptoms

No profile photo
No manager hierarchy
No audience targeting

Resolution

Reconfigure profile synchronization.

11. Third-Party Product Compatibility

Examples

Nintex
K2
AvePoint
Bamboo
Metalogix
DocAve

Problem

Older versions may not support SPSE.

Resolution

Upgrade third-party products first.

12. MinRole Architecture Changes

Problem

SP2019 farms may not follow MinRole.

SPSE farms often use:

Front-End
Application
Search
Distributed Cache

Challenge

Server roles need redesign.

13. Performance Degradation After Upgrade

Symptoms

Slow Site Collection
Slow Search
Slow Page Load

Root Causes

Missing indexes
SQL memory allocation
Search rebuild
Cache warming

Resolution

Perform performance testing before production cutover.

14. Security and Permission Issues

Problem

Broken inheritance often surfaces after migration.

Examples

Access Denied
Missing Permissions
Broken Groups

Resolution

Audit:

Get-SPUser
Get-SPGroup

before migration.

15. Downtime and Cutover Planning

Biggest Enterprise Challenge

Business asks:

"Can we migrate with zero downtime?"

Reality:

Database Backup
Restore
Validation
DNS Switch

requires a maintenance window.

Common Strategy

Freeze Content
Read-Only Mode
Backup Databases
Restore Databases
Mount Content
Validate
DNS Cutover

Microsoft's documented process includes placing the old farm in read-only mode while the new SPSE farm is upgraded. (Microsoft Learn)

Interview Question

Q: What is the biggest challenge during SP2019 → SPSE migration?

Answer:

"The biggest challenge is identifying and validating all customizations before attaching content databases. In my experience, missing WSP solutions, custom web parts, workflow dependencies, authentication changes, and third-party integrations are the most common causes of upgrade failures. I always run Test-SPContentDatabase, inventory all custom components, validate service applications, and perform multiple test migrations before the production cutover." (Microsoft Learn)

Real-Time Project Migration Checklist

Pre-Migration

Inventory farm solutions
Inventory workflows
Inventory service applications
Validate SQL health
Run Test-SPContentDatabase
Verify third-party products
Document AAM URLs

Migration

Build SPSE farm
Install custom solutions
Restore databases
Attach service app databases
Mount content databases

Post-Migration

Validate sites
Validate Search
Validate User Profiles
Validate Workflows
Performance testing
Security testing
Business UAT
DNS cutover

These are the areas most frequently discussed in senior SharePoint Administrator, SharePoint Architect, and SharePoint Migration Lead interviews.

From <https://chatgpt.com/c/6a13c835-b558-8321-9678-3f95678f6f56>

What is DLP (Data Loss Prevention) in SharePoint Online? – Easy Explanation

Think of DLP as a security guard for your documents and emails.

Its job is to prevent users from accidentally or intentionally sharing sensitive information such as:

Credit Card Numbers
Aadhaar Numbers
PAN Numbers
Passport Numbers
Bank Account Details
Patient Health Information (PHI)
Clinical Trial Data
Confidential Company Documents

Real-Time Example

Suppose an employee uploads an Excel file to SharePoint containing:

Employee Name
PAN Number
Aadhaar Number
Salary

If a DLP policy is configured:

✅ SharePoint detects the sensitive information.

✅ User receives a warning.

✅ External sharing can be blocked.

✅ Compliance team gets notified.

✅ An audit record is created.

Without DLP:

❌ User may accidentally share the file externally.

❌ Sensitive data could be exposed.

Where Does DLP Work?

DLP can protect data across:

DLP Architecture

Common Sensitive Information Types

Microsoft provides hundreds of built-in detectors.

Examples:

Data Type	Example
PAN Card	ABCDE1234F
Aadhaar	1234 5678 9012
Passport	A1234567
Credit Card	4111-1111-1111-1111
Bank Account	Account Number
US SSN	123-45-6789

Types of DLP Actions

1. Show Policy Tip

Displays a warning.

Example:

Warning:
This file contains sensitive information.

2. Block Access

Prevents sharing.

Example:

This document cannot be shared externally.

3. Restrict Download

Users can view but not download.

4. Send Alert

Emails compliance or security teams.

5. Generate Incident Report

Logs the violation.

How to Create a New DLP Policy (Step-by-Step)

Step 1: Open Microsoft Purview

Go to:

Microsoft Purview Portal

Step 2: Navigate to DLP

Solutions
|
+-- Data Loss Prevention

Click:

Policies

Step 3: Create Policy

Click:

+ Create Policy

Step 4: Choose Template

Microsoft provides templates:

Examples:

Financial Data
Privacy Data
Healthcare Data
GDPR
PCI-DSS
Custom Policy

For example:

Privacy Data

Step 5: Name the Policy

Example:

Protect PAN and Aadhaar Data

Description:

Prevent sharing of PAN and Aadhaar numbers.

Step 6: Select Locations

Choose where DLP should apply:

✅ SharePoint Sites

✅ OneDrive Accounts

✅ Exchange Emails

✅ Teams Chat

Example:

Apply to SharePoint Online only

Step 7: Create Rule

Click:

Create New Rule

Rule Name:

Block PAN Information Sharing

Step 8: Configure Conditions

Choose:

Content Contains

Select Sensitive Information Types:

India PAN Number
India Aadhaar Number

Condition:

If content contains at least 1 PAN number

Step 9: Configure Actions

Example:

Block External Sharing
Send Alert to Security Team
Show Policy Tip

Step 10: Configure User Notifications

Enable:

Notify users

Message:

This document contains sensitive information.
External sharing is not allowed.

Step 11: Incident Reports

Send reports to:

security@company.com
compliance@company.com

Step 12: Test Mode

Before enforcing:

Run Policy in Test Mode

Benefits:

No user impact
See what would be blocked
Validate policy

Recommended in production.

Step 13: Turn On Policy

After testing:

Enable Policy

Policy becomes active.

Real-Time Pharma / Clinical Research Example

In a CRO environment (such as clinical trials):

Sensitive data includes:

Patient IDs
Medical Records
Lab Reports
Adverse Event Data
Trial Participant Information

DLP Rule:

If Patient Information Found
     |
     +--> Block External Sharing
     +--> Notify Compliance Team
     +--> Log Incident

This helps support GDPR, HIPAA, and GxP compliance requirements.

How to Verify DLP is Working

Upload a Test File

Example:

Employee: John
PAN: ABCDE1234F

Upload to SharePoint.

Expected:

Warning appears
Sharing restrictions apply
Alert generated

PowerShell Verification

Connect to SharePoint Online and verify policy effects through Purview compliance reporting and audit logs.

Useful audit locations:

Microsoft Purview
|
+-- Audit
+-- DLP Alerts
+-- Activity Explorer