Migrate from LeadPrime to Twenty CRM

LeadPrime Leads map directly to Twenty CRM Person records. The Person object in Twenty serves as the unified record for prospects and contacts, with a personType field distinguishing between individual contacts. We preserve Lead status, source, owner assignment, and any LeadFinder enrichment data (email, phone) as fields on the Person record. Standard fields (name, email, phone, source) map 1:1; custom fields require pre-creation in Twenty's schema before migration.

LeadPrime Contacts map to Twenty CRM Person records with personType set to contact. Where LeadPrime stores both a Lead and a Contact for the same individual, we consolidate into a single Person record, preserving both records' activity history and field data. The mapping uses email address as the deduplication key across both Lead and Contact sources.

LeadPrime Company records map directly to Twenty CRM Company. We preserve company name, industry, size tier, address, domain, and any custom fields. Company records are migrated before Person records so that the Company lookup relationship is satisfied at Person insert time. The Company domain field maps to Twenty's website field for dedupe matching.

LeadPrime pipeline configurations map to Twenty CRM Opportunity records grouped by pipeline name. Twenty does not have a native multi-pipeline UI equivalent to LeadPrime's pipeline selector, so each LeadPrime pipeline becomes a custom field on Opportunity (e.g., pipeline_name) or a tagged grouping. We document the full pipeline topology and stage names for the customer to configure Twenty views and filters that replicate the pipeline segmentation.

LeadPrime pipeline stages map to Opportunity stage values in Twenty. Stage names and ordering migrate as written configuration. Any stage-specific routing triggers in LeadPrime are documented as a list of conditions for manual rebuild in Twenty; Twenty has no native stage-triggered routing engine. Probability percentages per stage are recorded for the customer to apply as stage-based probability fields.

LeadPrime's Round Robin, Blind, Shark Tank, and Hybrid routing rules are stored as configuration. We export the full rule definitions (territory boundaries, rep capacity, daily caps, seniority weights, bucket assignments) as a written configuration document. Twenty has no native equivalent routing engine, so the customer implements ownership assignment through manual setup, custom GraphQL mutations, or a third-party routing extension. We do not migrate rules as executable code.

LeadPrime Users map to Twenty CRM WorkspaceMember records. We resolve by email match. Any LeadPrime User without a matching Twenty WorkspaceMember is held in a reconciliation queue for the customer's admin to provision before record import. Active and inactive status, role assignments, and team membership are preserved in custom fields or documented for manual re-setup.

LeadPrime call logs migrate as Twenty Timeline entries with type set to call. Call duration, disposition, and outcome transfer to custom Timeline fields. The activity is linked to the corresponding Person record via the PersonId relationship. Activity timestamps preserve the original LeadPrime creation date for timeline ordering.

LeadPrime email engagements migrate as Timeline entries with type set to email. Email subject, body, and direction (sent/received) transfer to Twenty's Timeline fields. The activity links to the Person record. Email attachments migrate as file records linked to the Timeline entry where the attachment model is supported in the target Twenty version.

LeadPrime meeting logs migrate as Timeline entries with type set to meeting. Start time, end time, location, and attendee list transfer to Twenty's Timeline fields. Attendees resolve to Person records via email match where Twenty supports attendee linking in the target version.

LeadPrime notes migrate as Timeline entries with type set to note. Note body transfers as rich text. The note links to the Person, Company, or Opportunity record depending on the original LeadPrime association. We resolve the relationship using the original record ID reference and the email-to-Person lookup.

LeadPrime custom fields on Leads, Contacts, and Companies are mapped to Twenty custom fields. We read the full field list during scoping, map each field type (text, number, date, picklist, checkbox) to the equivalent Twenty field type, and pre-create the destination schema in Twenty before migration. Fields without a direct Twenty equivalent are flagged for the customer to decide on a target type.