Migrate from Leadtrekker Lead Management to Twenty CRM

Leadtrekker Lead records map to Twenty CRM Person records. Standard fields (name, email, phone, status, lead source) map directly. The Lead's assigned owner maps to the Person's workspace member assignment. We preserve the Leadtrekker status value in a custom field lt_original_status__c for audit. Because Twenty's Person object is a unified contact model without a separate Lead conversion step, Leadtrekker leads land directly as Twenty People without a split.

Leadtrekker activity records (notes, call logs, email events) attached to a Lead migrate to Twenty CRM Timeline Entries on the corresponding Person record. Each Timeline Entry preserves the original timestamp and user attribution. Call disposition and duration from Leadtrekker call logs migrate as custom fields on the Timeline Entry. We resolve the parent Person by matching the Lead's email address to Twenty's Person email field.

Leadtrekker's lead source attribution (website form, campaign, referral) is stored as a Lead property. We create a custom field lead_source__c on Twenty's Person object and populate it from the Leadtrekker source label. If the customer uses multiple source values, we normalize them to a consistent label set during migration to avoid fragmentation in Twenty's filtering.

Leadtrekker user accounts (name, email, login) map to Twenty CRM workspace members. We export the user roster by email match. Passwords and session tokens do not transfer; each user receives a Twenty invitation link post-migration. If a Leadtrekker user is inactive or has no email match, we flag them in the reconciliation queue for the customer admin to provision.

Leadtrekker user groups assign lead-level view and edit permissions to subsets of users. Twenty CRM uses workspace roles (Viewer, Editor, Admin) with optional field-level restrictions. We extract the full Leadtrekker group membership roster, map each group to the closest Twenty role (or create a custom role if the permission semantics require it), and document the mapping. Permission logic is reconfigured manually post-migration using Twenty's role settings.

Leadtrekker follow-up reminders carry a due date and owner assignment. We convert these to Twenty CRM Task records attached to the Person. Due date and assignee migrate directly. Completed status and completion timestamp transfer to the Task's status and completion date fields.

Any Leadtrekker custom fields added to the Lead object require explicit field-level mapping because Leadtrekker does not publish a stable field taxonomy. We conduct a discovery probe against the Leadtrekker API during scoping to enumerate all active custom fields, then create matching custom fields on Twenty's Person object before migration. Field type mapping follows: text to string, number to number, date to date, dropdown to select.

If Leadtrekker Lead records contain company name and the customer has a meaningful number of company-attributed leads, we create Twenty CRM Company records and link Person records via the company relationship. This mapping is optional and activated only if the company field is populated in more than 30 percent of Lead records.

Leadtrekker SMS and email notification preferences are platform runtime settings, not stored as exportable data records. We document all notification-trigger events observed during extraction (assignment alerts, status change alerts, reminder notifications) in the handoff inventory. The customer manually configures notification rules in Twenty CRM post-migration using Twenty's workflow actions.

Leadtrekker's automatic lead assignment rules (round-robin, territory-based, load-balanced) are platform logic with no direct Twenty CRM equivalent. We extract and document the active assignment rules as a written inventory with trigger conditions, target groups, and rule order. The customer rebuilds assignment logic in Twenty CRM using workflow filters and member assignment actions.