Migrate from Freshmarketer to HubSpot

Freshmarketer's single Contact object splits in HubSpot by lifecycle_stage. Contacts with lifecycle_stage set to 'Customer' or 'Evangelist' land as HubSpot Contacts; all other contacts (including 'Lead', 'Marketing Qualified Lead', 'Sales Qualified Lead', and 'Subscriber') route to HubSpot Leads. The split logic runs during migration based on the source lifecycle_type value stored on each contact record.

Freshmarketer company records map to HubSpot Companies with a direct 1:1 field mapping. The company name, domain, industry, employee count, and annual revenue fields carry over without transformation. Parent-company hierarchy in Freshmarketer maps to HubSpot's parent company association using the HubSpot parent_company_id reference field.

Freshmarketer deals map to HubSpot Deals. Each Freshmarketer deal carries a pipeline reference and a stage name; these map to HubSpot's deal_pipeline and dealstage fields. The deal amount, close date, owner, and custom deal fields migrate as HubSpot deal properties. Deals without a company link are attached to a default HubSpot Company record to satisfy the platform's referential integrity.

Each Freshmarketer pipeline becomes a HubSpot Deal Pipeline. Pipeline names map directly to HubSpot pipeline names. Stage names within each pipeline map to HubSpot dealstage values under that pipeline. Probability weights stored per stage in Freshmarketer are preserved in HubSpot's stage probability configuration. Teams using multiple pipelines in Freshmarketer end up with multiple pipelines in HubSpot — no collapsing occurs.

Freshmarketer custom contact fields (created under Settings > Custom Fields) are exported as named columns and must be pre-created in HubSpot as custom properties before the migration ingests contact records. FlitStack delivers a custom property creation guide with field type recommendations (text, number, date, checkbox, picklist) based on the Freshmarketer field type metadata. Unmapped custom fields land as text properties by default unless a type conflict is flagged.

Freshmarketer call logs (including call direction, duration, outcome, and owner) migrate as HubSpot engagements with type 'Call'. Original call start timestamp and owner assignment are preserved. HubSpot's engagement model requires a linked contact record; calls without a resolved contact are flagged for manual review before the activity migration batch runs.

Freshmarketer email logs (including subject, body, direction, and timestamp) migrate as HubSpot email engagements. Original timestamps and owner assignments are preserved in HubSpot custom datetime fields since HubSpot sets the engagement creation date at import time. Email body HTML is preserved as-is for display in HubSpot's contact timeline.

Freshmarketer meeting records (with title, start time, end time, location, and attendees) map to HubSpot Calendar Events linked to the contact record. Attendee email addresses are matched against the migrated contact list to create attendee associations. Meetings without matching contacts in HubSpot are imported as standalone events and flagged for owner assignment.

Freshmarketer notes migrate as HubSpot Notes attached to the relevant contact or company record. Note body text and any internal/external visibility flags are preserved. If the note contains a file attachment, the file is downloaded and re-uploaded to HubSpot Files and attached to the note record.

Freshmarketer user records (sales reps, admins) are resolved by email address against HubSpot users. Active Freshmarketer users who have a matching email in HubSpot get assigned as record owners. Users without a HubSpot match are flagged before migration — the team either creates HubSpot user accounts for them or assigns their records to a fallback owner. Inactive Freshmarketer users are not migrated.

Freshmarketer Journeys store multi-step behavioral sequences tied to contact events and email sends. HubSpot Workflows serve a similar function but use different trigger semantics, action types, and enrollment criteria. Journeys cannot be migrated as executable automation — FlitStack exports a JSON description of each Journey (trigger conditions, step sequence, delay rules, exit criteria) as a rebuild reference for the HubSpot admin.

Freshmarketer form submissions associated with contacts migrate as HubSpot form submissions attached to the contact record. Submission timestamp and form name are preserved through the migration. These submissions appear in HubSpot's form submissions array on the contact, maintaining the original context of when and how each submission occurred.

Freshmarketer's website tracking code captures page views, session duration, and behavioral events tied to known contacts. HubSpot has its own tracking pixel with a different event model. Historical behavioral events are preserved as contact property history entries but the raw session-level data is not migrated — the HubSpot tracking code must be installed post-migration to resume event capture.