Software & Automation
Migration & Automation Tooling
Internal tooling — portals, agents, and dashboards — built to support migration and operations work.
Scope
- Migration portal for tracking batch status and progress
- Background agents for queued migration jobs
- Operational dashboards for reporting
- REST API integrations between internal tools and Microsoft 365
Approach
- Started from the manual process already in use and automated it step by step.
- Built a migration queue so jobs run in the background instead of blocking an operator.
- Exposed status and progress through a lightweight portal instead of spreadsheets.
- Used REST APIs and PowerShell/Python scripting to connect tooling to Microsoft 365 and other systems.
Context
Large migrations and recurring operational tasks don’t scale well as manual checklists. This project covers the internal tools built to support that work: a migration portal, background processing agents, and reporting dashboards, built with .NET/ASP.NET Razor on the application side and PowerShell/Python for scripting and automation.
What this involved
The migration portal gives visibility into batch status and progress for migration jobs that would otherwise live in a spreadsheet — who’s been migrated, what’s queued, and what failed and needs attention. Behind it, background agents process queued jobs so operators aren’t stuck watching a script run in a terminal window.
Dashboards pull job and system data together into a single operational view, and REST API integrations connect these internal tools to Microsoft 365 (via Microsoft Graph) and other systems where needed.
Approach
Each piece of tooling started from a real manual process that was already happening — the goal was always to automate an existing bottleneck, not to build tooling for its own sake.