Featured engagement · Migration rescue
Called in after a botched migration. We stabilized it, then finished the move
Situation
A regional contractor had moved twenty-five years of project files to SharePoint and OneDrive on the cheap. It looked fine until estimators could not open files in the middle of a live bid, and the team had started blaming the platform.
What we found
Three faults were tangled into one symptom: folder names containing a "#" silently broke OneDrive sync, the deepest project paths sat on the Windows length limit, and a recent Windows update had broken the sign-in that OneDrive, Outlook and SharePoint all depend on.
What we did
We wrote a reconciliation script that compared the destination against the source and surfaced every missing file, fixed the folder-name and path faults at the root, completed the remaining migration, and handed over a written runbook so the team could maintain it.
Outcome
The move held, the missing files were recovered, and the readiness gaps that caused the chaos are exactly the ones a five-day assessment catches before the first file moves.