Migrate from Workpex to Twenty CRM

Workpex Leads map to Twenty CRM People records. The Lead status field maps to the People record's display name and source tracking fields. We preserve the Workpex lead status and source attribution as custom fields in Twenty's data model during pre-creation. Since Twenty does not have a separate Lead object, unqualified prospects land in People alongside contacts, which is the expected behavior for Twenty migrations.

Workpex Contacts map to Twenty CRM People records, preserving the Contact-to-Lead association from Workpex. The contact name, phone, email, and address fields map directly to Twenty's standard People fields. Email addresses serve as the dedupe key during import to prevent duplicate People records.

Workpex Company records map directly to Twenty CRM Company records. The company name becomes the Company display name and domain information maps to the website field. Any custom fields on Workpex Companies are pre-created in Twenty's data model under Company before import.

Workpex Deals map to Twenty CRM Opportunity records. The deal name, amount, close date, and pipeline stage migrate as standard Opportunity fields. Workpex pipeline stages map to Twenty Opportunity stage values, and any custom pipeline stages are flagged for value-mapping review during scoping.

Workpex Tasks map to Twenty CRM Task records with Status, Priority, and due date preserved. Task assignments migrate by resolving Workpex owner IDs to Twenty workspace Members by email match. Open and closed status translates directly to Twenty's task completion state.

Workpex Follow-up Reminders are tied to Leads and Contacts and map to Twenty CRM Task records with the reminder date mapped to the Task due date and the reminder description mapped to the Task body. Since Twenty does not have a native Reminder object, this transform is the standard mapping pattern.

Workpex call metadata (duration, direction, timestamp, disposition) migrates to Twenty CRM Task records with TaskSubtype indicated as call-related. Call recordings are flagged as file attachments to be re-associated post-migration. We note that Twenty does not have a native call recording storage mechanism, so recording files require separate handling.

Workpex pipeline stages define the sales process for Deals and map to Twenty Opportunity stage values. We capture the stage ordering and any custom stage names during the pre-migration audit. Deprecated or custom stages are flagged for value-mapping review before import to ensure no stage data is silently dropped.

Workpex Users and Owners are mapped to Twenty CRM Members by email address. Any Workpex Owner without a matching Twenty Member goes to a reconciliation queue for the customer's admin to provision the user before record import resumes. This step is required before Deals, Tasks, and Activities can reference owners.

Workpex custom fields on Leads and Contacts are discovered during the scoping phase and pre-created in Twenty's Settings Data Model before any data import begins. Field types are mapped to their nearest Twenty equivalents. Any custom fields with incompatible data types are flagged for manual review. This step is mandatory because Twenty's import creates records, not fields.

WhatsApp marketing and message logs from Workpex export as Task or Note records in Twenty CRM depending on whether the interaction is time-stamped (Task) or free-text (Note). Rich media attachments may require separate handling as file links. We document the WhatsApp data structure found during scoping and map accordingly.

File attachments associated with Workpex Leads, Deals, or Tasks are exported and re-associated in Twenty CRM. Large files or unsupported formats are flagged for manual upload review. We verify file association by matching attachment record IDs to their parent record IDs in Twenty.