Migrate from User.com to Twenty CRM

User.com's Contact records map directly to Twenty's People object. Every User.com contact with an email, phone, user_id, last_heard (chat visitor), web push subscription, or FCM key is a billable contact and must be audited before migration to disclose the true record count. We export the full attribute profile including tags, segments, and custom properties, then map to Twenty People fields. Bool attributes export as f/t and require normalization to boolean values during loading. The Twenty People object must exist before any Opportunity import that references a person as a decision-maker or contact.

User.com Companies map directly to Twenty Companies. The company-contact association is preserved by resolving the Company foreign key on the migrated People record. Company domain, industry, size, and address attributes map to the corresponding Twenty Company fields. We validate that all referenced companies exist in Twenty before importing people records that carry a company association.

User.com Deals map to Twenty Opportunities. The deal stage maps to Twenty Opportunity stageName, deal value maps to amount, and the deal owner maps to the Twenty user by email resolution. Custom deal fields migrate to custom fields on the Opportunity object; we pre-create the Opportunity fields in Twenty Settings → Data Model before migration begins. Closed-won and closed-lost deal outcomes preserve as stage values.

User.com Events (calendar/activity events) split by event type: meeting-type events map to Twenty Task records with taskType=meeting, and informational events map to Note records linked to the parent People or Company record. We preserve the original event timestamp as the ActivityDate on Task and the createdAt timestamp on Note. Attendee lists migrate as comma-separated text fields or are omitted if the attendee count exceeds the reasonable field length for a CSV-mapped field.

User.com Activities (calls, emails, meetings, tasks, notes) map to Twenty Task records with the activity type stored in a custom taskType field. Call duration, disposition, and recording URL preserve as custom fields on the Task. Email body content migrates as Task description or as a linked Note attachment. We preserve the original activity timestamp as ActivityDate for timeline ordering.

User.com custom properties on contacts, companies, and deals require pre-creation in Twenty Settings → Data Model before CSV import. Choice and fixed-choice fields in User.com (now using {} bracket syntax) map to Twenty select or multiselect fields. Multi-checkbox properties map to Twenty multiselect fields. Date fields migrate in ISO 8601 format which Twenty accepts natively. We document every custom property and its recommended Twenty field type during scoping.

User.com tags associated with contacts and deals migrate to Twenty Topics with TopicAssignment records linking to the People or Opportunity. If the customer prefers a simpler model, tags map to a multi-select picklist custom field on the relevant object. We confirm the preferred tag strategy during scoping because User.com tags are flat while Twenty supports hierarchical topics.

User.com Segments are dynamic groups based on contact attributes and behavioral rules. We export the segment membership (the list of contacts currently in each segment) but not the segment definition, because dynamic re-evaluation must be recreated in Twenty using Twenty's filter and view system. We deliver a segment membership export as a CSV of People IDs per segment for manual recreation.

User.com automation sequences are not accessible via documented CSV or public API export. We explicitly exclude automation migration from scope. We recommend capturing screen recordings of all active automations before migration begins and deliver a written inventory of each automation's trigger, conditions, delays, and actions for the customer's admin to rebuild in Twenty's workflow system.

User.com chat transcripts and conversation history can be exported, but the exported format bundles conversation threads with contact records. We flatten conversation threads and re-associate them as Task records with taskType=chat on the related People record. Chat messages migrate as Task description with a timestamp prefix. If the customer uses User.com live chat as a support channel, the migrated tasks represent conversation history for customer relationship continuity.