SharePoint Migration Tool (SPMT) Expert Needed to Fix Failing 540GB Migration

Job ID: 40299777

Budget: $2 – $8 USD

I need an expert with deep, hands-on experience using Microsoft’s SharePoint Migration Tool (SPMT) to troubleshoot and complete a large migration that keeps failing.


Environment details:


Source: Windows Server file server (local NTFS file share)

Destination: SharePoint Online document library

Total data: ~540GB

Key folder: “Titan Fire Protection” with a “00-PROJECTS” folder around 400GB

Large subfolders inside 00-PROJECTS (approx): 2023 – 197GB, 2025 – 124GB, 2024 – 70GB


Maintenance window: We are currently in a maintenance window over the weekend and need to get as much done as possible before Monday 6:00 AM (server local time).


The current migration job has been run several times and fails partway through. I will provide:


The SPMT migration.log file (already exported, ~5MB)

Screenshots of the folder structure

Access to the file server and tenant (via remote session) so you can review and adjust settings

I am looking for someone who can:

Analyze the existing migration.log and identify the root cause of the failures

Recommend a clear migration strategy (e.g., splitting into smaller jobs, adjusting package sizes, concurrency, staging location, etc.)

Implement the migration plan end‑to‑end, including multiple passes (non‑projects folders first, then large annual project folders, then final delta sync)

Work within a tight timeline over the weekend to move as much as realistically possible before the maintenance window ends

Please only apply if you:

Have strong, proven experience with SPMT on large (>300GB) file share to SharePoint Online migrations

Can start immediately and are comfortable working under time pressure

Can clearly explain your proposed approach based on the environment above

When you apply, briefly answer:

What is the largest SPMT migration (in GB) you have successfully completed?

How do you normally handle very large subfolders (100GB+) in SPMT?

What would be your first 2–3 steps after reviewing our migration.log?