Migrate from Net-Results to HubSpot

Net-Results workflows and scoring rules do not migrate and require complete rebuild in HubSpot

Net-Results stores workflow logic — drip sequences, if-then routing rules, lead scoring models, and behavioral triggers — as platform configuration that defines how contacts move through campaigns. This logic has no HubSpot equivalent in the data layer. HubSpot workflows are defined using the Workflows tool (for CRM record changes) and Campaigns (for marketing sequences), both of which require manual rebuild. We can export your Net-Results workflow definitions as documentation to hand to your HubSpot admin for rebuilding, but the automation logic itself cannot be transferred automatically. This is the most significant manual effort item in any Net-Results to HubSpot migration and should be scoped separately from the data migration.

Campaign membership imports require all contacts to exist in HubSpot first

Net-Results campaigns have member associations linking contacts to specific campaigns with engagement history (opens, clicks, bounces). HubSpot's campaign model works the same way — contacts must exist before they can be added as campaign members. This creates a migration sequencing dependency: contacts migrate first, then companies, then deals, then campaigns with their member associations. If your Net-Results account has a high ratio of campaign members to direct contacts (contacts enrolled in multiple campaigns), the campaign import phase adds proportionally to the migration timeline. We flag any orphaned campaign members (contacts that no longer exist in Net-Results) before the import runs so you can decide whether to exclude them or create stub records.

HubSpot lifecycle stage is required for contact reporting but has no direct Net-Results equivalent

HubSpot uses lifecyclestage as a mandatory property for native reporting and automation triggers — contacts without a lifecycle stage value cannot be properly segmented in HubSpot lists or used in lifecycle-based workflows. Net-Results does not enforce a comparable contact stage property across all records. During migration, we map Net-Results contact status or campaign membership data to HubSpot lifecycle_stage values using value mapping rules you define (e.g., contacts who opened any email become 'lead', contacts who converted on a form become 'MQL'). If Net-Results data does not contain enough context to infer lifecycle stages, all contacts land as 'subscriber' by default and the rest must be set via HubSpot workflows post-migration — this is a decision point your team needs to make before migration runs.

Net-Results API rate limits may extend extraction time for large datasets

Net-Results exposes a JSON API for data extraction, but the platform applies rate limits on API calls that govern how quickly data can be pulled. For migrations with more than 100,000 records across contacts, companies, deals, and campaign memberships, API rate limiting can extend the extraction phase from hours to a day or more depending on your Net-Results plan tier. We use paginated API requests with exponential backoff to stay within Net-Results' rate limit thresholds, but this adds overhead that factors into the overall migration timeline. We surface the extraction rate in the discovery phase and adjust the migration schedule accordingly if rate limits are tighter than expected.

Custom property type mismatches require pre-migration HubSpot configuration

Net-Results custom fields store data types (text, number, date, dropdown, checkbox) that must map to HubSpot property types exactly. HubSpot's property type system is stricter — a number field cannot accept text values, and enumeration fields require the exact option labels to be present in HubSpot before import. If your Net-Results account uses custom fields with mixed-type data (e.g., a number field containing occasional text values), those records require data cleaning before import or HubSpot custom properties must be configured as text to accept all values. We audit Net-Results custom field data types and values during discovery and either clean the data or configure HubSpot properties with the correct type before migration runs.