ComputerEase to a live lakehouse in eleven days
A residential specialty contractor running ComputerEase for job cost and accounting.
11 daysfrom the first test extract to production cutover
65 tablesrefreshed every night
4.6 millionrows in the full-history load
2 access tiersoperations data and owner financials, kept apart
The situation
The company ran ComputerEase for job cost, purchasing, inventory, AP, AR and the GL, and a separate CRM for sales, scheduling and field work. The two never talked. Reporting meant emailed report books and Excel exports, and automation meant software robots clicking through CE screens, because the ComputerEase API doesn't cover purchase orders, AP or the GL.
What we built
- A nightly extract on the CE server: 65 tables through a dedicated login that only reads, with payroll and every sensitive column left behind.
- A certificate-signed upload into a separate landing zone in Microsoft Fabric, then a checked load into two lakehouses: one for operations data and one for owner-level financials.
- Around 90 readable views that decode CE's cost types, voucher statuses and custom fields, and correct its known data problems.
- A Power BI job costing report that reads the lakehouse directly, shared to readers through an app with no database access.
- A purchasing agent that answers questions like "what's arriving this week?" from operations data only, and an executive agent with its own separate, audited access to the financials.
- Email and Teams alerts if a night's load fails or the data goes stale.
Where it stands
It runs every night in production with no one touching it. The job costing dashboard is live, and more agents are being built on the same foundation.