Migrate from Data Team DDS to HubSpot

HubSpot lifecycle_stage requires value remapping for non-standard source values

HubSpot's lifecycle_stage property accepts only a specific set of values: subscriber, lead, MQL, SQL, opportunity, customer, evangelist. If Data Team DDS uses different stage labels (for example, prospect, qualified, booked), those values cannot land directly in HubSpot's lifecycle_stage property — they will be rejected or default to blank. FlitStack AI preserves the original stage label in a custom property (original_lifecycle_label) and surfaces a value-mapping plan so your team can decide how to collapse or re-label stages before the full migration runs.

HubSpot auto-associates contacts to companies by domain — may override explicit associations

When HubSpot processes a new contact record with an email address whose domain matches a HubSpot Company, HubSpot automatically links that contact to the company regardless of any explicit company_id field in the import. This means contacts from Data Team DDS that are explicitly associated with one company may be re-associated to a different company based on email domain matching. To prevent this, we disable HubSpot's domain-based company auto-association before the migration import runs, then re-enable it post-migration. This ensures the company association you specify in the migration plan is preserved.

Deal pipelines must exist in HubSpot before deals can reference them

HubSpot's Deal object requires a valid pipeline ID for every deal record. If the source system groups deals into named pipelines or stages, those groupings must be pre-created as HubSpot Deal Pipelines before the migration inserts any deal records — otherwise deal insertion fails. FlitStack AI generates a HubSpot pipeline setup plan (pipeline names, stage labels, stage probabilities, and display order) as part of the migration package. Your HubSpot admin creates the pipelines, or we can create them on your behalf, before the data migration begins.

Custom objects with N:N relationships require HubSpot custom association types

Data Team DDS may support many-to-many relationships between custom objects (for example, a custom Project object linked to multiple custom Invoice records). HubSpot's standard association model supports N:N between Contacts and Companies and between Deals and Contacts, but custom object N:N relationships require HubSpot Custom Association Types (available on Professional and Enterprise). We define the required association types in the migration plan, but creating them requires HubSpot admin credentials and may require a brief HubSpot product limitation review for edge-case relationship types.

HubSpot creates a new contact on each import if email is not treated as a unique key

HubSpot's Contacts API treats each import row as a new contact unless a unique identifier or email deduplication setting directs it to update an existing record. FlitStack AI uses a two-pass approach: first, we identify existing contacts in HubSpot by email or by matching the source system's record ID stored in the dds_record_id property. On the second pass, matched records are updated in place and unmatched records are inserted as new. If your Data Team DDS data contains duplicate contact records (same email, different IDs), these will surface as duplicates in HubSpot post-migration and will need a deduplication step.