I would like to have the ability to create multi-language property names for internal use.
My company database is entirely in English and my Dev, Product, Data and other more technical users prefer to use HubSpot in English as well.
However, Sales, Customer Success, Collection, and Customer Experience teams prefer to use HubSpot in Portuguese (our country's main language).
HubSpot default properties usually are translated from English to Portuguese, but we use a lot of custom properties because of our business needs and in these properties, we can't auto-translate based on our employee's HubSpot language. This generates a little friction because technical users want our CRM property naming like our database (English) and operational users want our CRM property naming in our country's language.
If a could manually insert the default property name (English) and the translated one (Portuguese) this problem would be solved.
Hi everyone - another quick update - it is now possible to import .XLSX (Excel) files when using the beta Translate custom CRM data. The goal of this change is to reduce the likelihood of errors when importing (e.g. encoding issues).
Also, this feature now supports custom properties including custom pipeline and pipeline stages, as well as custom object labels.
Hi everyone - a quick update - Enterprise customers can now opt into the beta: Translate custom CRM data directly via Product Updates (no need to request via a Customer Success Manager).
Hi all! There should be a CSAT survey in-app for beta users where you can leave feedback. Another way to provide feedback is to communicate to your CSM, who can pass feedback to my team diectly. If you are in the beta and have a pressing question or issue, please reach out to the Support team, that is the fastest way to get issues resolved.
Pipeline stage properties translations (including lifecycle stage) are not yet included in the beta. Additionally, this beta will only impact pipeline stages that can be edited (it will not impact any translations of default pipeline stages provided by HubSpot that cannot be customized).
👋 Hello! I'm Rachel from the HubSpot Product team. Sharing an update - we have a beta in its early stages called Translate custom CRM data. In the current stage of the beta, you can create translations for custom properties, excluding custom pipeline and custom pipeline stage translations. During the beta, the ability to translate other custom data such as custom pipeline and pipeline stages will be added.
This is an Enterprise feature. To learn more details, or to join the beta, please contact your Customer Success Manager so they can request beta access on your behalf.
Critical for us to. 90% of our used properties are custom making the user language fairly meaningless with the exception of menu's
This needs to be an area upon property editing or creating where you can manually set a translation for each language as required, this should tie into the user preferences i.e if a user sets default to German it will use the German label of all custom properties.
This is essential for companies with Eurpean and global operations.
Following on from this I have mocked up what a potential solution could look like to meet the user case to help HubSpot visualise how this could work. Take a look here:
Critical for multi language like the original poster mentions and for global business looking to utilise a single portal
The current workarounds on offer are:
- Clone all properties and rename to different language (We have custom properties in the 100's we also have complex integrations and API routines meaning this is unworkabel)
- Add the translation into the label i.e. "Customer Type / Kundentyp" however for companies using more than 2 languages this becomes unworkable
- Add the translation into the field description (this unfairly causes friction for other languages outside of your companies default, our German businesses would be at a disadvantage)
Therefore i believe the only solution is to create this new functionality
Hi, it will be very helpful if we can use multi-language property for personalised token in marketing email. So we can really localise for different market:)
General Translation functionality is also an upgrade for dependent field functionality in hubspot forms. Currently it is not possible to change the object's property label for the dependent field in the form (expect you override the label directly in the object). There must be a differentiation between customers language and employees/users language.
Agree! Having a language variation of custom properties rather than having to clone all custom properties and create new views would be extremely beneficial. This would also be very useful for client communication. Now, when we are creating a workflow that uses a property to send communication to a client, we have to essentially double the work by having to remember the names of all properties that are the same thing but in multiple languages (difficult when some of our team only speaks one of those) and then add them all to the trigger. Would prefer a solution that allows us to add one property, which would, in turn add all of it's variations to the trigger.
Being a company having users in several countries, we 'ld also appreciate having multilanguage property labels as we do experience language barrier issues using HubSpot.
