Migrate from Marketing Tools Growth Marketing Platform to HubSpot

HubSpot stores all person records as Contacts with lifecyclestage determining their position in the buyer journey. Source platform person records map directly to HubSpot contacts. Lifecyclestage values from the source are preserved — HubSpot supports subscriber, lead, mql, sql, opportunity, and customer as standard values plus custom stages.

HubSpot Companies store firmographic data including name, domain, industry, employee count, and annual revenue. Source platform company or account records map 1:1 to HubSpot companies. Parent-child company hierarchies in the source platform map to HubSpot's company association model using the same hierarchy logic.

HubSpot Deals store pipeline data including deal name, amount, stage, close date, and owner. Source platform deal or opportunity records map to HubSpot deals. The destination deal's pipeline and stage fields are populated based on the source's pipeline configuration — HubSpot supports multiple pipelines with distinct stage sets per pipeline.

HubSpot's deal model uses a Pipeline object that groups Stages. Each pipeline has its own name and set of ordered stages with probability weights. Source platform pipeline definitions are translated into HubSpot pipeline objects with corresponding stage names and probabilities preserved. If the source uses a single pipeline, that becomes one HubSpot pipeline; if multiple pipelines exist, each is created as a separate HubSpot pipeline.

HubSpot Engagements store email records with subject, body, timestamp, and owner. Source platform email activity records map to HubSpot engagements of type email. The original sent timestamp and email direction (sent/received) are preserved as engagement metadata. Thread linking depends on the source platform's thread ID storage — HubSpot does not natively maintain conversation threads, but the email body and timestamp are preserved.

HubSpot stores calls, meetings, and notes as separate engagement types. Source platform call logs and meeting records map to HubSpot engagements of type call or meeting, preserving the original timestamp, duration (for calls), and owner. Notes map to HubSpot engagement notes with the original body text preserved.

HubSpot supports custom objects at Enterprise tier. Source platform custom objects map to HubSpot custom objects using the same name and field labels. Custom-object associations that use N:N linking in the source platform are handled via HubSpot's association labels or custom junction objects depending on the relationship cardinality. FlitStack AI identifies the appropriate association model during the mapping phase.

HubSpot tracks form submissions on the contact record as a timeline entry with the form name and submission date. Source platform form submission data is mapped to HubSpot contact timeline events showing the original form identifier and submission timestamp. Behavioral events like page views are preserved as a reference note if the source stores them as structured records.

HubSpot Users are the owner records in the CRM. Source platform owner or user records are matched to HubSpot users by email address. If a source owner has no matching HubSpot user, their records are assigned to a designated fallback owner (or a placeholder user created for migration) and flagged in the pre-migration report so your team can reassign after go-live.

HubSpot Files store attachments and documents linked to records. Source platform file attachments are downloaded and re-uploaded to HubSpot Files, then linked back to the parent contact, company, or deal record. File size limits apply (HubSpot's file upload limit is 250MB per file). Inline images embedded in notes are extracted and rehosted as HubSpot-hosted assets.

HubSpot Lists can be static or dynamic. Source platform static lists or segments are recreated as HubSpot static lists using the same contact membership. Dynamic lists with filter rules do not have a direct equivalent in HubSpot and must be rebuilt as HubSpot smart lists — the filter criteria are documented during the mapping phase so your team can reconstruct the logic in HubSpot's list builder.