We are using the official HubSpot-built data sync integration for the Swiss accounting software bexio.
For several weeks, the sync has been failing or did not go thorugh correctly for many of our company and contact records. We have identified the root cause: bexio has changed its address format to comply with new Swiss financial regulations (QR-bills), but the HubSpot integration has not been updated yet.
The Problem:
bexio (New): Now uses four separate, structured fields for addresses: Street, House Number
HubSpot (Current): Still uses a single, unstructured Address field.
The integration is unable to map the single HubSpot field to the four separate fields in bexio, which causes the synchronization to fail. This is a critical issue for our invoicing and accounting workflow.
Here is the official announcement from bexio detailing the mandatory change: helpcenter
Since this is an official integration developed and maintained by HubSpot, we urgently request that your development team updates the app to support bexio’s new structured address fields.
Could you please provide information on whether this is on your roadmap and when we can expect a fix?
Hi @GF23,
Thank you for posting to the Community!
I’d like to tag in a Hubspotter from the Product team to see if this is expected behavior.
Hi @FransLeys! Hope your having a great Friday. Do you have any ideas on this one?
Cassie, Community Manager
You’re right to flag this one as critical. At the moment HubSpot’s Data Sync for bexio hasn’t been updated to handle the new structured address fields (Street, House Number, etc.), and because HubSpot only stores a single unstructured address field, the mapping fails. That explains why your sync is breaking.
The only native workaround right now is to either:
Flatten bexio’s address fields into a single text field before they reach HubSpot (via a middleware like Make/Zapier).
Or, store the four fields in custom HubSpot properties and adjust your workflows/reports accordingly until HubSpot updates the official connector.
HubSpot’s documentation on custom properties and data sync limitations has some context on why the mapping breaks.
And just as a side note, some teams that hit this kind of mismatch between systems lean on Stacksync since it handles real-time two-way sync with field-level mapping flexibility you don’t get blocked when one platform changes its schema, because you can transform fields on the fly.
Thanks a lot for your quick and helpful reply.
I’ll review the suggested workarounds and see if we can bridge this in the short term with a middleware solution.
That said, I really hope HubSpot will update the official connector soon, since this is such a critical integration for our workflow.
Sorry for this belated reply - I was out on parental leave.
We actually migrated/implemented towards the new address type well before their announcement - so it is peculiar you are still suffering issues. Maybe your connection did not get migrated yet?
What are the exact errors you are getting?
I can confirm that Bexio --> Hubspot works now.
In our process, however, we use Hubspot as our single source of truth and maintain the data accordingly in this system. Address data synchronization from Hubspot to Bexio does not work for us (yet?). Has this also been fixed or is it still to come?
bexio now offers the following street address fields:
address (read-only), which contains the full street address as one field.
address is a combination of the following fields:
street_name (read-write, contains only the street name)
house_number (read-write, contains the house number)
address_addition (read-write, contains any extra address information)
It’s not possible on our end to combine the three read-write fields (street_name, house_number, address_addition) into a single read-write field for address to just make it magically work within a default field mapping.
The HubSpot schemas and Bexio schemas just dont align nicely anymore and it looks like it can only be fixed if e.g. on the HubSpot side you create custom fields for those house numbers and address additions. And then custom map them.
Solution would be:
The default Address mapping syncs the address field (full address) one-way only.
The “Address (Street Name)” mapping syncs only the street_name field—no house number or additional info. This is not enabled by default, but can be set up with a custom mapping -- this requires Operations Hub Starter.
Likewise, you can set up custom mappings for Address (House Number) and Address (Addition) if you wish -- this also requires Operations Hub Starter