I led the migration to AccuDash — a custom-built service system replacing a rigid, outdated platform — including a robust data connector that extracted all legacy service data so AccuDash launched with full access to the complete history.
Leaving the Old System Without Leaving the Data
The outgoing platform was rigid and outdated, but it held years of service history nobody could afford to lose. Migrating to AccuDash meant more than standing up a new system — it meant building a connector that pulled every legacy record across cleanly, so day one felt like continuity, not a reset.
What I Delivered
AccuDash migration
Replaced a rigid, outdated platform with AccuDash, a flexible custom-built service system.
Legacy data connector
Built a robust connector that extracted all legacy service data into AccuDash.
Zero data loss
Ensured a seamless transition with the full history intact — nothing left behind.
Better service ops
Improved service request tracking, scheduling, and completion on an adaptable platform.
Skills & Tools
The stack behind this build — tap any to see related work.
The Impact
AccuDash live with the complete legacy service history intact — better tracking, scheduling, and completion on a flexible platform the team can keep evolving as the department’s needs change.
Migrate the System, Keep the Memory
A migration that loses history isn’t a migration — it’s a restart. Building a connector that carried every legacy record into AccuDash let the team move to a better system without losing a day, or a record, of what came before.
Image credits: “Wikimedia Foundation Servers 2015-88” by VGrigas (WMF) (CC BY-SA 3.0) · “Mariam and Uche, a statistician and a software developer in Lagos (8102029130)” by DFID – UK Department for International Development (CC BY 2.0) · “123Net Data Center (DC2)” by 123net (CC BY-SA 3.0) · “Dell PowerScale F600 nodes in storage cluster” by Btrs (CC BY-SA 4.0)
