Migrate from Sales Journey to HubSpot

Sales Journey contacts map directly to HubSpot contacts. Email address is the primary deduplication key. If a Sales Journey contact has no email, FlitStack flags the record for manual resolution before the full migration runs. All native contact properties transfer as HubSpot native fields or custom properties depending on HubSpot's field availability.

Sales Journey company records map 1:1 to HubSpot companies. Domain is used to match and de-duplicate against HubSpot's existing company database. Parent-child company hierarchies in Sales Journey map to HubSpot's parent company field. Multi-company associations on a contact collapse to one primary company in HubSpot, with secondary associations stored as custom properties for reference.

Sales Journey deals map directly to HubSpot deals. The deal name, amount, close date, owner, and stage transfer to HubSpot deal fields. Pipeline association maps to HubSpot's pipeline field. If Sales Journey uses multiple pipelines, each maps to a corresponding HubSpot deal pipeline created in the target account before migration.

Sales Journey pipelines translate to HubSpot deal pipelines. Each Sales Journey pipeline becomes a separate HubSpot pipeline with its own stage set. Stage names, probabilities, and forecast-category values map value-by-value into HubSpot stage definitions. HubSpot allows up to 50 pipelines in Enterprise editions — Sales Journey pipeline counts are validated against this limit before mapping.

Sales Journey sequences — the ordered series of emails and tasks sent to a contact — have no native equivalent in HubSpot CRM. FlitStack preserves sequence membership (which sequence, enrollment date, current step, status) as a custom contact property. Rebuilt HubSpot sequences can use this property to re-enroll contacts at the correct step. FlitStack exports sequence definitions as a JSON reference file for the admin to use when rebuilding in HubSpot Sequences.

Sales Journey engagement tracks record when a buyer opens an email, clicks a link, or views a content page. This data stores as activity timestamps in Sales Journey. HubSpot's engagement timeline captures calls, emails, and meetings natively. FlitStack converts engagement track events into HubSpot engagement log entries and preserves summary data (last engaged date, content viewed) as custom contact properties.

Sales Journey stores branded pages, pitch decks, and sales content as records. HubSpot Files store documents and media. FlitStack exports Sales Journey content files and re-uploads them to HubSpot Files. Engagement analytics on content pages (view count, time spent) do not have a HubSpot equivalent — these are preserved as custom properties for reference, and HubSpot's native file tracking can be enabled post-migration.

Sales Journey activity records (calls logged, emails sent, meetings scheduled, notes) map to HubSpot's engagement timeline on the contact record. Call disposition, duration, and outcome map to HubSpot call properties. Meeting titles and times transfer as HubSpot meeting records. Original timestamps and owner assignments are preserved so the engagement timeline reflects the full buyer journey.

Sales Journey custom fields on contacts, companies, and deals map to HubSpot custom properties. FlitStack creates each custom property in HubSpot before the migration run, matching the source field type (text, number, date, picklist). Picklist fields require value-by-value mapping if HubSpot's allowed values differ from Sales Journey's options. Custom fields that have no HubSpot equivalent are flagged for custom property creation.

Sales Journey owner records are matched to HubSpot users by email address. Active users with matching emails link automatically. Owners without a HubSpot user account are flagged before migration — the team either creates the HubSpot user first or assigns those records to a designated fallback owner. This prevents orphan records in HubSpot.

Sales Journey deal stage names map to HubSpot pipeline stage names value-by-value. Where stage names are identical, mapping is direct. Custom stage names in Sales Journey require a HubSpot stage with the matching name to be created first. Stage probabilities and forecast categories are re-applied based on HubSpot's stage configuration. Historical stage-enter timestamps are preserved as deal custom datetime properties.