Revit and Business Central Don't Talk to Each Other. Your Team Pays the Difference.

Your design team lives in Revit. Your operations team lives in Business Central. They're working on the same project. They're rarely working from the same data.

This isn't a technology problem. It's a structural one. Two specialized systems, built for fundamentally different purposes, with no native connection between them. And in the gap between those two systems, somewhere between the last model save and the next procurement run, things go wrong.

Two Systems, Two Realities

Revit thinks in elements, assemblies, and geometric properties. It knows about walls and their layers, doors and their hardware, structural members and their connections. Business Central thinks in items, SKUs, costs, and availability. It knows about inventory, supplier lead times, purchase orders, and project budgets.

These two systems need each other's data constantly. And yet, at most companies, that data exchange happens through email, spreadsheets, and manual copy-pasting.

The Questions Nobody Can Answer Quickly

When a design changes, who updates the ERP? When a material is out of stock, does the designer know before committing to a specification? When a change order comes in, which system gets updated first — and which one ends up out of sync?

At most companies, the answer to these questions involves someone making a phone call, sending an email, or opening a spreadsheet and hoping it's the current version. That's not a workflow. That's a series of manual interventions, each one a potential point of failure.

The Real Cost Is the Reconciliation

The most visible cost is the manual work: a project manager or administrator spending hours bridging the two systems. Exporting from Revit, reformatting in Excel, importing into Business Central, then checking for discrepancies. They're not adding value — they're translating. And they're one mistake away from a discrepancy that takes twice as long to find as it does to fix.

The less visible cost is the decisions made on stale data. Change orders that aren't reflected in procurement. Material costs that don't feed back into design decisions. Project milestones tracked in one system, billing running in another. The gap between what the model says and what the ERP knows grows quietly, project by project.

Why It Doesn't Get Fixed

Most companies accept this as the cost of using specialized tools. "We've always done it this way." The workarounds become institutional. New team members inherit the spreadsheets and the process, and the inefficiency becomes invisible because it's been normalized.

But the gap isn't shrinking. As BIM models get more complex and ERP implementations get deeper, the translation effort grows. More data, more fields, more revisions, more chances for the two systems to diverge.

The Uncomfortable Question

What's the last decision your operations team made based on data that was already outdated the moment the designer saved the model?

If you don't know — or if you'd rather not find out — that's the gap you're living with.