@MDiaz705 welcome to the community.
Dealing with dual CRMs during a migration is tricky, and without dev support, it’s even more critical to find a clean workaround that won’t break data or waste ops time.
Your idea to store HubSpot Record IDs in NetSuite and map them back for mass updates is solid. It’s a workaround we’ve seen work well for teams who are still bridging between legacy and new systems without needing developers.
Here’s how you can do it without breaking your back or hiring custom code:
1. In HubSpot, use a workflow to copy the Company Record ID
into a custom property (e.g., hubspot_record_id
) so it’s available for syncing.
2. Create a corresponding custom field in NetSuite to receive that HubSpot ID (make sure it’s set to external ID if you want to map back easily).
3. In your iPaaS (if you use one) or CSV export/import cycle, pull reports from NetSuite including this HubSpot ID field, so you can match it back to existing companies.
4. On HubSpot’s side, import updates using that ID as a matching key, not email or domain—avoids mismatches.
5. If you’re using Operations Hub Pro/Enterprise, consider setting up a data sync but disable create/new record so you avoid duplication during this phase.
P.S. We actually built StackSync for exactly this kind of migration pain—real-time, two-way sync between HubSpot and NetSuite, with ID tracking and mapping handled automatically. It can track custom associations, sync millions of records in seconds, and even trigger workflows from field changes.
If you go that route, we support intermediate database setups to bridge differing models between CRMs and ERPs (NetSuite tends to be opinionated with customer records).
Hope this helps.