Migrate from karmaCRM to Twenty CRM

karmaCRM Contacts map to Twenty CRM People. The mapping requires resolving the karmaCRM company association before People import because Twenty uses separate People and Company objects. We extract the company_name or company_id from each karmaCRM Contact during export, hold it in a staging lookup, then link each People record to the resolved Company record in Twenty via the PersonCompany relationship. Email, phone, address, and any custom field values transfer as typed field values against the People object.

karmaCRM Companies map directly to Twenty CRM Companies. The company name, domain, address fields, and custom field values transfer as written. Twenty requires Companies to exist before People are imported if linking is required, so we sequence Company records first in the migration run order. The domain field from karmaCRM becomes the Company domain in Twenty for deduplication and enrichment.

karmaCRM's inline company association on a Contact record becomes a lookup in Twenty CRM. We perform a two-pass extraction: first pass exports all karmaCRM Companies and creates Twenty Companies, second pass re-queries karmaCRM Contacts with their company association and links each to the newly created Twenty Company ID via PersonCompany. Records where the karmaCRM company field is empty create People with no Company link, which is valid in Twenty.

karmaCRM Deals map to Twenty CRM Opportunities. The deal name becomes Opportunity name, deal value maps to the amount field, and deal stage maps to Opportunity stage with a customer-supplied stage value mapping document. The karmaCRM deal owner (assigned user) resolves to the matching Twenty User by email during owner reconciliation. Closed-won and closed-lost statuses carry over with their original timestamps preserved as Activity records.

karmaCRM Tasks map to Twenty CRM Tasks with due date, status, priority, and linked contact or company associations preserved. The linked record reference (contact_id or company_id) resolves to the equivalent Twenty People or Company ID after the lookup pass completes. Task body and description transfer as rich text. Completed status maps directly; open tasks carry over as pending with their original due dates.

karmaCRM Events map to Twenty CRM Activity records with type=Event. Each event record generates one Activity entry plus one EventRelation record per attendee. The event title, start and end timestamps, location, and description transfer directly. If karmaCRM attendees include external contacts, we create People records for them first before creating the EventRelation entries. Duration is computed from start and end timestamps at migration time.

karmaCRM Users and team members map to Twenty CRM Users. We extract user name, email, and role from karmaCRM and create matching User records in Twenty before any other object migration begins because OwnerId references on Deals, Tasks, and Events require a valid User to exist at import time. The karmaCRM role label maps to a Twenty workspace Role with the closest permission equivalent; the customer reviews and adjusts role permissions in Twenty Settings after migration.

karmaCRM supports fully customizable fields across screens and object types. Custom field definitions and values from karmaCRM migrate as freeform name-value pairs. Twenty CRM requires custom fields to be created in Settings Data Model before any CSV import because the CSV import creates records only, not fields. We extract the full custom field schema from karmaCRM, create matching custom fields in Twenty for each object, then migrate values as field data during the record import pass. Field types are approximated to the closest Twenty native type (text, number, date, select).

karmaCRM stores files and attachments linked to contacts, companies, and deals, but the platform backup and API documentation do not describe a programmatic attachment export path. We cannot migrate attachments via API or CSV. We produce a written inventory of all karmaCRM attachments with their parent record reference and suggested re-upload path in Twenty. The customer re-uploads attachments post-migration using Twenty's built-in file upload on each record.

karmaCRM tags applied to Contacts and Companies migrate as a custom multi-select text field in Twenty CRM. We extract the full tag vocabulary from karmaCRM, create a multi-select field on the People and Company objects in Twenty's data model settings, then map tag associations as comma-separated values in the custom field. The customer chooses whether tags on People and Company use a shared field or separate fields during scoping.

karmaCRM email campaign records on Pro and Premium tiers include audience lists, subject lines, send dates, and open or click statistics. We import campaign metadata as a written inventory document rather than as records in Twenty because Twenty does not have a native email campaign or engagement studio engine. Subject lines and send dates are preserved for reference; the customer rebuilds campaign logic in an external email tool or waits for Twenty's campaign features to reach feature parity.

karmaCRM integrates with Google Calendar, Google Contacts, and MailChimp via OAuth tokens and embedded iframe configurations that do not transfer between platforms. We document which integrations are active in karmaCRM during discovery and deliver a written integration map listing each tool, the authentication method used, and the recommended reconnection path in Twenty or an equivalent external tool. No OAuth tokens, connected account states, or API key configurations migrate.