Compatibility scanning
Find invalid names, reserved files, long path segments, destination paths over 400 characters, large files and other common blockers.
Scan file shares for common SharePoint migration issues, design folder-level access and package a review-ready handoff. Everything stays on the machine.
691 KB · No installation or administrator rights required
One practical workspace
Find invalid names, reserved files, long path segments, destination paths over 400 characters, large files and other common blockers.
Explore the full folder tree, define proposed groups and members, then set a permission level for each group on each folder.
Confirm the plan and export one integrity-checked ZIP with reports, mappings, project data and a PowerShell group provisioning script.
Save the complete working session as a single .sprproject file. Open it on another machine and continue where you left off.
A clearer migration conversation
Choose the source directory and planned SharePoint destination. The tool builds an expandable tree and checks every discovered item.
Filter blockers, inspect path lengths and export the findings that need remediation before content moves.
Create proposed security groups, add members and map access levels to selected folders with inheritance-aware controls.
Confirm the customer plan and produce a single package for the authorised migration engineer to validate and implement.
Local by design
SharePoint Readiness does not upload files, connect to Microsoft 365 or silently change tenant settings. Scans, project data and autosaves remain on the Windows machine.
Latest release
Portable Windows executable. Run it in place, save a project and send that single project file when someone else needs to continue.
E41915A13667E8EEC9E10BCFCF4B7FFBFE5236071BE280D9132347DEA61990F3A note on Windows security: this independent release is not code-signed yet, so Microsoft Defender SmartScreen may ask you to confirm before running it. Verify the SHA-256 value above if you received the file from anywhere else.
Good questions
No. The desktop application is a planning and handoff tool. It does not connect to Microsoft 365. The handoff can include a PowerShell script for an authorised engineer to review and run separately.
A project file can contain the selected source path, scan results, folder list, findings, proposed groups and members, access assignments and customer confirmation details. It does not contain the content of scanned files.
Yes. Save a .sprproject working file so another person can reopen and edit the complete session. Once confirmed, export the separate ZIP handoff for the delivery team.
The supplied rules cover invalid and reserved names, temporary Office files, leading or trailing spaces, trailing periods, 255-character path segments, the complete 400-character destination path and configurable file-size limits.
No. Download the EXE and run it as the signed-in user. Its embedded runtime is unpacked under the user's local application data folder; it does not write to system folders.
No. It is an early assessment and access-planning aid. Always validate the final package, run generated scripts with -WhatIf first, and complete the migration platform's own pre-flight checks.
Made independently
SharePoint Readiness is built and maintained by Jamie Chalmers. If it saves you time, you can support continued development without a subscription or an awkward pop-up.