Migrate from Data Team DDS to Salesforce Sales Cloud

Direct 1:1 map for contacts that route to the Contact object. Salesforce requires AccountId for most contact operations — contacts without a primary company in the source land on a default 'Unassigned' Account or are flagged for your admin to resolve before migration runs.

Contacts ending at 'Customer' or 'Evangelist' route to Salesforce Contact. All other lifecycle values route to Salesforce Lead. The split happens based on the final lifecycle value at migration time — stage-transition history is preserved as Lifecycle_Stage_History__c custom field for audit continuity.

Direct map. HubSpot company hierarchies (parent/child) preserved using Salesforce's Parent Account field. Multi-company contacts collapse to one primary AccountId with Account Contact Relations for the rest — your admin chooses the primary-company selection rule before migration. If a contact is linked to more than one company, each additional company appears as an Account Contact Relationship, preserving the original association label and any related custom fields.

Direct map. Each deal's pipeline maps to a Salesforce Sales Process tied to a record type. The deal's stage, amount, close date, and owner all migrate as Opportunity fields. Deal name becomes Opportunity Name, and deal amount maps directly to the Amount field.

HubSpot pipeline becomes a Salesforce Sales Process keyed by RecordTypeId. Each pipeline requires its own record type in Salesforce so that stage pick-list values and page layouts are scoped correctly per deal type. Your admin pre-creates record types before migration — we deliver the setup plan.

Stage names map value-by-value per record type. Stage probability, forecast category, and stage-entered timestamps are re-applied based on Salesforce's stage model. We preserve the original stage-enter date as a custom datetime field so reporting continuity is maintained after go-live. During migration, each stage transition also records the Salesforce StageName that corresponds to the source stage name, ensuring that historical pipeline reporting reflects the same milestones.

Salesforce has no native lifecycle-stage equivalent. We migrate the field as a custom pick-list (Lifecycle_Stage__c) on both Lead and Contact. Stage-changed timestamps are preserved as Lifecycle_Stage_Updated__c custom datetime fields. Salesforce admins configure the pick-list values to match source values during schema setup.

HubSpot calls and emails map to Salesforce Tasks with Type='Call' or Type='Email'. Meetings map to Events with original start/end times preserved. Notes map to Salesforce Notes (not legacy Note object). Original timestamps, owners, and parent-record links are preserved; activity-to-record associations are re-established in Salesforce.

Custom objects map 1:1 to Salesforce custom objects. Custom object associations that use a HubSpot N:N model need Salesforce junction objects when the relationship is many-to-many — we surface this in the migration plan and your admin defines the junction object structure before migration.

File attachments on records are re-uploaded to Salesforce Files. Salesforce's default file size limit is 25 MB per file — files exceeding this are flagged before migration so your team can decide whether to split, compress, or store externally. Inline images in notes are downloaded and rehosted in Salesforce.

Workflows and automations are platform-native constructs that do not have a direct migration path to Salesforce. FlitStack exports workflow definitions as a rebuild reference document for your Salesforce admin. Automations must be rebuilt in Salesforce Flow — the exported definitions serve as the functional spec for the rebuild.

Reports and dashboards are configuration artifacts that do not migrate. The underlying data that reports reference does migrate, so report bodies can be rebuilt on migrated data after go-live. FlitStack exports report and dashboard names and configurations as a reference list for your Salesforce admin.