Migrate from Prophet CRM to Twenty CRM

Prophet Contacts map to Twenty People records. Prophet stores first name, last name, email, phone, address, job title, company association, and custom fields per department template. We extract all fields during the custom field audit phase and create matching custom fields in Twenty's Settings → Data Model before import. The Outlook bidirectional sync is frozen before extraction to prevent duplicate records post-import. Email addresses serve as the dedupe key during Twenty CSV import.

Prophet Company records map directly to Twenty Company records. Standard fields (company name, industry, address, website, employee count, revenue) export cleanly. Industry classification and employee count ranges from Prophet map to Twenty's industry and employeeCount fields, with format normalization applied where Prophet uses free-text. We pre-create any industry picklist values not present in the default Twenty workspace before import.

Prophet Opportunities map to Twenty Opportunities with name, value, close date, probability, owner, and pipeline stage. Stage assignments migrate as part of the record. We capture the full Prophet pipeline stage list during scoping and create matching stage values in Twenty's pipeline configuration before migration. Closed-won and closed-lost reasons from Prophet custom fields become Twenty custom fields on Opportunity.

Prophet pipeline stages are configurable per department and vary across organizations. We enumerate the complete stage list during the scoping audit, including stage names, probabilities, and which departments use which pipelines. Each stage maps to a Twenty Opportunity stage value, with probability percentages rounded to Twenty's allowed integer format.

Prophet Activities include email tracking, tasks, appointments, and call logs linked to Contacts and Opportunities. These map to Twenty Task records (for calls, tasks, and appointments) and Note records (for logged emails and text notes). Activity date and time are preserved in Twenty's ActivityDate field. There is no bulk export endpoint in Prophet, so we extract via OData pagination in batches, preserving the linked Contact and Opportunity references for reconstruction in Twenty.

Prophet departments are first-class objects with custom templates and configurable cross-department access. Twenty's permission model uses Workspace Members with object-level visibility rather than a department hierarchy. We evaluate the customer's department structure during scoping and recommend either a custom department field on each record (if departments represent reporting structures) or Workspace Member-based team segmentation (if departments represent access-controlled silos). The recommendation is documented and implemented as part of the schema pre-build.

Prophet supports custom fields on Companies, Contacts, and Opportunities with schemas that vary by department template. We conduct a mandatory custom field audit before migration, enumerating all field names, data types, and which departments use which templates. Every distinct custom field is created in Twenty's Settings → Data Model before the corresponding object import begins. Fields must exist in Twenty before the CSV import step; CSV import creates records only, not fields.

Prophet stores file attachments on Companies, Contacts, and Opportunities. We extract attachment metadata and file URLs from the OData export and upload files to Twenty's file attachment capability, linking each file to the parent record by resolving the target People, Company, or Opportunity ID in Twenty post-import.

Prophet Owners map to Twenty Workspace Members. We resolve owners by email match. Twenty's migration documentation explicitly requires that users exist in the workspace before importing records with owner references. Any Prophet Owner without a matching Twenty Workspace Member enters a reconciliation queue for the customer's admin to provision the account before record import resumes.

Prophet's Enterprise tier supports custom objects with department-scoped schemas. Twenty supports custom objects via its /metadata API with GraphQL schema generation. We pre-create the destination custom objects (including all custom fields, field types, and lookup relationships) before any data import. Twenty's schema must be deployed via the Settings → Data Model interface, and all fields must exist before CSV import begins.