Preconstruction and Pursuit Stay in HubSpot
The relationship, bid activity, proposal, follow-up cadence, and anything tied to deciding whether to pursue a job in the first place.
Viewpoint Vista is built around job cost accounting: a Job Code, its phases, its cost types, and the contract tied to it carry the data. HubSpot is built around companies, contacts, and deals. A HubSpot Vista Integration lives or dies on how those two models get reconciled.
Vista has no HubSpot-built connector and no listing on HubSpot’s App Marketplace. Vista’s data sits in a SQL Server database with no open or free API, so a HubSpot Vista integration is either a direct SQL connection or a build against Trimble’s optional Xchange Direct API, where it’s been provisioned.
HubSpot’s deal object assumes a single-moment outcome: a deal is open, then it’s won or lost. Vista’s Job Cost module assumes something longer-lived: a Job Code that stays open from award through closeout, often for months or years, accumulating phases, cost types, change orders, and billing against a contract the whole time.
The two don’t line up cleanly, and this is where most HubSpot Vista integrations get stuck. A deal represents the pursuit: the bid, proposal, and relationship being worked before anyone signs anything. A job represents the work: the Job Code, phases, cost types, and contract Vista creates the moment that Job Code is set up.
The fix most of our construction clients land on isn’t syncing the deal into the job continuously. It’s recognizing that a deal and a job are two different stages of the same pursuit, with a single handoff point between them, not a two-way mirror running the whole project.
Vista has its own Bid Management capability for soliciting and comparing bids before a job exists. Once a bid is won, setting up the Job Code in JC Jobs automatically creates the matching contract behind it. That moment, when bid becomes job, is the one point where HubSpot and Vista need to agree.
Before that point, the pursuit lives in HubSpot: the deal, contacts, proposal activity, and follow-up. After that point, the job lives in Vista: cost, billing, payroll, change orders, and closeout. The handoff is usually the only sync that has to happen in real time. Everything after it is just job cost reporting flowing back to HubSpot for visibility.
The Job Code is set up in JC Jobs, and Vista automatically creates the matching contract behind it.
Don’t try to make HubSpot and Vista mirror each other completely.
The relationship, bid activity, proposal, follow-up cadence, and anything tied to deciding whether to pursue a job in the first place.
A rep or account manager in HubSpot needs to know where a job stands (on budget, behind, closed out) without needing every cost-type line that got it there. Syncing summary job status back on a custom object in HubSpot tends to hold up well.
Budget, committed cost, change orders, payroll, equipment charges, and billing. This is system-of-record territory, and trying to make HubSpot a second source of truth for it usually creates more work than it saves.
As a HubSpot Elite Solutions Partner built around industrial, manufacturing, and construction companies, we scope Vista integrations through the Industrial Growth System: strategy first, then people, then process, then technology, so we’re drawing this line based on how your team actually works, not how much data happens to be technically reachable.
Explore the Industrial Growth SystemThere are three ways to connect HubSpot and Vista: direct SQL server connection, Trimble Xchange direct API, or iPaaS/integration platform.
| Direct SQL Server Connection | Trimble Xchange Direct API | iPaaS / Integration Platform | |
|---|---|---|---|
| Best For | Companies without Xchange provisioned, comfortable maintaining a custom sync against Vista’s supported views | Companies that already have (or can get) Xchange provisioned and want an HTTP layer instead of raw database access | Companies wanting a managed, ongoing sync without owning the build directly |
| Pros | Available on virtually every Vista install; no separate Trimble feature to request | A more standard integration surface than raw SQL; built and supported by Trimble | Vendor-managed; broader library of prebuilt actions across systems |
| Cons | Must be built against Vista’s views and stored procedures, not raw tables, or it risks breaking on upgrade; requires direct database/network access | Not every Vista install has it, and provisioning goes through Trimble support, not self-service | Ongoing subscription; still has to account for the job-to-deal mapping problem manually |
| Our Take | The most common path today, and reliable when built against the right surface | Worth pricing out if you’re cloud-hosted and want a supported surface instead of a direct database dependency. Not a fit when the handoff has to happen the moment a deal closes, since the API reads from a cache rather than Vista itself. | Reasonable if Vista is one of several systems in your stack, not the only integration you’re managing |
Everything above is what shapes the pitch and the budget. Everything here is what your Vista admin or IT contact will actually be asked to confirm or provision before build work starts. Forward it to them directly, or walk through it together on our Integration Readiness Check.
Vista’s database is Microsoft SQL Server, which is both the easiest and riskiest part of integrating with it. Vista doesn’t expose a free or open API on its own. Direct SQL Server access is common, and for a lot of Vista shops, it’s more available than the equivalent access on most other ERPs, since there’s no separate API license to negotiate first.
The catch is that Vista’s own integrations, including the Xchange Agent Trimble uses for its first-party connections, are built to go through Vista’s supported views and stored procedures, not raw tables. A custom sync built against raw SQL tables instead of those views can work fine today and then break the next time Vista is upgraded, because nothing obligates Trimble to keep an undocumented table structure stable across versions.
Where it’s provisioned, Trimble’s Xchange Direct API offers an HTTP layer instead of a raw database connection. There are two things to know before you plan around it. It’s a paid add-on, sold to Trimble Construction One cloud-hosted Vista customers, not a feature you toggle on. And it doesn’t read your Vista instance directly: calls go to App Xchange, which holds a cached copy of your Vista data, refreshed on a schedule, with write actions queued. That’s a supported, documented surface, which direct SQL is not. It’s also not real time, which direct SQL is.
On an on-premises install, a custom integration typically connects directly to your SQL Server over your own network, the way any internal reporting tool would.
On a hosted deployment (Vista SaaS, Viewpoint Enterprise Cloud, Trimble Construction One, Viewpoint One), your database lives on Trimble’s Azure infrastructure. Third-party access runs over a TLS Database Endpoint, a TLS-encrypted connection protected by IP whitelisting, set up through a cloud support ticket. You’ll need a static, public IP on the connecting side. Trimble requires one whether you’re on the TLS Database Endpoint or IPSEC, with no workaround for lacking one.
Two things to plan around: a static IP can only be whitelisted for one customer environment, so the same gateway IP can’t cover both a client’s test and production environments, and Trimble adds a non-negotiable VPN fee to TC1/Viewpoint One contracts that applies to both the TLS endpoint and IPSEC.
Neither path is harder in an absolute sense, but they’re different projects. Confirming which one you’re on, and who has the authority to request IP whitelisting or Xchange provisioning on Trimble’s side, is worth doing before anyone quotes integration work.
Viewpoint Vista is Trimble's construction ERP for job cost accounting, payroll, equipment, and service management, built for general contractors and specialty trades. It's part of the Trimble Construction One suite, alongside Spectrum, a separate cloud-native product aimed at a different segment of contractors.
Not through a connector either company built. Vista has no listing on HubSpot's App Marketplace, so a HubSpot Vista integration is built either directly against Vista's SQL Server database or against Trimble's optional Xchange Direct API, where it's provisioned.
Not cleanly. A deal represents the pursuit of work before it's won. A job represents the work itself once a Job Code is set up in Vista, which also automatically creates the job's contract. Most integrations treat the handoff from deal to job as a single sync point rather than trying to keep the two in continuous lockstep.
Not a standard one. Vista's database is SQL Server, and most integrations connect to it directly. Trimble's Xchange Direct API is an optional HTTP layer some subscribers have provisioned on top of that database, but it isn't available or enabled by default.
Yes, if it's built against Vista's own supported views and stored procedures rather than raw tables. Vista's own first-party integrations use this same approach. A sync built against raw tables instead can work today and break on the next Vista upgrade.
Yes. On-premises, a custom integration typically connects directly to your network. On hosted Vista (Vista SaaS, Viewpoint Enterprise Cloud, or similar), your database lives on Trimble's Azure infrastructure, and a third-party integration needs its IP addresses whitelisted through a Trimble support request before it can connect.
Job status and summary cost position tend to hold up well. Full job cost detail, payroll, and change order line items generally aren't worth mirroring into HubSpot. They belong in Vista, and attempting to sync everything bidirectionally is the most common way Vista integrations become unsustainable.
It depends heavily on whether Xchange is already provisioned, whether the build goes against raw SQL or Xchange, and how much job cost detail the client wants synced beyond status. A build scoped to the bid-to-job handoff and status sync is a meaningfully smaller project than one trying to mirror full job cost detail.
Cost depends on whether Xchange is provisioned, how much of the job cost model needs to surface in HubSpot, and whether the build has to account for hosted Vista's IP whitelisting process.
Before you scope a Vista integration, find out whether Xchange is already provisioned, what your job-to-deal handoff actually needs to look like, and which side of hosted versus on-premises you’re on. Our ERP Integration Readiness Check starts with those questions.