When NetSuite is your finance system of record, a careless HubSpot merge can do real damage. Billing history disappears. A company gets collapsed into the wrong record, and your finance team loses the NetSuite ID they rely on to process orders, invoices, or renewals. The tricky part is knowing which duplicates are safe to merge automatically and which ones need a human eye.
This is especially common when integrations like Apollo, ZoomInfo, or HubSpot forms keep creating new company records without checking what's already in your database. Over time, you end up with duplicates everywhere and with NetSuite in the mix, the cost of a bad merge is much higher than usual.
Koalify lets you handle this precisely. You can protect NetSuite-linked records from unsafe merges, automate the safe ones, and flag the sensitive ones for manual review. Here's how.
Before touching anything, establish one ground rule: any company with a NetSuite ID (or Customer ID) is a finance-critical record. That record should never be merged into a duplicate that doesn't share the same ID, or worse, merged with a completely different company that happens to have a similar name or domain.
In Koalify, this is handled through two settings: your duplicate rules (which control what gets flagged) and your primary rules (which control which record survives the merge). Both need to account for your NetSuite ID field.
✅ Action: DO NOT MERGE
If two records both have a NetSuite ID and those IDs are different, they are two distinct finance entities, regardless of how similar the company name or domain looks. Merging them would collapse two separate records into one, potentially deleting billing history, breaking the NetSuite sync, and misrepresenting the customer relationship in your reports.
💡 Edit your duplicate rules
Add a filter to every company duplicate rule:
NetSuite ID matches (or is unknown) NetSuite IDThis tells Koalify to only flag companies as duplicates when:
It will never flag two records with different NetSuite IDs as duplicates, no matter how similar they look.
Apply this filter to every rule in your company duplicate rules list. Each rule runs independently, so the filter needs to be present on all of them.
✅ Action: Merge — but keep the NetSuite record as primary
This is the most common scenario when integrations or HubSpot users create a new company record that partially overlaps with a customer already in your system. The new record has no NetSuite ID; the original does.
These are safe to merge — but only in the right direction. The company with the NetSuite ID must be the primary record. If the non-customer record becomes primary, you lose the NetSuite ID and everything connected to it.
💡 Edit your primary rules
Set your first priority in the company primary rule to:
NetSuite ID is knownThis ensures that whenever Koalify runs a merge, the record carrying the NetSuite ID is automatically designated as primary. The non-customer duplicate gets merged into it, and your finance sync stays intact.
You can then add secondary criteria for cases where neither record has an ID (see Scenario 3 below):
✅ Action: Merge — automate it
When neither duplicate has a NetSuite ID, there's no finance record at risk. These are typically duplicates created by enrichment tools, web forms, or manual data entry and they're safe to merge automatically via a HubSpot workflow.
💡 Set secondary primary rules
Since there's no NetSuite ID to guide the merge, use a combination of:
This handles the practical reality that historical company records sometimes have the wrong owner assigned, or were created before your current team took over. Prioritising the most active record with the most contacts gives you the best approximation of the "real" company.
For these records, you can safely enrol them in a Koalify workflow and let the merges run automatically in the background.
Once your rules are in place, here's the recommended approach:
It depends on which record becomes primary. If the record with the NetSuite ID survives the merge as the primary, the sync should remain intact. If you accidentally merge the NetSuite-linked record into a secondary, the ID may be lost. That's why setting the primary rule to prioritise NetSuite ID is known is essential before running any merges.
This usually means two genuinely separate billing entities have ended up sharing a name or domain in your CRM. Don't merge them — flag them for manual review and verify with your finance team before taking any action. Koalify's duplicate rules will prevent these from being flagged automatically once you've added the matches (or is unknown) filter.
Yes. Every merge run through a Koalify workflow is recorded in the workflow's enrolment history, and the merge is logged in the company record's activity timeline. You can also view the Merged Company IDs property on any primary record to see which records were consolidated into it.
All contacts associated with the non-primary record are re-associated with the primary record after the merge. You won't lose those relationships — they move over automatically.
If you're running HubSpot alongside NetSuite and want to get your duplicate rules set up correctly before running any merges, install Koalify free and book an onboarding call — we'll walk through your specific setup together.