Migrate from Freshmarketer to Freshsales

Freshmarketer contacts map directly to Freshsales contacts. Email address is the deduplication key: if a contact with the same email already exists in the destination Freshsales account, Freshmarketer field values overwrite existing data based on the precedence configured during scoping. We explicitly map field precedence before migration and give the customer a field-level diff to decide which values win. Custom contact fields are supported but require per-field type mapping because Freshmarketer supports only text, paragraph, number, checkbox, date picker, and dropdown while Freshsales supports additional types including lookup and multiselect.

Freshmarketer company records map to Freshsales accounts. The company domain becomes the Account Website field, and company-contact associations are preserved at migration time by resolving the Freshmarketer org_contact_id to the Freshsales Contact.AccountId relationship. We import Accounts before Contacts so that the AccountId lookup is satisfied at the moment of Contact insert to avoid orphaned contact records.

Freshmarketer deals map to Freshsales deals with pipeline stage names and amounts preserved. Pipeline assignment maps to a Freshsales pipeline that we verify or configure before migration. Custom deal fields require mapping against the destination field type. Owner fields reference Freshmarketer user IDs that are remapped to Freshsales User IDs by email match during the owner reconciliation phase.

Email logs, email conversations, sales activities, and calls migrate as activity records linked to the parent contact or company. We preserve the chronological activity timeline by setting timestamps to the original Freshmarketer values. Email activities sync between Freshmarketer and Freshsales as a separate integration layer; post-migration we flag whether this sync should be disabled or reconfigured to prevent duplicate entries.

Freshmarketer's Marketing Contacts concept is a billing distinction (contacts targeted in campaigns) with no direct Freshsales equivalent. We flag which contacts were enrolled in active Journeys or campaigns at migration time by checking the enrolled_contact_ids against the contact export. This flag is preserved in a custom field for billing transparency. The customer should verify Freshsales Suite plan limits for marketing contacts above the included threshold.

Freshmarketer segments do not have a direct equivalent in Freshsales as live dynamic audiences. We export segment criteria and contact membership as a static contact list document. The customer admin recreates these as Freshsales segments or static lists post-migration. Segments used for campaign targeting are documented with their contact count at cutover so the admin can validate the rebuilt audience.

Journeys cannot be exported as executable automation logic via Freshmarketer API. We capture Journey configuration as a structured reference document including trigger conditions, step definitions, enrolled contact count, and which contacts were enrolled at cutover. The customer admin uses this to replay Journeys manually in Freshsales Workflows or to configure equivalent automation. We explicitly flag which Journeys were active and the total enrolled contact volume per Journey so nothing is silently lost.

Custom fields on contacts, companies, and deals are supported via API but require explicit per-field mapping. Field type differences must be resolved during scoping: Freshmarketer does not support lookup, tooltip, multiselect, radio button, or formula fields, so any Freshsales destination fields of those types require either field type changes in Freshsales or a dependent field workflow to replicate the data. We map dropdown to dropdown, text to text, and number to number directly; multi-select and lookup require a custom handling decision.

Tags migrate as a flat string list applied to contacts, companies, and deals. No tag hierarchy exists in Freshmarketer. Tags are re-applied as tag values at the destination and are preserved on a per-record basis. We verify tag character encoding during extraction to avoid truncation issues with non-ASCII characters in tag names.

User accounts including name, email, role, and team assignment migrate by email match. Owner fields on Contacts, Deals, and Activities reference Freshmarketer user IDs that are remapped to Freshsales User IDs. Any Freshmarketer user without a matching Freshsales User is held in a reconciliation queue for the customer admin to provision before record import resumes. During the migration, Freshmarketer users are not charged as Freshsales users per Freshworks migration policy, but post-migration any user addition triggers billing.