I would like to create a mapping between the Lifecycle Stage field in Hubspot and the Status field in Netsuite for my companies, but the Status field doesn't show up in the list when I try to create a mapping. Does anyone have any experience with this?
Hello! Yes, we use this integration, and I found a workaround for the Lifecycle stage! It's a bit complicated, but it does work.
So first, I edited all of the Lifecycle statuses in Hubspot to match the same names we use in Netsuite. (Ex. PROSPECT-Qualified Prospect and so on). You can edit the names of the Lifecycle stages in Hubspot, adding however many that are needed.
Next, I created a custom single-line text mapping from the Lifecycle stage in Netsuite to Hubspot and named it "LS Stage (NS)". We only use this on the Company (Customer in NS), so I only mapped on the Company sync.
I then created a Company based workflow for each Lifecycle Stage to map the single-line text to the radio select in Hubspot. Here are the different workflows mapping each of the Lifecycle statuses:
Here is a breakdown of one of the workflows. I basically created one workflow and then copied the rest, updating to the next status:
The thing to note is that we use this on the Company (Customer) level only in Netsuite. So for us, we rely on the native setting "Copy Lifecycle status to Customer" to update the contacts based on the customer stage. This only works in one direction, so if you ever change your customers from the stage Customer back to a Prospect at any point in Netsuite, you will have to create a reverse workflow to change it back in Hubspot. It wasn't a difficult workflow to set up, but since it is something we frequently do, it was necessary for us.
Happy to answer any other questions you may have! This took a lot of troubleshooting to get here, but it does work perfectly for us now.
Yes, Operations Hub Starter is required for custom fields.
Now, let's define what custom vs default fields mean for Data Sync apps (i.e. NetSuite).
Default fields in NetSuite are fields such as first name, last name, and email.
It has a specific definition:
It must be a default field in NetSuite
It must be a default field in HubSpot
It must be consistently mapped, with little room for debate.
Fields that fit this for example on the contact record are first name, last name, and email. There maybe a handful more. These are available for free with Operations Hub Free.
Custom field mappings are everything else.
Take the HubSpot lifecycle stage field - that's default in HubSpot, but you could map it to NetSuite Status (default) or to a custom NetSuite Lifecycle stage field. Because there's an element of user choice in this, we wouldn't consider it default and you'd need to upgrade to Operations Hub Starter to have access.
Clarification point - Dropdown select, radio buttons, and checkboxes are not considered "custom field mappings". These mappings are a type of field mapping. We’re still working hard on adding support for all dropdown fields.
Recommendation: Check the fields you need are available before you upgrade to Operations Hub Starter+. You can create a developer test account that gives you access to the full tiers for testing. An alternative chatting with your sales rep about trialing Operations Hub Starter before you commit.
Hope that helps! I can give general guidance, but a question like “does X field map in the integration” is best done by trying it out. The install flow is pretty quick!
Hello! Yes, we use this integration, and I found a workaround for the Lifecycle stage! It's a bit complicated, but it does work.
So first, I edited all of the Lifecycle statuses in Hubspot to match the same names we use in Netsuite. (Ex. PROSPECT-Qualified Prospect and so on). You can edit the names of the Lifecycle stages in Hubspot, adding however many that are needed.
Next, I created a custom single-line text mapping from the Lifecycle stage in Netsuite to Hubspot and named it "LS Stage (NS)". We only use this on the Company (Customer in NS), so I only mapped on the Company sync.
I then created a Company based workflow for each Lifecycle Stage to map the single-line text to the radio select in Hubspot. Here are the different workflows mapping each of the Lifecycle statuses:
Here is a breakdown of one of the workflows. I basically created one workflow and then copied the rest, updating to the next status:
The thing to note is that we use this on the Company (Customer) level only in Netsuite. So for us, we rely on the native setting "Copy Lifecycle status to Customer" to update the contacts based on the customer stage. This only works in one direction, so if you ever change your customers from the stage Customer back to a Prospect at any point in Netsuite, you will have to create a reverse workflow to change it back in Hubspot. It wasn't a difficult workflow to set up, but since it is something we frequently do, it was necessary for us.
Happy to answer any other questions you may have! This took a lot of troubleshooting to get here, but it does work perfectly for us now.
Thank you for the detailed answer, but in our company Hubspot is the source of truth, so therefore the lifecycle stage should migrate from Hubspot to Netsuite, not the other way around.