Migrate from Star CRM to Twenty CRM

Star CRM Contact records map to Twenty's People object. We perform live schema discovery against Star CRM during scoping to identify actual field names (email, phone, address, name fields) since no public API spec exists. Custom contact properties identified during discovery map to custom fields that we pre-create in Twenty's Settings → Data Model before import. The primary email field on People serves as the dedupe key during insert.

Star CRM Company records map directly to Twenty's Company object. Company name becomes the Company name field, and domain or website maps to the domain field if present. Company is imported before People so that the People → Company relationship is satisfied at the moment of People insert. We resolve the association by matching People records to their parent Company by company name or a discovered foreign key.

Star CRM Deals map to Twenty's Opportunity object. Deal stage maps to the Opportunity stage field, and deal value maps to the amount field. Pipeline stages from Star CRM are mapped to Twenty's Opportunity stage values during the scoping call, since stage names and counts differ between platforms. Stage-specific probability and closed-won/closed-lost dates migrate to corresponding fields on Opportunity.

Each Star CRM pipeline's stages are mapped to Twenty Opportunity stage values. We capture the stage order and probability from Star CRM and reproduce it in Twenty's Opportunity pipeline configuration. Closed-won and closed-lost stage transitions are preserved to maintain historical pipeline integrity.

Star CRM Activity records (calls, emails, meetings, notes) map to Twenty Tasks and Notes. We infer the activity type from the source data during discovery and route records to the appropriate Twenty object. Task and Note records are linked to the parent People or Company by resolving the contact or company reference from Star CRM. Activity timestamps are preserved on the Twenty record's creation date or a dedicated activity-date field.

Where Star CRM distinguishes a Lead object from Contact, we export Leads separately and merge them into Twenty's People object. The original Star CRM Lead source or lead status is preserved as a custom field on the People record. We flag any Lead-specific properties during discovery that do not map directly to standard People fields for custom field creation in Twenty.

Star CRM User records (name, email, role) map to Twenty Members via email matching. We extract every distinct user referenced on Contact, Company, Deal, and Activity records and match by email against the Twenty Members list. Any Star CRM Owner without a matching Twenty Member goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Star CRM custom fields on any object require field-level mapping work. We read the observed source schema during discovery (via live API probing) and document all custom property names, data types, and sample values before mapping them to Twenty custom fields. Twenty custom fields must be created in Settings → Data Model before CSV import begins; the import creates records, not fields. We pre-create all required custom fields during the Twenty workspace setup phase.

Star CRM tags on Contacts or Deals transfer as label values. Multi-select tags may map to a Twenty custom field with multiple values or to a separate tagging configuration depending on the customer's preference. We preserve tag names and apply them consistently during import. The customer's admin chooses the tag strategy during scoping.

Star CRM exports attachments as individual files per record, not as a structured archive. We download all attachment files, build a manifest linking each file to its parent record ID (Contact, Company, or Deal), then re-associate them in Twenty during upload. This step adds time proportional to attachment volume. We handle both document attachments and inline email attachments from activity records.