Overview
We partnered to transfer and modernize multiple legacy management areas — training videos, vehicle requests, purchasing, legal records, and a master calendar — into a single tenant-aware plugin platform. We rebuilt each area on backend APIs and a React frontend, layered in slim AI-assisted suggestions, and delivered an idempotent, tenant-scoped migration with a QA-backed cutover.
Challenges
- Critical management workflows — training videos, vehicle requests, purchasing, legal records, and calendars — were trapped in disconnected legacy systems with no unified manager view.
- Legacy features were tied to old code and UI, making them risky to copy directly and impossible to maintain on a modern, tenant-aware platform.
- Vehicle requests, purchasing, and approvals lacked structured workflows, leaving managers without a clear submit-and-approve path or visibility into inventory.
- Migrating years of legacy data risked ambiguity and corruption without agreed export shapes, controlled cutover timing, and reliable update rules.
- Multi-tenant data carried real cross-tenant import risk if migration ran without strict tenant scoping.
- Purchasing and receipt handling were limited and informal, with no vendor management, price comparison, or pre-approval controls for inventory-linked items.
- Stakeholders wanted AI to help with vehicle assignment, purchasing, and calendar decisions, but unchecked AI risked overreaching into autonomous actions instead of safe recommendations.
- Without disciplined scope control, the transfer could balloon into rebuilding the entire platform and rewriting non-target and legacy systems.
- A late, untested cutover risked release failures across training, vehicles, purchasing, legal, and calendar areas all going live at once.
Solution highlights
- We transferred the training video area onto the new platform with hosting, upload, listing, management, and playback support.
- We rebuilt vehicle requests with data models, APIs, and a UI wired into task, operations, and inventory-related workflows.
- We exposed vehicle inventory to AI and added AI-assisted vehicle request assignment suggestions for managers.
- We expanded receipt handling into a full purchasing module with invoice and receipt upload and management.
- We implemented a manager pre-approval workflow where a requester submits and a direct supervisor approves.
- We added vendor management and price shopping for commonly purchased, inventory-linked items, plus an AI purchasing MVP inspired by procurement-assistance flows.
- We transferred legal records with list, detail, upload, models, APIs, and frontend support.
- We delivered a master calendar that brings events and volunteer days into a single view, with an AI-assisted display and suggestion layer.
- We built JSON-based data import with tenant-scoped management commands that perform authoritative, idempotent create-or-update migrations, and ran a dedicated integration phase for cross-area wiring, QA, cutover, and documentation.
Outcomes
- Managers now work from one modern, tenant-aware workspace spanning training, vehicles, purchasing, legal, and calendar instead of juggling disconnected legacy systems.
- Legacy features run on clean backend APIs and a React frontend, making them easier to maintain and extend without inheriting old code or UI.
- Vehicle requests flow through structured workflows connected to tasks, operations, and inventory, with AI suggesting assignments to speed decisions.
- Purchasing now supports invoices, receipts, vendor management, price shopping, and a clear submit-then-supervisor-approve workflow.
- AI assistance stays safely scoped to recommendations and display only across vehicles, purchasing, and calendar — managers keep final control.
- Legacy data migrates reliably from client-provided JSON exports, with idempotent updates that can be re-run without creating duplicates.
- Tenant-scoped migration commands protect against cross-tenant data leakage during import.
- A reserved integration and release phase with QA and a controlled cutover reduced the risk of a disruptive all-at-once launch.
- Tight scope discipline kept the project focused on the target platform, avoiding changes to legacy and non-target systems and unnecessary procurement-product parity.