Migrate from Prospect CRM to Twenty CRM

Prospect CRM Contacts map directly to Twenty CRM Person records. Standard fields (firstName, lastName, email, phone, address) map 1:1. Custom contact fields migrate as custom fields on the Person object. We preserve the RFM segmentation value (Recency, Frequency, Monetary tier) as a custom picklist field rfm_segment__c on Person. The contact's linked Company record is resolved via the Person's companyId lookup before insert to avoid orphaned relationships.

Prospect CRM Company records map directly to Twenty CRM Company. Company name, domain, industry, employee count, and address fields migrate 1:1. Custom company-level fields migrate as custom fields on the Company object. Company is imported before Person so that the companyId lookup is satisfied at the moment of Person insert.

Prospect CRM Deals map to Twenty CRM Opportunities. Deal name, value, stage, close date, owner, and linked Company and Contact references migrate directly. Pipeline stage names from Prospect CRM are mapped to Twenty's Opportunity stage values explicitly since stage IDs are not portable across platforms. We preserve any custom deal properties as custom fields on Opportunity.

Prospect CRM's custom pipeline stages (e.g., 'Quoted', 'Awaiting Stock', 'Negotiation') require explicit mapping to Twenty's Opportunity stage values. We capture stage order and probability percentages from Prospect CRM and configure the corresponding stages in Twenty during schema setup. The stage mapping document is delivered as part of the migration scope so the customer can validate stage semantics before cutover.

Prospect CRM's Problem Pipelines (used for tracking delivery issues, returns, and complaints) is a non-standard object with no direct Twenty CRM equivalent. We extract Problem records with Status, Outcome, and linked Customer fields, then map them to Twenty Tasks with a custom problem_type__c label. For high-volume problem sets (over 500 records), we create a custom Problem object in Twenty with its own fields rather than overloading the Task object. The mapping decision is made during scoping based on record count and expected future volume.

Prospect CRM Product catalog data (SKU, name, description, pricing) migrates to Twenty's Product object. The stock-aware flag and live inventory linkage from Prospect CRM are non-transferable; we document them as a manual checklist item for the customer to re-implement via Twenty's API or a third-party inventory integration.

Prospect CRM Activity history (notes, calls, tasks) migrates as Twenty CRM Tasks. Activity type labels from Prospect CRM are mapped to Twenty Task category fields. Call duration and disposition from Prospect CRM migrate to custom fields on the Task record. Activity timestamps are preserved to maintain the historical timeline. Activity linking (which record the activity belongs to) is resolved via email match to Person or Company during migration.

RFM (Recency, Frequency, Monetary) segmentation data is a Prospect CRM-specific classification stored per contact. We export the segment assignment (e.g., 'Best Customer', 'At Risk') as a custom picklist field rfm_segment__c on Twenty's Person object. The segment calculation logic (which defines the Recency, Frequency, and Monetary thresholds) does not migrate as code; we document the customer's current thresholds for manual re-implementation in Twenty if needed.

Custom fields on Prospect CRM Contacts, Companies, and Deals migrate as custom fields in Twenty CRM on the equivalent objects. We capture field type (dropdown, date, number, text) to ensure the correct field type is created in Twenty. Validation rules and conditional logic on custom fields in Prospect CRM do not transfer; these are documented for manual re-implementation in Twenty's field settings.

Prospect CRM User records (names, email addresses, role assignments) migrate as Twenty CRM WorkspaceMembers. We resolve by email match. Any Prospect User without a matching Twenty workspace account is held in a reconciliation queue for the customer's admin to provision before record import completes. Role assignments are documented for manual configuration in Twenty's workspace settings.

File attachments linked to Prospect CRM Deals, Contacts, and Problems are not included in CSV exports from Twenty's migration tooling. We flag attachment count and size during scoping, provide a file list with source URLs where available, and deliver a checklist for manual re-upload to Twenty's document storage or a linked file storage service. This limitation is documented in Twenty's own migration documentation.