Migrate from Chakra Sales CRM to Twenty CRM

Chakra Sales CRM Contact records map directly to Twenty CRM Person records. Standard fields (name, email, phone, address) map 1:1. Custom Contact properties are captured during discovery and mapped against Twenty's standard Person fields or pre-created custom fields before the load phase. Owner assignment resolves by email match to Twenty workspace members.

Chakra Accounts map to Twenty Companies. The company name, domain, address, and industry fields map directly. Any custom Account-level fields require pre-creation in Twenty during the schema setup phase. Company is created before Person import so that the Person-Company relationship is satisfied at insert time.

Chakra Deals map to Twenty Opportunities. Deal name, amount, expected close date, and stage all map to corresponding Twenty Opportunity fields. Stage values require explicit mapping because Chakra stage names (e.g., Negotiation, Proposal Sent) may not match Twenty's default Stage picklist values. We document the full stage sequence during discovery and configure Twenty's Stage field before the Opportunity load.

Chakra Leads are top-of-funnel records with status, source, and qualification fields. Depending on the customer's use of Chakra's Lead object versus treating all prospects as Deals in a pipeline, we either map Leads to Twenty Persons with a lead_source__c indicator or evaluate Twenty's custom object support for a dedicated Lead record type. The split logic is designed during discovery based on the customer's existing Chakra workflow.

Chakra's pipeline stages are configured per-account via no-code setup and do not export as a schema artifact. We document the stage name, order, and probability percentages during the discovery call and configure Twenty's Stage picklist values and ordering to match before Opportunity import begins. If the customer uses multiple pipelines in Chakra, each maps to a separate Stage value set in Twenty.

Chakra Tasks map directly to Twenty Tasks. Due date, assignee, status, priority, and description transfer 1:1. Task associations to Contact, Lead, or Deal resolve to the migrated Person and Opportunity records using the ID mappings established during the Person and Opportunity load phases.

Chakra email activity associated with Contacts, Leads, or Deals migrates as Activity records in Twenty's timeline linked to the target Person record. Email content, direction (sent/received), and timestamp transfer. The activity ordering in Twenty's timeline preserves the original Chakra timestamp.

Chakra call logs migrate to Twenty Activity records with the call type indicator. Call duration, disposition, and any notes attached to the call record transfer as Activity fields. Recording URLs stored in Chakra may not export via the standard API and are flagged for supplementary file transfer if critical.

Meeting records in Chakra with date, duration, attendees, and location transfer to Twenty Activity records of the meeting type. Attendee resolution uses the email-to-Person lookup to link attendees to the correct Twenty Person records.

Chakra Notes attached to Contacts, Leads, or Deals migrate as Note records in Twenty, linked via the appropriate Person or Opportunity relationship. Note content and author transfer directly. Note timestamps preserve the original Chakra creation date for timeline accuracy.

File attachments linked to Chakra CRM records (proposals, signed documents, call recordings) are stored in Chakra's file layer and may not retrieve via the standard Cloud API. We audit attachment coverage during the pre-migration data audit. For records with critical attachments, we either request a manual export from the source account or perform a supplementary file transfer step, uploading to Twenty's file storage and linking to the target record.

Chakra's no-code custom field creation means field definitions do not export as a schema file. We perform a full custom field inventory during discovery, comparing source custom fields against Twenty's standard field list. Any fields without a direct match are pre-created in Twenty before the data load phase begins, with the correct field type (text, number, date, picklist, boolean, etc.) assigned to avoid import type errors.