Migrate from Leadfwd to Freshsales

Salesforce extraction and polling lag management

We begin by connecting to the customer's Salesforce instance—the system that Leadfwd syncs to via OAuth. We confirm the last Leadfwd sync timestamp, wait for the next hourly poll to complete, then extract all Contacts, Companies, Leads, and Deals with their most recent modified dates. We pull engagement history (calls, emails, meetings) using Salesforce SOQL queries scoped to the Leadfwd sync window. This extraction step takes two to four hours and produces the staging CSV files that all downstream import steps reference.

Schema audit and Freshsales custom field creation

We audit every custom field on Leadfwd's Contact, Company, and Deal objects by reviewing the Salesforce field map that Leadfwd syncs. We then create matching custom fields in the customer's Freshsales instance under Admin Settings, matching field types (text, number, date, picklist) to their Freshsales equivalents. This step also includes configuring Lead conversion field mapping for any Leads that will convert to Contacts and Accounts post-migration.

Sequence enrollment export as rebuild inventory

We export all active Sequence enrollment records from Salesforce, including Contact email, Sequence name, current step index, enrollment status, last activity timestamp, and channel (email, LinkedIn, SMS). We format this as a structured CSV and a written inventory document. This is the handoff artifact the customer's admin uses to replay Sequences in Freshsales Workflows after migration. We do not attempt to execute these enrollments in Freshsales because there is no native equivalent.

Sandbox import and reconciliation

We run a test import into the customer's Freshsales sandbox or a trial account using the extracted CSV files. We validate record counts (Contacts in, Accounts in, Deals in), spot-check twenty to thirty records field-by-field against the Salesforce source, and verify that custom field data landed correctly. Any mapping corrections or missing custom fields are fixed in this phase before production import begins.

Production import in dependency order

We run production import in dependency order: Accounts first (from Leadfwd Companies), then Contacts, then Leads, then Deals. Icebreaker content attaches as Notes after Contact import. Engagement history (calls, emails, meetings) imports as Activities via CSV. Each phase emits a row-count reconciliation report before the next phase begins. Owner assignment resolves by email match; any Leadfwd owner without a matching Freshsales user is flagged in the reconciliation report for admin provisioning before the next phase.

Cutover, delta sync, and rebuild handoff

We freeze Leadfwd writes during cutover, run a final delta import of any records modified during the migration window, then hand off. The Sequence enrollment inventory and Icebreaker content are delivered as part of the migration package. We do not rebuild Leadfwd Sequences as Freshsales Workflows inside migration scope; that is a separate exercise documented in the handoff. We offer a one-week hypercare window for reconciliation issues raised by the sales team during the first days of Freshsales use.