Migrate from LeadSimple to Twenty CRM

LeadSimple leads bundle contact info, property details, and deal stage into one record. FlitStack AI splits this into a Twenty Person record for the contact fields and an Opportunity record for the property data and pipeline stage. The Opportunity links back to the Person via the opportunities array. This preserves the lead's identity and deal value in the correct Twenty objects.

LeadSimple's Lead Name field holds the full contact name. Twenty Person requires a name object with firstName and lastName or a displayName. FlitStack parses the full name, splitting on the first space; names without a space land in firstName with lastName blank. Original Lead Name preserved in a custom text field for reference.

LeadSimple email maps directly to Twenty Person email field. Email serves as the unique identifier for Person-to-Person deduplication and for resolving workspace member relations during import. Bounced or invalid emails flagged in a custom field for post-migration cleaning. Teams should verify email deliverability status in LeadSimple before migration to ensure active addresses transfer cleanly without bounced-flag overrides.

LeadSimple's Combined Phone Numbers concatenates multiple phone types into one field. FlitStack parses and splits by type label (Cell, Work, Home) into Twenty Person.phone primary and phone (additional) fields. If parsing fails, the full string lands in phone with a warning flag.

Property Type (e.g., Single Family, Multi Family, Commercial) has no Twenty native equivalent. FlitStack creates a custom pick-list field (customPropertyType__c) on Opportunity, populates with LeadSimple's values, and maps the pick-list options during migration. Teams must configure field visibility in Twenty's data model settings.

LeadSimple Annual Contract Value maps directly to Twenty Opportunity.amount as a currency field. This is the primary deal-value field in Twenty's pipeline view. Values preserved as-is; null ACV records land with amount = 0 and a note flagging the missing value.

LeadSimple Pipeline Name and Stage Name combine into a stage value. FlitStack maps stage names to Twenty Opportunity.stage pick-list values. New stage options created in Twenty's data model to match LeadSimple's exact stage names before import. Stage probabilities re-applied from LeadSimple stage configuration as custom number fields.

LeadSimple Tag List is a comma-separated string per lead. FlitStack creates a custom text array field (customTags__c) on both Person and Opportunity, populating with LeadSimple's exact tags. Tag filtering in Twenty's view builder lets teams replicate LeadSimple's tag-based segmentation. Multi-value tags are preserved as array elements with original casing intact for accurate reporting.

LeadSimple Assigned To references a user. FlitStack resolves by email match against Twenty workspace members. Unmatched owners flagged before migration; teams either invite them to Twenty first or assign to a fallback workspace member. The workspace member relation links the Person and Opportunity to the correct Twenty user.

LeadSimple tracks lead Source and Referrer as separate fields. FlitStack creates custom text fields on Opportunity (customSource__c, customReferrer__c) and populates from the export. These drive source reporting in Twenty's pipeline views and can be used for lead attribution analysis. Teams should audit source and referrer field values during discovery to identify all unique values that need corresponding pick-list options or custom field configurations in Twenty.

LeadSimple lead records sometimes link to a Company object. When present, the Company maps directly to a Twenty Company record. The Person links to the Company via Person.companyId. Companies without contacts land as standalone records for future association. During migration, FlitStack validates that all LeadSimple company IDs have corresponding records and flags any orphaned references for manual resolution before the People import begins.

Occupancy field (e.g., Occupied, Vacant, Under Renovation) has no native Twenty equivalent. FlitStack creates a custom pick-list field (customOccupancy__c) on Opportunity with values matching LeadSimple's pick-list. This drives vacancy-rate reporting in Twenty's pipeline dashboards. Teams should audit all LeadSimple occupancy values during discovery to ensure all active statuses transfer and unused values are excluded from the pick-list configuration to keep the field clean.

Number of Units per property record maps to a custom integer field (customUnits__c) on Opportunity. This is critical for property managers tracking portfolio size per deal. Values preserved as integers; null values flagged for manual review post-migration. Teams should verify unit counts in LeadSimple before migration to ensure data accuracy and identify any non-numeric values requiring normalization during the import process.

LeadSimple Cost field (likely property management cost or deal cost) maps to a custom currency field (customCost__c) on Opportunity. FlitStack preserves the decimal precision and currency label. Teams use this for margin analysis in Twenty reporting. Currency formatting should be verified during test migration to ensure consistent display across all records and alignment with team preferences for regional number formats.