Migrate from eTrigue to Twenty CRM

eTrigue Prospects map 1:1 to Twenty CRM Person records. Standard fields (name, email, phone, company, job title) transfer directly. We resolve the email address as the dedupe key and flag any Prospects with duplicate emails for the customer's admin to resolve before final insert. The migration runs in CSV tranches from eTrigue's built-in export because no public API exists.

eTrigue's Status field exports as numeric codes (e.g., 1 = Active, 2 = Opt-Out) that must be decoded before insert. We detect these during data profiling, apply a decoding map derived from eTrigue's support documentation, and set Twenty's Person subscriptionStatus or a custom hasOptedOut field appropriately. Silent insertion of numeric codes as text values would incorrectly set all records to active status.

eTrigue Prospects reference a company name as a text field rather than a related Company object. We extract distinct company names from all Prospects, upsert them as Twenty CRM Company records, then back-fill the Person.companyId lookup on each Person during insert. This creates the account hierarchy in Twenty that eTrigue never maintained.

eTrigue's 3D Lead Scoring stores Campaign Score, Activity Score, Source Score, Relationship Score, and Buy Time Score as five separate numeric properties on the Prospect. We create five custom number fields on the Person object in Twenty before migration, map each sub-score to its corresponding field, and flag the composite logic in a written scoring rebuild guide for the customer's admin. Merging five scores into one field loses the attribution detail that makes the 3D model useful.

If the customer uses eTrigue's standard composite Lead Score rather than 3D scoring, we map it to a single custom number field etrigue_lead_score__c on Person. We note which scoring model was active so the customer can decide whether to use Twenty's built-in lead scoring or rebuild the composite formula in a companion tool.

eTrigue records each Prospect's campaign responses (page views, email opens, form submissions, click-throughs) as a dated Activity History. We export this as a structured log and load it as Twenty CRM Timeline entries on the Person record, preserving the original timestamp and activity type. Each response becomes a separate Timeline entry with the campaign name as the context label. This is the richest data set in eTrigue and the most migration-intensive because of row count.

eTrigue Campaigns (names, campaign type, start and end dates) transfer to Twenty CRM Programs. We preserve the campaign response count and the associated Prospect list as a Program participants list in Twenty. Note that the campaign automation logic (workflow triggers, nurture sequences, enrollment criteria) does not migrate; we deliver a written campaign logic inventory for the customer's admin to rebuild in Twenty or a companion marketing automation tool.

eTrigue Boolean, Text, Number, and Date custom fields defined in Settings > Prospect Fields migrate to Twenty CRM Person custom fields of the equivalent type. Boolean fields with custom labels (e.g., true = 'Has Demo Access') transfer their string labels into a Text or Select field to preserve the original meaning. We pre-create the custom field schema in Twenty before any Person records are inserted.

Customers using eTrigue Lead Accelerator store partner organization names and partner-specific campaign attribution in custom Prospect fields. We map these to Twenty CRM Company custom fields (partner_name__c, partner_attribution__c) and flag any partner-specific scoring rules that relied on the Lead Accelerator scoring engine for manual recreation. The partner-to-company elevation requires that the Prospect.companyName field is populated, which we validate during data profiling.

eTrigue progressive form field definitions export as a field list but do not migrate as a functional form. We deliver a written form inventory with the source field names, types, and validation rules for the customer's admin to recreate in Twenty or a companion form tool. Styling and layout are not preserved.