Migrate from BenchmarkONE to HubSpot

BenchmarkONE contact records migrate directly to HubSpot Contacts. The primary company association (Account Company ID) resolves to a HubSpot Company lookup; if no matching company exists, the contact lands without an association and your team confirms the link in HubSpot post-migration.

BenchmarkONE Temperature (Cold / Warm / Hot) maps to a HubSpot custom pick-list property named BenchmarkONE_Temperature__c. The HubSpot native lifecycle_stage is assigned based on a configured rule — for example, Warm and Hot map to 'lead' while records your team marks as active customers route to 'customer'. The original Temperature value is preserved as a reference field.

BenchmarkONE company records migrate directly to HubSpot Companies. We map company name, domain/website, industry, employee count, and annual revenue to HubSpot's standard company properties using their native field names. If your BenchmarkONE instance uses parent-child company hierarchies, those relationships transfer to HubSpot's Parent Company field, preserving organizational structure across the migration.

BenchmarkONE deals map to HubSpot Deals. Deal name, amount, and close date migrate as HubSpot dealname, amount, and closedate. The dealstage maps to a HubSpot deal stage within a named pipeline — we create the pipeline and stages in HubSpot to match BenchmarkONE's stage names before migration runs.

If BenchmarkONE uses a single flat deal list, HubSpot creates a single deal pipeline named 'Default Pipeline'. If multiple named deal categories exist in BenchmarkONE (e.g., New Business, Renewal), each becomes a separate named pipeline in HubSpot with its own stage sequence and probability weights.

BenchmarkONE tags on contacts and companies migrate as a HubSpot multi-value custom property named Tags__c. HubSpot does not have a native tag taxonomy — we store the full comma-separated tag list as a single string property so your team can reference the original tagging data and rebuild tagging logic as HubSpot lists or static lists.

BenchmarkONE email records (sent, opened, clicked) migrate as HubSpot Email engagements. All original metadata is preserved including timestamps, subject lines, and sender/recipient information. Each email engagement links back to its originating HubSpot Contact record through engagement associations, maintaining the complete communication history.

BenchmarkONE tasks and notes migrate as HubSpot Tasks with type='NOTE' for notes and type='CALL' or 'OTHER' for tasks. All original metadata transfers including completion dates, owner assignments, and body text content. Any tasks without a due date are imported without that property populated, ensuring no artificial data is introduced.

Every BenchmarkONE custom field on contacts and companies becomes a HubSpot custom property. We pre-create each property in your HubSpot portal (with the correct data type — text, number, date, checkbox, or pick-list) before the migration run, then map source values into the corresponding property names using BenchmarkONE's export column headers.

If BenchmarkONE has custom objects defined (e.g., Products, Projects), those map to HubSpot Custom Objects (available on HubSpot Professional and Enterprise). N:N associations between custom objects and contacts require HubSpot junction-object configurations — we surface these dependencies in the pre-migration schema plan.

BenchmarkONE's Assigned Sales Rep (user ID) resolves by email match against HubSpot user accounts. Unmatched owners are flagged before migration — your team either invites the user to HubSpot first or assigns their records to a fallback HubSpot owner. No record lands without a resolved owner.

BenchmarkONE's opt-in status maps to HubSpot's consent_to_communicate property. GDPR-style consent records are preserved as a boolean flag — if BenchmarkONE tracks individual consent categories (email, SMS, etc.), each becomes a separate HubSpot consent property to maintain granular communication permissions.

BenchmarkONE lead source values (e.g., Website, Referral, Trade Show) map to HubSpot's hs_analytics_source and hs_analytics_source_data_1 properties. We create a value-mapping table from the BenchmarkONE export so each source label lands in the correct HubSpot field with accurate attribution data.