My contribution
- Browser-session and report extraction workflow
- Financial-year, date, pagination and checkpoint handling
- Canonical data model, matching and difference classification
- Readiness scoring, progress events and recovery tools
ERP-migration automation: reliable multi-year data extraction from legacy systems, then reconciliation you can trust.
My roleDesigned and implemented the system end-to-end, including the AI logic, backend, frontend, data processing and automation workflows.
Problem
When housing societies move to NoBrokerHood, years of financial records sit in legacy ERPs. Extracting them by hand is slow, and without systematic reconciliation nobody can be sure the migrated books agree.
System pipeline
Approach
Automates extraction of multi-year financial reports from legacy ERPs with checkpoints and count validation, then reconciles them against the new system. The workflow keeps inputs, decisions and exceptions visible so that a reviewer can understand how the output was reached.
My contribution
Try the demo
Simulated legacy ERP → real filtering, pagination, extraction, normalisation, de-duplication and reconciliation.
Create a synthetic browser session.
Ready for a synthetic extraction run.
Choose a date range to run real filtering, de-duplication and reconciliation.
This interactive demonstration is a simplified, synthetic representation inspired by an enterprise project. Production systems, company data and proprietary implementation details are not publicly exposed.
Result
The portfolio demo filters and paginates synthetic records, removes exact duplicates, reconciles two datasets and derives its readiness grade from the computed match rate.
Technical architecture
Legacy ERP session → Adopted browser session
Report + date range → Loaded, filtered report
Paginated table → Raw dataset + checkpoints
Raw datasets → Canonical records
Canonical records (old vs new) → Matches + difference categories
Reconciliation results → Readiness report
Tech stack
The portfolio demo itself is static TypeScript running locally in the browser with synthetic data and no API key.