Migrate from Kartra to Twenty CRM

Kartra Contacts (renamed from Leads in October 2024) map directly to Twenty CRM Person records. Standard fields (firstName, lastName, email, phone, address) map cleanly to Twenty's Person object fields. We export oldest-to-newest to preserve creation-order timestamps, which become the createdAt value on each Person record. The Kartra GDPR Status field maps to a custom field on Person. Contacts without email are flagged during profiling and held in a reconciliation queue.

Kartra Company records map to Twenty CRM Company. The company name becomes the Company name field. We run a dedupe check on companyName before import to catch duplicate Kartra companies that represent the same business. Companies are imported before People so that the Company-Person relationship (Company name on Person) can be resolved at insert time.

Kartra supports five custom field types: input_field, text_area, drop_down, radio_button, and checkbox. We read the Kartra field schema during scoping to determine types, then pre-create matching custom fields in Twenty via Settings → Data Model before migration begins. Drop-down and radio_button types become Twenty Select fields; checkbox becomes a Boolean; text_area becomes a Long Text field. API field names must be set explicitly on Twenty custom fields during creation for import compatibility.

Kartra stores tags as comma-separated strings per contact in the CSV export. We parse and split these into individual tag values, then create corresponding tag records in Twenty CRM's workspace. Each migrated Person receives tag associations linked to its record. Note: retroactive tags (e.g., 'form_completed') that were not set up in Kartra are absent from export and cannot be recovered. We probe the customer's tag taxonomy during scoping to identify which behavioral events were captured versus which are permanently absent.

Kartra Lists are exported as comma-separated values per contact. We split list memberships into individual workspace or segment associations in Twenty CRM. If the customer used lists for audience segmentation in Kartra's email marketing, these translate to Twenty workspace-level tag segments. List-based marketing segmentation that drives Kartra email campaigns must be rebuilt as Twenty Workflow trigger conditions post-migration.

Kartra Transactions export as a separate CSV from contacts. We map transaction amount, product name, date, and payment method to a Twenty CRM Opportunity record. The Opportunity name is derived from the Kartra product name or a transaction reference. Transaction date becomes the Opportunity createdAt; amount becomes the Opportunity amount. Note: Kartra does not export lifetime value or total spend aggregates — only per-transaction records. Subscription transactions migrate with status (active, cancelled, paused) mapped to Opportunity stage or a custom subscription status field.

Kartra Subscription records export separately from contacts and include status, start date, and associated product. We map active subscriptions to Opportunity records with a subscription-specific stage, or to a custom Subscription object if the customer requires recurring revenue tracking. Cancelled and paused subscriptions map to a separate stage. Kartra does not export subscription MRR or ARR values — only the product association and status.

Kartra Calendar bookings are separate from the contacts export. We map calendar names and booking metadata to Twenty CRM Task or Event records linked to the Person. Historical appointment records require a separate Kartra export and are not included in the standard contacts CSV. If no historical appointment export exists, appointment history is absent from the migration.

Affiliate sign-up events tracked in Kartra's API events system map to a custom Affiliate or Partner object in Twenty CRM. We create the custom object schema during migration setup, then populate affiliate relationships from Kartra's events data where available. Standard Kartra exports do not include affiliate commission history.

Kartra Sequences are multi-step email automation flows with conditional branching, delays, and action triggers. This automation logic does not exist as a data file that can be exported — only the contacts enrolled in sequences are present in the contacts export. We do not migrate sequence logic. We deliver a written inventory of every active Kartra Sequence (step count, triggers, conditions, and actions) for the customer's team to rebuild as Twenty Workflows post-migration.