Migrate from Dashcord to HubSpot

Dashcord lifecycle stages require value-by-value mapping to HubSpot lifecycle_stage

Dashcord stores lifecycle stage as a custom Salesforce pick-list field on Contact with values the organization defined. HubSpot's lifecycle_stage has a fixed set of values (subscriber, lead, MQL, SQL, opportunity, customer). Non-standard Dashcord stage names have no automatic HubSpot equivalent — we create a custom contact property named Dashcord_Lifecycle_Stage__c and map each value to the nearest HubSpot standard or preserve it as-is in the custom property. The mapping plan must be reviewed and approved before migration runs.

Salesforce-to-HubSpot API migration requires email-based de-duplication across both platforms

Dashcord data lives in Salesforce, which may already contain contacts also present in HubSpot from a prior implementation. Our migration runs email-matching against existing HubSpot contacts before inserting — contacts with matching emails update the existing HubSpot record rather than creating duplicates. Contacts with no HubSpot match insert as new records. This prevents the double-contact problem where the same person appears twice in HubSpot post-migration. We apply case-insensitive email matching and optionally use secondary fields such as phone number or company domain to resolve ambiguous cases. The deduplication report lists every match and update, allowing your team to review before finalization.

Dashcord event registrations stored as Salesforce custom objects have no native HubSpot equivalent

Dashcord event data — registration date, attendee status, session selections, dietary requirements — lives as a custom Salesforce object with a relationship to Contact. HubSpot has no native event-registration object. We create a HubSpot custom object named 'Event Registration' with fields mapped from the Salesforce custom object schema. The relationship to HubSpot contacts is preserved via email matching. Post-migration, your team decides whether to continue using the custom object or migrate to a dedicated event platform like Luma or Eventbrite with HubSpot integration.

Dashcord lead scores normalized to HubSpot scale require admin calibration

Dashcord lead scores in Salesforce may use any numeric range the organization configured (0-10, 0-100, 1-5 with decimals). HubSpot's native HubSpot Score also uses a range (typically -100 to +100). We map Dashcord scores to HubSpot's scale proportionally — a Dashcord score of 100 does not become a HubSpot score of 100. Your HubSpot admin should review the mapping formula and set threshold values for lead-status workflows after migration. If your organization uses tiered lead scoring, we can create a custom numeric property to preserve the original granularity while still exposing the normalized score to HubSpot's native scoring engine.

Salesforce API rate limits apply during extraction from Dashcord's host org

Dashcord stores data in Salesforce, so extraction uses Salesforce's Bulk API or REST API subject to Salesforce's daily API request limits. Large Salesforce orgs with active users during extraction may hit governor limits or experience throttling. We batch extraction to stay within limits and re-attempt failed batches. The Salesforce admin may need to request a temporary limit increase for the migration window. We monitor API usage in real time using Salesforce's REST API logs, adjusting batch sizes dynamically to avoid hitting limits. If a batch fails due to a limit breach, we automatically retry after a short back‑off period, ensuring a smooth extraction even during peak usage.