NetSuite…2-Way Sync!

Posted by: Bri Guarnieri Date Posted: November 21, 2025
Back to Case Studies

Issue

NetSuite integrations are challenging…and this was my first one! I didn’t know what to expect & definitely like I had to explore NetSuite a bit [there’s tons of data and objects within it]. Additionally, Alejandro had never sent attribution data to NetSuite, so this was a first!

Throughout our project, we had to tackle the following:

  1. Instances of MANY contacts associated with a contract in NetSuite.
  2. Identifying via the API how to distinguish between a rental and a sale contract, as we need to report on these separately for the client [no field accessible via the API].
  3. On rentals, we needed the client to create a custom field that calculated the rental revenue value, as there were 3 fields that made up rental revenue prior.
  4. Different contact objects in NetSuite that refer to the same person, resulting in duplicate RCFX contacts.
  5. The contact stage mapper was fighting against the deal stage mapper.

Solution

This integration had a lot to it, as we looked to pull in custom fields, pull in revenue, update contact stages from the lead object, create deals from the contract object, and send data back to the contact in NetSuite. As a result, we broke the integration into 3 phases to ensure we weren’t biting off more than we could chew!

  • Phase 1: Getting contracts & revenue into RCFX!
  • Phase 2: Updating contacts in RCFX earlier on in the funnel (leads).
  • Phase 3: The 2-way sync – sending data from RCFX into NetSuite.

Personally, I think this helped Alejandro and I, as we completed/Q&A’d the integration AND it helped with my communication to the client. ‘Completing phases’ sounds more appealing, in my opinion, and makes it feel like something has been achieved, even when we’re only 1/3 of the way there.

Now, how did we tackle the issues outlined above?

  1. Instances of MANY contacts associated with a contract in NetSuite.
    1. We tried to do logic where we could identify a B2B vs B2C sale and base the number of contacts off of that…but we couldn’t find the field we needed for that. Instead, we capped the number of contacts at 5, which seems to be working well for us for now! It’s not perfect but it yields the result that we need for now (we can always revisit later if we think it’s a problem). 
  2. Identifying via the API how to distinguish between a rental and a sale contract, as we need to report on these separately for the client [no field accessible via the API].
    1. This took trial and error, but there was a hidden API field that Alejandro was able to identify after we pulled a few sample contacts for review/cross-reference! 
  3. On rentals, we needed the client to create a custom field that calculated the rental revenue value, as there were 3 fields that made up rental revenue prior.
    1. The client’s NetSuite guy had to put in some work for us! He created a custom, calculated field & ran a backfill, so we could get historical data. 
    2. This field also ended up being a win for the client… they realized that they should probably have that anyway – now they don’t have to reference 3 fields on rentals! 
  4. Different contact objects in NetSuite that refer to the same person, resulting in duplicate RCFX contacts.
    1. This was an interesting issue! I think there are contacts and customers in NetSuite, which are essentially the exact same thing BUT they have different contact IDs, so Bri would be 123 & 234, but still be the same person. As a result of that, we had duplicate contacts in RCFX – which was causing issues with deal attribution. We decided that we would not map the external contact ID to help resolve the issue. 
  5. The contact stage mapper was fighting against the deal stage mapper.
    1. The contact stage mapper automations for ‘churned’ & ‘mql’ that we were identifying at the lead level were overriding our deal stage mapper automations. Essentially, if someone had a closed won deal now & then two months from now submitted a new inquiry, it was reverting a customer contact stage back to mql, which we don’t want. 
    2. Alejandro coordinated with R&D and determined this is a client-wide issue with the mapper, so we had to figure out an interim solution. We went with manually setting the automations through the integration in Workato. 

Overall, we conquered a lot! We had a number of hurdles & lots of testing to get to where we are now, but we did it & the client began reporting on revenue by the second report – what a win!

Achievement

We are logging sales data from NetSuite in RevenueCloudFX, and we are sending attribution data to NetSuite to help with the clients internal reporting [this was a BIG win & the client is pumped]!

Snippet/Screenshot/Link