Featured engagement · Migration rescue
Called in after a botched migration, 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 the review 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 was done
A reconciliation script compared the destination against the source and surfaced every missing file. The folder-name and path faults were fixed at the root, the remaining migration completed, and a written runbook handed over so the team could maintain it.
Outcome
The move held, every missing file was recovered and reconciled against the source, and the team still runs on the handover runbook.
One symptom
Estimators cannot open project files in the middle of a live bid
Root cause 01
Folder names containing a "#" silently broke OneDrive sync, so files never arrived.
Root cause 02
The deepest project paths sat on the Windows path-length limit and failed without an error anyone saw.
Root cause 03
A recent Windows update had broken the sign-in that OneDrive, Outlook, and SharePoint all depend on.
Proof of recovery
A reconciliation script compared the destination against the source, surfaced every missing file, and verified the recovery before handover.
Reconstructed from the documented diagnosis of this delivered engagement. Client anonymized.