Migrate from LeadSmart Channel Cloud to Twenty CRM

LeadSmart Lead records migrate to Twenty Person records with the Workable toggle enabled. Standard Salesforce Lead fields (FirstName, LastName, Email, Phone, Company, LeadSource, Status) map to Twenty Person fields by API name. Lead Status from LeadSmart becomes a custom picklist field in Twenty. We resolve the Lead conversion by creating the Company record first (from LeadSmart Account or Company), then linking the Person to that Company.

LeadSmart Contact records migrate to Twenty Person records (Workable = false). Standard Contact fields (FirstName, LastName, Email, Phone, Title, Department) map to Twenty Person fields. The contact's role on an Account (e.g., distributor rep, dealer contact) migrates to a custom text or picklist field in Twenty since Twenty lacks a native Contact Role object like Salesforce.

LeadSmart Account records migrate to Twenty Company records. The manufacturer-distributor-dealer hierarchy uses the Account.ParentId relationship, which we preserve by migrating parent Accounts first, then resolving ParentId as a lookup to the already-migrated Company. LeadSmart Account custom fields (channel_type, tier_level, etc.) map to Twenty Company custom fields by API name.

LeadSmart Opportunity records migrate to Twenty Opportunity records directly by object name. StageName maps from LeadSmart's pipeline stage to Twenty's Stage field. Amount, CloseDate, Probability, and Description migrate directly. OwnerId from Salesforce resolves to Twenty's workspace Member assigned to the Opportunity. Opportunity custom fields for channel-specific deal types map to Twenty Opportunity custom fields.

LeadSmart Activity records (Task and Event) migrate to Twenty Task and Event records with the original ActivityDate preserved for timeline ordering. Task status (Not Started, In Progress, Completed) maps to Twenty Task status. Event start and end timestamps migrate to Twenty Event. Completed activities preserve CompletedAt timestamp from Salesforce.

LeadSmart Partner Portal external user records have no direct Twenty CRM equivalent. We inventory every Partner Portal contact role (reps, brokers, dealers, distributors), map the external contact to a Twenty Person record, and document the channel partner relationship as a custom field on the associated Company record. The customer rebuilds any portal-facing sharing logic using Twenty's row-level security and custom views.

LeadSmart Campaign records migrate to Twenty Target List records. Campaign Member status history (Sent, Open, Clicked, Responded) maps to Target List membership fields. Campaign Type and BudgetedCost migrate as custom fields. Note that Twenty's Target List is a simpler model than Salesforce Campaigns; multi-touch attribution and campaign hierarchy do not have direct equivalents.

LeadSmart adds industry-specific custom fields to standard Salesforce objects for channel sales workflows. During scoping we inventory every custom field with its Salesforce API name, data type, and current values. We create matching custom fields in Twenty's schema before migration. Fields with no semantic equivalent (e.g., channel_visibility__c for Partner Portal sharing) are flagged and either created as generic custom fields or exported to a supplementary CSV with the migrated records.

LeadSmart Files and Attachments linked to standard Salesforce records migrate to Twenty Attachments. We preserve the parent record linkage by resolving the target Contact, Company, or Opportunity by email or name match. Large binary files (over 10 MB) may require chunked transfer; we flag these during scoping.

LeadSmart internal User records migrate to Twenty Workspace Members. We match by email address and resolve Role and Profile assignments from Salesforce to Twenty's permission model. External Partner Portal users do not migrate as Members; they are handled via the Partner Portal records inventory.