Migrate from eSalesTrack to Twenty CRM

eSalesTrack Lead records map to Twenty CRM Person records. The Lead's first name, last name, email, phone, and company association transfer directly. We create a Person record first, then link it to the corresponding Company record that was created from the eSalesTrack Account. Lead status values from eSalesTrack are preserved in a custom field esalestrack_lead_status__c for reporting continuity.

eSalesTrack Contact records map to Twenty CRM Person records. If the customer uses both Lead and Contact objects in eSalesTrack, we migrate both to Person and rely on the esalestrack_lead_status__c field to distinguish converted versus unconverted records. Contact title, department, phone, email, and address fields map directly to the corresponding Twenty Person fields.

eSalesTrack Account records map to Twenty CRM Company records. The Account name, domain, industry, phone, website, billing address, and annual revenue transfer directly. Account is created before any Person import so that the Person-to-Company link is satisfied at the moment of Person insert. We use Account domain as a deduplication key during import.

eSalesTrack Opportunity records map to Twenty CRM Opportunity. The opportunity name, amount, close date, probability, and stage transfer directly. Stage values from eSalesTrack are mapped to Twenty Opportunity status values, with the stage probability preserved as a custom field opportunity_probability__c. Owner assignment resolves by matching eSalesTrack owner email to Twenty User email.

eSalesTrack pipeline stages map to Twenty CRM Opportunity status values. We configure the status sequence in Twenty's Settings before migration, including stage names, order, and probability percentages where applicable. If eSalesTrack uses a custom stage name not available in Twenty's default set, we create a custom status value.

If eSalesTrack includes product catalog data, we map Product records to Twenty CRM Product records. Product name, SKU, description, and unit price transfer directly. Products are imported before any OpportunityLineItem records to satisfy the foreign key reference.

eSalesTrack task records map to Twenty CRM Task records. Subject, due date, status, priority, and assigned owner transfer directly. Task status values are mapped to Twenty Task status options. Owner resolution uses email matching to the Twenty User table. Tasks are imported after Person and Opportunity records so that the activity links are satisfied.

eSalesTrack note records map to Twenty CRM Comment records. The note body, associated record type (Lead, Contact, Account, Opportunity), and associated record ID transfer directly. We create Comment records linked to the corresponding migrated Person, Company, or Opportunity using the post-migration record IDs. Note timestamps are preserved as the Comment creation date.

eSalesTrack owner records map to Twenty CRM User accounts. We resolve owners by email match. Any eSalesTrack Owner without a matching Twenty User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on Leads, Contacts, Accounts, and Opportunities is resolved after User provisioning completes.

eSalesTrack custom fields on Lead, Contact, Account, and Opportunity map to Twenty CRM custom fields. We pre-create the destination schema in Twenty's Settings → Data Model before any data import, including all field types, labels, and API names. Text, number, date, picklist, and boolean field types migrate directly. Multi-select picklists from eSalesTrack map to Twenty multi-select fields.

eSalesTrack workflow automation rules do not migrate to Twenty CRM. We deliver a written inventory of every active eSalesTrack Workflow with its trigger conditions, actions, and field updates. The customer's admin reviews this inventory and configures equivalent automation in Twenty's workflow settings. This ensures transparency about what automation requires manual rebuild.

eSalesTrack engagement records for calls, emails, and meetings map to Twenty CRM Activity records. The activity type, subject, date, duration (for calls), and associated record link transfer directly. Activity associations are resolved using the post-migration record IDs for the linked Person, Company, or Opportunity. If eSalesTrack exports engagement history as a separate CSV, we parse and ingest it after the primary record migration.