Migrate from Market Leader to Freshsales

Lead product assignments have no native Freshsales equivalent

Market Leader lead products (Lead Stream, Network Boost, Leads Direct, HouseValues) attach to contacts as campaign-style product assignments that track which paid lead source generated each contact. Freshsales has no native equivalent — there is no 'lead product' field on Contact. FlitStack stores the lead product name as a custom pick-list field on Contact for historical reference, but the financial tracking model (how much you paid per lead, which zip codes triggered which product) is not carried. Your team recreates this tracking in Freshsales using custom fields and reports post-migration.

Auto-drip campaign logic requires Freshsales Workflow and Sequence rebuild

Market Leader auto-drip campaigns store email content, timing rules, and contact enrollment criteria as a campaign object. Freshsales separates this into Sales Sequences (for outreach cadence) and Workflows (for enrollment triggers). The email content itself can be exported as HTML, but the cadence logic — delay days, step conditions, exit criteria — must be rebuilt manually in Freshsales. FlitStack exports the campaign structure as a reference document your admin uses to configure Sequences. Plan 2–4 hours per complex drip sequence for this rebuild.

Market Leader lifecycle stage needs manual Freshsales lifecycle configuration

Market Leader tracks contact lifecycle through status flags and lead-product associations. Freshsales Lifecycle Stages are configured in Admin > Lifecycle Stages with custom labels and transition rules. If your team uses custom lifecycle stage names in Market Leader (e.g., Prospect, Active, Closed-Won), those labels must be re-created as Freshsales Lifecycle Stage values manually before contacts import — otherwise contacts land with a blank lifecycle stage and require manual updating. This step is critical for reporting accuracy and for automation triggers that depend on lifecycle stage values. Plan to allocate time in the Freshsales admin console to define each stage and its downstream effects before the migration window.

Duplicate contact detection requires Freshsales merge review post-import

Market Leader allows duplicate contacts on the same email address under different company associations. Freshsales Contact deduping runs on email by default and flags duplicates at import. FlitStack identifies duplicate email addresses before migration and surfaces them as a pre-migration report — your admin decides whether to merge in Market Leader before export or handle duplicates in Freshsales post-import using Freshsales's native contact merge tool. If duplicates are not resolved prior to migration, Freshsales will create multiple contact records sharing the same email, which can affect segmentation and email deliverability. Choose the merge strategy that aligns with your data hygiene policy and update any automation rules that reference contacts accordingly.

Inactive owners create orphan records without fallback assignment

Market Leader owner records can be marked inactive while retaining deals and contacts. Freshsales requires every record to have a valid OwnerId — records without an owner fail import. FlitStack flags all inactive Market Leader owners before migration and assigns their records to a designated fallback Freshsales user. Without this step, records from inactive owners would fail to write and appear as incomplete in your Freshsales account after migration. This ensures data completeness and prevents gaps in owner assignment that could affect reporting and task routing.