Migrate from eSalesTrack to Freshsales

eSalesTrack leads migrate to Freshsales Lead records. The eSalesTrack lead status and source fields map to Freshsales Lead Status and Lead Source picklists. We resolve any custom fields on the eSalesTrack lead by pre-creating matching custom fields in Freshsales under Admin settings before import. If the customer plans to convert leads to contacts post-migration, they should configure the Field mapping dropdown under Leads module in Freshsales to map lead custom fields to Contact, Account, or Deal fields, otherwise data is lost on conversion.

eSalesTrack contacts map directly to Freshsales contacts. The contact name, email, phone, and address fields migrate to matching Freshsales fields. Owner assignment resolves by email match against Freshsales users. We flag any contacts with duplicate email addresses against the source dataset for the customer to resolve before final import, as Freshsales uses email as the unique identifier for deduplication.

eSalesTrack accounts map to Freshsales accounts. The account name, domain, industry, and address fields migrate directly. Account is imported before contacts so that the Account-Contact lookup relationship is satisfied at the moment of contact insert. Any eSalesTrack accounts without contacts migrate as standalone account records.

eSalesTrack opportunities map to Freshsales deals. The deal name, amount, close date, and stage migrate to matching Freshsales deal fields. Pipeline stage names from eSalesTrack are mapped to Freshsales pipeline stages, which must be configured under Admin settings before migration. We recommend configuring at least one pipeline in Freshsales before the migration begins.

eSalesTrack tasks migrate to Freshsales tasks with Status, Priority, due date, and description preserved. Task assignments migrate by resolving the eSalesTrack owner email against Freshsales users. Open and closed task status maps directly to Freshsales task status values.

eSalesTrack notes migrate to Freshsales notes attached via ContentDocumentLink to the parent record (Lead, Contact, Account, or Deal). Note content migrates as plain text. We use the parent record's email or name as the dedupe key to link the note to the correct record in Freshsales after the parent objects have been imported.

eSalesTrack owner assignments on leads, contacts, accounts, and deals resolve by email match against Freshsales users. We extract the full list of owners from eSalesTrack during discovery and compare against the Freshsales user list. Owners without a matching Freshsales user are flagged for manual provisioning before the main import begins, since OwnerId is required on all standard objects.

All eSalesTrack custom fields require pre-creation in Freshsales before migration. We audit the eSalesTrack field schema during discovery, map each field to the appropriate Freshsales field type (text, number, picklist, date, multi-select), and create the destination fields under Admin settings before any record import begins. Custom field creation is the gating step for any migration involving more than five custom fields.