Vastu Vihar — Enterprise ERP Replacement & Real-Estate Operations

Enterprise replacement, from business data to daily operations

I owned Vastu Vihar’s company-wide migration from Dataman Real Builder to ERPNext/Frappe and continued engineering its business workflows. This was a replacement of an existing enterprise ERP, spanning property inventory and bookings, construction, collections, branch accounting, procurement, stock, HR and payroll. Payroll/HRMS migration from Keka was also part of my work.

Verified operating scale

These are current platform counts checked on 29 September 2026, not counts attributed to the original cutover. Project records include phases; customer records are not a claim about unique people.

• 50 enabled branches out of 72 branch records.
• 324 project/phase records and 10,951 unit-master records.
• 31,917 customer records and 356,986 payment/receipt entries.
• 2,156,965 general-ledger entries.
• 755 active employees; 5,129 employee records including historical records.

Engineering behind the migration

• Carried the business onto a Frappe/ERPNext customization layer with branch, project, phase and booking relationships. The implementation retains Dataman booking-reference fields in booking statements and receipt generation.
• Worked on booking and payment workflows linking unit allocation, customer records, construction milestones and payment schedules, including cancellation and reversal behavior.
• Continued engineering across branch accounting, fund movements, procurement, stock and payroll, with operational reporting and field-application integrations.

What the platform enables

A live collection-and-booking report for 1–29 September 2026 returned 42 branch rows and reported 3.73 seconds of execution time in one observed run. This is a point-in-time observation, not a benchmark or a measured improvement over Dataman.

• A connected property lifecycle: inventory and booking through construction tracking, collections, transfers and registry approvals.
• Consolidated branch-level collection and booking reporting, with project-wise filtering and separate collection channels.
• Organization-specific approval and access workflows maintained in the ERP customization layer.

Platform & operations

• CI/CD and Kubernetes deployments with ArgoCD, multi-bench Frappe operations behind Nginx, and ELK monitoring.
• Keycloak/OAuth2 integration and published Frappe authentication tooling.
• Mentored interns in Python and Frappe/ERPNext development.

Evidence and scope

The migration source and end-to-end ownership are my account of the work. Operating-scale figures were checked against the live ERP; workflow descriptions were cross-checked against the application repository. Private source code, customer records and financial amounts are not published here. Before/after cost, time-saving and error-reduction percentages require an old-system baseline and are not asserted.