For specialty contractors and roll-ups

Several companies, one ERP, one set of numbers

Each company you bring in arrives with its own job numbers, cost codes and vendor list, on QuickBooks, Sage, Spectrum or Vista. Moving everyone onto one ERP breaks every report that relied on the old structure, and history ends up stranded in systems nobody wants to log into.

Viewpoint Vista
Trimble Spectrum
Sage 300 CRE
QuickBooks Online
Procore
Microsoft Fabric

Book a 30-minute call Send a short brief

Sound familiar?

Every acquired company codes cost differently, so group margin is a spreadsheet exercise.
Moving to one ERP strands job history in the old system, with no clean before-and-after comparison.
The board pack is assembled from a different export for each company, every month.

What we'd build first

1
A versioned old-to-new map for each company
Jobs, cost codes and vendors mapped from each old system to the target ERP as reference data, reconciled by job and cost code before cutover, using the same old-to-new cost-code mapping we run in production.
ERP migration data mapping
2
One cost-code standard the group agrees on
Projects, cost codes and vendors mapped once in versioned reference data, so every company reports the same way and gaps go back to the owner to fix.
Cost-code crosswalk
3
A portfolio view across every company
A portfolio page and a one-page executive KPI view that read every company through the maps, with drill-through from any project to its detail.
Executive portfolio dashboard

Who you'd work with

At Viewpoint, Nearmap, and Trimble, Charley connected ERPs (Viewpoint Vista and Spectrum most of all), schedules, cost systems, and field tools for contractors and owners across the country. Most recently, as an Integrations Engineer on Trimble App Xchange, he built connectors and MCP servers for Vista, ProjectSight, Accubid, PowerFab, and Trimble Connect. The information was almost always there. What teams lacked was a reliable path from that data to a report or action they could trust.