Migrate from LeadTrac to Twenty CRM

LeadTrac leads map directly to Twenty People records. Email, phone, name, and address fields transfer as-is without transformation. Owner assignment resolves by email match against Twenty workspace members; we check each LeadTrac ownerId against Twenty's workspaceMember records and flag unmatched owners for manual resolution before migration commits. This ensures every migrated Person has a valid ownerId and prevents orphaned records.

LeadTrac contacts map to Twenty People with full activity history preserved. All standard fields including name, email, phone, and address transfer directly. If the contact has an associated company in LeadTrac, the company must exist in Twenty as a Companies record first so the companyId relation resolves correctly during import. Owner assignment follows the same email-match logic used for leads, with unmatched owners flagged for manual assignment.

LeadTrac companies map to Twenty Companies records with all standard fields transferred including name, domain/website, industry, employee count, and annual revenue. Industry pick-list values map value-by-value to Twenty's industry options; any unmapped values default to a generic option and are flagged for admin review post-migration. The companyId is preserved as the primary key for cross-object linking.

LeadTrac deals map to Twenty Opportunities with deal name, amount, stage, and close date preserved across both systems. Stage values are mapped value-by-value to Twenty Opportunity stage options during the schema setup phase. The associated companyId links to the migrated Companies record, and the ownerId resolves via email match against Twenty workspace members before the Opportunity import batch runs.

LeadTrac activities map to Twenty Tasks for calls and emails, Events for meetings, and Notes for free-form entries. Original timestamps and owner assignments are preserved throughout the transformation. If LeadTrac exports activities as a flat list without parent relations, we reconstruct the relation to the parent Person or Opportunity record using available foreign keys in the export.

LeadTrac document attachments — PDFs of bills, settlement offers, agreements — are downloaded from LeadTrac's storage layer and re-uploaded to Twenty's storage layer, linked via Note records to the parent Person, Company, or Opportunity. File size limits apply per Twenty's hosting configuration, and we verify each document is within those limits before uploading. Documents that exceed limits are flagged for manual handling.

LeadTrac custom field sets scoped to intake, enrollment, and sales processes migrate as custom fields on the corresponding Twenty object (Person, Company, or Opportunity). We create each field in Twenty's data model before migration runs, preserving the original field type such as text, number, select, multi-select, date, or currency. If a LeadTrac field type has no direct Twenty equivalent, we flag it for admin review and create a best-fit alternative.

LeadTrac owner IDs resolve by email match against Twenty workspace members. We generate an owner-resolution report during the audit phase showing matched and unmatched owners. Your team resolves unmatched owners either by inviting them to Twenty first or by assigning their records to a designated fallback workspace member. No record migrates without a resolved ownerId to maintain accountability trails.

LeadTrac department-specific workflows and automation rules covering intake, enrollment, and sales processes do not have a direct equivalent in Twenty and cannot be migrated as data. We export the workflow definitions as a structured JSON reference document for your Twenty admin to rebuild using Twenty's Workflows feature (Organization tier and self-hosted only) or external automation platforms such as Zapier or Make.

LeadTrac SMS and telephony activity logs have no native equivalent in Twenty and require external tooling post-migration. Twenty does not include built-in SMS or telephony integration, so teams typically reconstruct this functionality using Twilio, Intercom, or similar communication platforms connected via webhook-to-Twenty workflows or the MCP server.

LeadTrac's native DocuSign integration for agreement and envelope signing has no direct Twenty equivalent. Completed envelope IDs and completion status can be recorded as a Note or custom field on the associated Person record for historical reference, but the active DocuSign connection must be rebuilt post-migration using DocuSign's own API, DocuSign webhook integrations, or middleware platforms like Zapier.

LeadTrac lead source fields and UTM tracking data migrate as custom text fields on Twenty People records. These are preserved for reporting continuity even though Twenty's native attribution model differs from LeadTrac's source-tracking approach. The custom fields are created in Twenty's data model before migration and populated with the original LeadTrac values for analytics and historical reporting purposes.