Migrate from Marketing Tools Growth Marketing Platform to Freshsales

The source platform uses a single Contact object with lifecycle-stage properties for all person records. Freshsales separates unqualified prospects into Leads and qualified contacts into Contacts tied to Accounts. We define the split rule during scoping using the source lifecycle stage values, apply it as the first transform during migration, and preserve the original source lifecycle stage in a custom field on both Lead and Contact for audit. The split decision is the most consequential mapping in this migration pair.

Source platform Company records map directly to Freshsales Account. The company domain becomes the Account Website field and serves as the dedupe key during import. We export contact-company pairs from the source to preserve linkage, then resolve AccountId on each Contact at import time. Account records must import before Contact records so that the lookup relationship is satisfied.

Source platform segment definitions use platform-specific rule syntax that is not exportable. We extract the resulting segment membership per Contact — which contacts belong to which segments — and replicate that as Freshsales Tags on each Contact record. Segment rule logic must be rebuilt manually in Freshsales Segmentation or as contact property fields. This is documented in the migration scope for the customer admin.

Source platform Campaign metadata (name, status, channel, start/end dates) exports via API and maps to Freshsales Deals for revenue-linked campaigns or to Event records for event-based campaigns. Campaign performance metrics — open rates, click rates, revenue attribution — are not available via the documented export path. We advise customers to export reporting snapshots from the source analytics dashboard before the cutover date and preserve them as a reference CSV.

Workflow journey definitions — triggers, conditions, branch logic, and action steps — live in the source platform's internal automation engine and are not accessible via API export. We cannot carry them over automatically. During discovery we document every active journey with screenshots and a written description, and recommend rebuilding them in Freshsales Workflows (available from Growth tier) within the first post-migration sprint. This is a manual rebuild scope, not an automated migration.

Tags export from the source platform as flat key-value pairs per Contact. We map them directly to Freshsales Tags on the Contact record. We flag any tags that exceed Freshsales character limits before import and resolve by truncating or mapping to a custom field. Tag relationships to other objects (if stored cross-object on the source) are preserved as additional tag entries on the Contact.

The source platform's custom object schema is not publicly documented in the available evidence base. Where customers report custom object usage, we attempt field-level mapping during scoping by reviewing the custom object's data structure via API discovery calls. We then provision equivalent Freshsales custom objects with matching field types and lookup relationships before importing data. Any fields that cannot be mapped due to undocumented schema are flagged in a custom field inventory document for the customer's admin to address.

Source platform Owners map to Freshsales User records by email match. We extract every distinct Owner referenced on Contact, Company, and Deal records and match against the Freshsales destination User table. Any Owner without a matching Freshsales User is held in a reconciliation queue for the customer admin to provision before record import resumes.