Migrate from Lead Perfection to Twenty CRM

Lead Perfection prospects map directly to Twenty People records. The primary contact name, email, phone, and job title transfer as standard People fields. Prospects without a company association create standalone People records; those with a company link require a prior Company record in Twenty.

Lead Perfection company/organization records map to Twenty Companies. Company name, website, industry, and address fields transfer directly. Multi-address records (billing/shipping) require splitting into separate custom address fields in Twenty since Twenty's standard model stores a single address per company record.

Lead Perfection jobs map to Twenty Opportunities. The job name becomes the Opportunity name, estimated value maps to the amount field, and job status maps to the Opportunity stage via value mapping (Lead Perfection's open/closed/in-progress stages translate to Twenty's custom stage pipeline). Job-level custom properties that don't match Twenty's standard Opportunity fields become custom fields on the Opportunity record.

Lead Perfection appointment records attached to jobs become Twenty Tasks linked to the parent Opportunity. Appointment summary, notes, start/end times, and assigned sales representative transfer as Task fields. The original appointment date is preserved as a custom datetime field if reporting continuity requires historical activity timestamps.

Lead Perfection stores address components (line_1, city, state, postal_code) on the job record and separately on a Job Address object. These map to the Twenty Companies address fields and any additional address custom fields. Multiple job addresses per record require either a custom Address object in Twenty or a comma-joined string in a single address field.

Lead Perfection's multi-phone model (primary phone, AltPhone1, AltPhone2 with type labels) maps to Twenty People phone fields. Phone type labels that have no Twenty equivalent become a custom pick-list field on the People record to preserve the type attribution. All phone numbers transfer with their original formatting intact, and the custom pick-list maintains visibility into which number served which purpose in Lead Perfection.

Lead Perfection captures lead_source and sub_source as structured fields on prospects. Twenty has no native lead source field; these migrate as custom text or select fields (Lead_Source__c, Lead_Sub_Source__c) on the People object for reporting continuity and historical attribution. Pick-list values are recreated in Twenty to maintain consistent reporting segmentation across the migrated dataset.

Lead Perfection sales representative assignments (sales_person, assigned_rep) resolve by email match against Twenty workspace members. Unmatched reps are flagged before migration; records without a match assign to a fallback owner. The original rep name is preserved in a custom field for historical reference.

Any custom fields configured in Lead Perfection that have no direct Twenty equivalent (e.g., project_type, contract_type, coverage_area, insurance_claim_id) are created as custom fields in Twenty's Data Model before the migration runs. Field type mapping: text → text, number → number, pick-list → select, date → date.

Free-text notes from Lead Perfection transfer as Twenty Notes attached to the related People, Companies, or Opportunities record. Notes preserve the original body text and creation timestamp. Rich-text formatting in Lead Perfection notes is simplified to plain text during transfer since Twenty Notes supports plain text.

Lead Perfection file attachments on jobs or prospects re-upload to Twenty as file attachments on the related record. File size limits (Twenty has no explicit per-file limit but storage is workspace-dependent). Attachments that reference external URLs in Lead Perfection preserve the URL in a custom text field since Twenty does not auto-fetch linked files.