Migrate from Pro-Sales CRM to Twenty CRM

Pro-Sales CRM Contact records map to Twenty CRM's Person object. Standard fields (name, email, phone) map directly. Lifecycle stage from Pro-Sales CRM becomes a custom select field in Twenty since the standard field set is minimal out of the box. We inspect the source field list during discovery and create matching custom fields (e.g., jobTitle, department, source) before migration begins. Email is the primary deduplication key during import.

Pro-Sales CRM Company records map to Twenty CRM's Company object. The address, industry, and size fields in Pro-Sales CRM require custom field creation in Twenty before migration because Twenty does not include industry, employeeCount, or annualRevenue as standard fields. We create these fields during the schema pre-creation phase and then populate them from the Pro-Sales CRM export. Companies are imported before Persons so that the Person-Company relationship (workspaceMember) resolves correctly during Person import.

Pro-Sales CRM Deal records map to Twenty CRM's Opportunity object. The deal name, value, close date, and stage migrate directly. Pipeline stage names are customer-configured in Pro-Sales CRM; we extract the active stage configuration and create matching stage values in Twenty's Opportunities pipeline before migration. Stage probability percentages transfer to a custom field or to Twenty's stage probability if supported in the target workspace version.

Pro-Sales CRM allows custom stage names and probability weights per pipeline. We extract the full stage configuration (stage name, probability, order) and create a matching stage sequence in Twenty's Opportunities object. If the customer uses multiple pipelines in Pro-Sales CRM, we create Twenty workspaces or filter views per pipeline and document the mapping in the discovery output.

Pro-Sales CRM call logs migrate to Twenty Task records with the type set to Call. Call duration, disposition, and outcome transfer to custom fields on the Task. The associated Person or Company reference resolves via the email lookup performed during the Person and Company import phase. Activity timestamps are preserved to maintain the timeline ordering on the record.

Pro-Sales CRM email engagement records migrate to Twenty Task records of type Email. Email subject, body, and direction (sent/received) transfer to custom fields on the Task. The recipient and sender are resolved to the corresponding Person records via email address matching. If the source email body contains HTML, we strip to plain text for Twenty's field type compatibility.

Pro-Sales CRM meeting records migrate to Twenty Task records of type Meeting. Start time, end time, and location transfer to custom date and text fields on the Task. Attendee information resolves to Person records by email where attendees are present in the source data.

Pro-Sales CRM note records migrate to Twenty Task records of type Note. Note body transfers to a custom long-text field on the Task. The linked record reference (Person or Company) resolves via the lookup performed during the Person and Company import phase.

Pro-Sales CRM allows custom fields on Contact records. We inspect the full custom field list during discovery, create matching custom fields in Twenty's Person object schema (with type mapping: text to text, number to number, date to date, picklist to select), and then populate them during Person import. Multi-select picklists in Pro-Sales CRM map to Twenty multi-select fields if available, otherwise to text with comma-separated values.

Pro-Sales CRM allows custom fields on Deal records. We create matching custom fields in Twenty's Opportunity object during the schema pre-creation phase, type-mapped from the source field definitions. Custom fields with lookup references to Company or Contact records are migrated after all primary record imports complete so that the referenced record IDs are available for resolution.

Pro-Sales CRM assigns a single owner per Contact, Company, and Deal record. We extract the owner ID and email from each record and match against Twenty CRM's WorkspaceMember list by email. Any owner without a matching WorkspaceMember is flagged and reassigned to a designated fallback WorkspaceMember. The customer provisions any missing Twenty users before the production migration phase.

Pro-Sales CRM tag assignments on records migrate to a custom select or multi-select field in Twenty. The tag strings are preserved verbatim. If the customer has a large tag vocabulary (over 50 unique tags), we discuss whether to use a single multi-select field or split into multiple single-select fields for better filtering performance in Twenty views.