Dataforma setup guide
Review credentials, connection steps and the first sync-rule workflow.
Connect two platforms, map your fields once, and let synkazo keep them in sync.

Keep HubSpot contacts and roofing workflows aligned with Dataforma—without duplicate entry, brittle automations, or a custom integration project.
It lands in HubSpot, and someone re-types it into Dataforma as a new client by hand. Every single time.
Dataforma knows. HubSpot never finds out — so marketing keeps sending “get a free roof inspection” to a customer whose roof you just replaced.
“Which ads actually brought in signed projects?” Nobody can answer, because the ad spend sits in HubSpot and the project revenue sits in Dataforma.
The tools are fine. They just don’t talk.
A lead captured once exists everywhere. At even 30 minutes a day of duplicate entry saved, the subscription pays for itself before any marketing benefit.
Completed projects flow into HubSpot, so your lists, workflows and follow-ups reflect reality instead of a snapshot from whenever someone last exported a CSV.
Project value lands on HubSpot deals — so HubSpot’s own reports can tell you which campaign, ad or referral source produced signed work, not just enquiries.
How A regional roofing and exterior services contractor put this connector to work.
Connector scope
These rows reflect the Dataforma qualification scope used for marketing and setup guidance. Exact HubSpot internal object names remain subject to the active project configuration.
| Field-service object | HubSpot object | Direction | Match key | Notes and qualifications |
|---|---|---|---|---|
| Contacts | Contacts | Dataforma → HubSpot | Email, then Dataforma contact ID | The Dataforma contact ID is stored in HubSpot for stable matching after the initial email lookup. |
| Customers | Companies | Dataforma → HubSpot | Dataforma customer ID | Customer identity is stored on the HubSpot company for repeat updates and associations. |
| Projects | Projects | Dataforma → HubSpot | Dataforma project ID | Uses the HubSpot Projects object with configured pipeline and status mappings. |
| AR invoices | Invoices | Dataforma → HubSpot | Dataforma invoice ID | Invoice associations and line-item behavior follow the approved project mapping. |
| Work Orders | Work Orders | Dataforma → HubSpot | Prefixed Dataforma work-order ID | Work orders use the approved WO-prefixed identifier and configured HubSpot destination properties. |
| Project Jobs | Work Orders | Dataforma → HubSpot | Prefixed Dataforma project-job ID | Project jobs use the approved PJ-prefixed identifier and configured HubSpot destination properties. |
Swipe horizontally to review all columns.
Four ways to connect Dataforma and HubSpot, plus ours. We’d rather you pick the right one than the one that pays us.
Approve access in one click from the marketplace listing or our install page.
Paste your API key and account subdomain once — they live under Admin → API Access, and we show you exactly where.
Start from our recommended mapping, adjust anything you want, then activate.
Continue evaluating
Review credentials, connection steps and the first sync-rule workflow.
Compare a maintained connector with Zapier-style workflows and other approaches.
See the documented problem, mapping approach and intended operational outcome.
Compare plan limits and prepare the questions needed for an accurate scope.