Migrate from Leadtrekker Lead Management to Salesforce Sales Cloud

Leadtrekker's Lead record (name, email, phone, status, lead source, owner) maps to Salesforce Lead for unqualified prospects. Leads that represent qualified buyers with an existing company context split to a Salesforce Account and Contact pair. We compute the split using Leadtrekker's status and assignment history during scoping. The original Leadtrekker source attribution (form, campaign, referral) migrates to Salesforce LeadSource or a custom field for reporting continuity.

Leadtrekker's lead source attribution (website form, campaign, referral) maps directly to Salesforce's standard LeadSource picklist or a custom multi-select field if the customer's source taxonomy is broader. Source labels are preserved as-is to maintain historical marketing ROI reporting continuity. If Leadtrekker stored UTM parameters as custom fields, these migrate to Salesforce custom fields with a utm_ prefix.

Leadtrekker activities (notes, call logs, email events) attached to a Lead migrate to Salesforce Task and Event records linked to the migrated Lead or Contact via WhoId. Call logs map to Task with TaskSubtype = Call. Email events map to Salesforce EmailMessage plus a related Task for timeline display. Timestamps and user attribution are preserved as ActivityDate and OwnerId. Large activity volumes require Bulk API 2.0 with parent-record resolution.

Leadtrekker follow-up reminders with due date and owner migrate to Salesforce Task. Due date, assignee (OwnerId), priority, and status migrate directly. Reminders without a due date migrate as open Tasks with no due date. Completed status on the source reminder maps to Salesforce Task Status = Completed.

Leadtrekker user accounts (name, email, profile) export as a roster. We resolve Leadtrekker owners by email match against the destination Salesforce org's User table. Any Leadtrekker owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Passwords and session tokens do not transfer.

Leadtrekker groups define lead-level view and edit permissions for a set of users. We extract the full group membership roster and build a mapping table from Leadtrekker groups to Salesforce Roles or Teams. The destination permission model (role hierarchy versus team-based sharing) is chosen during scoping with the customer's admin. Group permission logic is reconfigured manually post-migration as Salesforce Sharing Rules, Role Hierarchy, or Team Membership.

Leadtrekker does not publish a stable custom field taxonomy in its public documentation. We conduct a schema discovery step during scoping, probing the Leadtrekker API for field metadata to identify all custom fields in use. Each discovered custom field is mapped to a typed Salesforce custom field (Text, Number, Picklist, Date, Checkbox) before migration. Custom field names are preserved with a Leadtrekker origin prefix (lt_legacy__) for audit trail clarity.

Leadtrekker stores SMS and email notification settings (autoresponders, assignment alerts, response-time triggers) as platform runtime preferences, not as exportable data records. We do not migrate notification settings. We document every notification-trigger event in use during extraction and deliver a written inventory of each autoresponder, alert type, and routing rule with recommended Salesforce Flow equivalent for the customer's admin to rebuild manually.

Leadtrekker's automatic lead assignment rules (round-robin, source-based, territory-based) are platform configuration, not data records. We extract the rule logic during scoping and document the rule type, conditions, and assignment targets for manual rebuild as Salesforce Lead Assignment Rules or Flow-based routing.

Leadtrekker's automated workflows, SMS autoresponders, and multi-step sequences are automation code that has no Salesforce equivalent as data records. We do not migrate them. We deliver a written inventory of each automation with its trigger, conditions, actions, and a recommended Salesforce Flow replacement for the customer's admin to configure post-migration.

Leadtrekker's built-in lead management analytics and marketing ROI reporting do not transfer as Salesforce reports or dashboards. We document the Leadtrekker report names, metrics, and filter logic during extraction. The customer's admin or a Salesforce partner rebuilds equivalent reports in Salesforce Reports & Dashboards or a BI tool of choice.

Leadtrekker's website form integrations (one-tag WordPress and Drupal embed) and Zapier connections do not migrate. We document the integration endpoints and trigger events during extraction. Salesforce Web-to-Lead or a Salesforce-provided form embed replaces the website capture layer. Zapier automations are re-created as Salesforce Flow or webhook-based integrations post-migration.