Migrate from Leadtrekker Lead Management to Freshsales

Leadtrekker Lead records map directly to Freshsales Lead records. Standard fields (name, email, phone, status, lead source, owner) migrate as typed Freshsales Lead fields. Leadtrekker's lead status values map to Freshsales Lead Status dropdown values. Custom fields require discovery extraction during the API probe phase because Leadtrekker does not publish a stable field taxonomy. We create matching custom fields in Freshsales before import and apply the Freshsales field mapping configuration for lead conversion so custom field data transfers to Contact, Account, and Deal fields during the conversion step.

Leadtrekker activity records (notes, call logs, email events) attached to a Lead map to Freshsales Task, Event, or Note records linked to the migrated Lead. Each activity carries a timestamp and user attribution that we preserve in the Freshsales Activity Timeline. We use the activity type property from Leadtrekker to determine whether to create a Task (call log), Event (meeting), or Note (free-text entry) at the destination.

Leadtrekker user accounts (login, name, email, profile data) map to Freshsales User records. We resolve owners by email match. Any Leadtrekker user without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Passwords and session tokens do not transfer and require Freshsales login provisioning separately.

Leadtrekker user groups define which users can view and edit specific lead subsets. Freshsales uses a Team-based permission model where team membership controls record visibility. We extract the full group membership roster from Leadtrekker, map group structures to Freshsales Teams, and flag cases where Leadtrekker's lead-level permissions require a Freshsales permission-set or sharing-rule workaround. Group-level permission logic is reconfigured manually post-migration using the documented mapping table we deliver.

Leadtrekker lead source attribution (website form, campaign, referral) stored as a Lead property migrates to Freshsales Lead Source field. Source labels preserve as string values and can be mapped to Freshsales predefined lead source picklist values during import. If Leadtrekker uses custom source labels not present in Freshsales, we add them as custom picklist values before migration.

Leadtrekker follow-up reminders carry a due date and owner. We convert these to Freshsales Task records with the due date (Activity Date) and assignee (Owner) preserved. Reminder text migrates as the Task description. If the Leadtrekker reminder had a priority flag, we map it to Freshsales Task Priority values.

Leadtrekker custom fields on Leads require explicit field-level mapping because the platform does not publish a stable field taxonomy in public documentation. We conduct an API probe during discovery to extract the actual custom field names, types, and values from a sample of Lead records, then create matching custom fields in Freshsales (using the Add field workflow under Admin Settings) before migration. Freshsales field mapping configuration is applied so that custom field values transfer correctly during lead conversion to Contact, Account, or Deal.

Leadtrekker's automatic lead assignment rules cannot be exported as automation rules. We document every active assignment rule (criteria, assigned owner or group, priority order) in a written handoff inventory. The customer's admin rebuilds these as Freshsales Assignment Rules under Admin Settings, using the documented criteria and owner mappings as the specification.