SharePoint-to-IT-Glue Migration
Roughly 3,500 documents across 28 client organizations, moved with Graph API tooling and AI-assisted categorization.
context
An MSP consolidating onto IT Glue as its documentation system of record. Years of client documentation - runbooks, configurations, diagrams, vendor records - lived in SharePoint document libraries, spread across per-client folder trees that had grown organically. The documentation needed to live where technicians actually work, structured the way IT Glue expects.
problem
Move roughly 3,500 documents covering 28 client organizations out of SharePoint and into IT Glue, mapped to the right organization and the right document category on the other side. Done by hand, that is weeks of tedious, error-prone work - and misfiled documentation is worse than missing documentation, because technicians trust what they find.
constraints
The content is exactly the kind of material that cannot leak or be mishandled: client infrastructure documentation. Access had to run through properly scoped Microsoft Graph permissions rather than a user dragging files around. A run this size will be interrupted - API throttling, transient failures, a workstation reboot - so the pipeline had to be checkpointed and resumable rather than restartable-from- zero. And 28 organizations meant 28 chances to map a document to the wrong client, which is the one failure mode that was not acceptable.
approach
Python tooling against the Microsoft Graph API enumerated the SharePoint sites and document libraries and pulled content down in controlled batches, recording progress at every step so an interrupted run picked up where it left off. Each document was categorized for IT Glue automatically, with AI-assisted classification doing the first pass and explicit per-organization mapping keeping documents inside the right client boundary. Uploads went through the IT Glue API into the target structure. The pipeline itself was built by directing AI coding sessions against defined standards - the same working method this site's demo walks through.
outcome
About 3,500 documents migrated across 28 client organizations with automated categorization, off plaintext SharePoint storage and into the documentation system technicians use daily. The interrupted-run design proved itself in practice: the migration completed across multiple sessions without ever restarting from scratch.