Migrate from Kartra to Odoo CRM

Kartra Contacts map directly to Odoo Partner records. Standard fields (name, email, phone, website, address) map to Odoo partner fields using XML-RPC string and char types. We use the partner's email as the external identifier for deduplication. Tags stored as comma-separated strings in the Kartra CSV are parsed into individual Odoo Tag records and linked via ir.attachment or a dedicated tag relation table. If the Kartra contact has a company_name value, we create a parent Partner with company_name and a child Partner record for the individual contact.

Kartra's five custom field types map to Odoo field types: input_field maps to char, text_area maps to text, drop_down maps to selection, radio_button maps to selection, and checkbox maps to boolean. We read the Kartra field schema via API during scoping to determine types and labels, then pre-create the corresponding fields in Odoo via Studio or XML definition before migration. Relational custom fields (e.g., a drop-down referencing another Kartra object) require Odoo many2one or many2many configuration during schema setup.

Kartra tags stored as comma-separated strings in the Contact CSV are split into individual tag values. Each tag becomes an Odoo res.partner.category record. We map the tag name directly and link it to the Partner via the category_id many2many relation. Note: tags applied retroactively (e.g., 'form completed') after the original contact creation date will migrate with the contact but the customer should verify whether Odoo's tag assignment logic meets their segmentation needs.

Kartra Lists are exported as comma-separated membership values per contact. We split list memberships into individual group assignments. If the customer used Lists for audience segmentation in Kartra, we create Odoo Partner Categories (tags) or configure Odoo Smart Groups with domain filters to replicate the segmentation logic. The customer chooses the target model during scoping.

Kartra Transactions export as a separate CSV with amount, product, date, and payment method. We map these to Odoo Sale Orders (if the transaction is an order) or Account Invoice records (if it is a completed payment). The Odoo CRM module links the sale order to the Partner record via partner_id. Transaction products require Odoo Product records to exist before order import; we create placeholder Product records during schema setup if they do not exist.

Kartra Subscription records (active, cancelled, paused) with start date and associated product map to Odoo Subscription records if the Odoo Subscription app is installed, or to linked Sale Orders if only the base CRM app is in scope. Subscription status (active, cancelled, paused) maps to Odoo subscription state values. Kartra does not export subscription revenue MRR/ARR; we note this as a data gap and document it in the migration inventory.

The Kartra CSV includes GDPR Status and GDPR Status Date fields per contact. These values migrate to Odoo partner fields. We recommend the customer verify consent records against their actual legal obligations in the destination jurisdiction, as Odoo may interpret consent states differently from Kartra. A custom partner field gdpr_consent_date__c is created to preserve the original Kartra GDPR status date.

Kartra Calendars (booking objects) with appointment names and configurations map to Odoo Calendar Events. Historical appointment records require separate export from Kartra and are not included in the standard Contact or Transaction CSV. We flag this gap and map any appointments found to Odoo calendar.event linked to the partner_id. The customer's Odoo calendar must be configured with the appropriate user attendees before migration.

If the customer used Kartra's Deal module (available on Silver/Growth and above), Deal records map to Odoo CRM Opportunities (crm.lead with type='opportunity'). Kartra Deal stages map to Odoo Stage values configured in the CRM pipeline. Deal amount, close date, and associated contact (partner) migrate to the Odoo opportunity fields. We create the Odoo pipeline stages during schema setup to match the customer's Kartra deal stages.

Kartra Owners (team members) referenced on Contact and Deal records are resolved by email against the Odoo User table. Any Kartra Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on migrated Opportunities uses the resolved User ID.

Affiliate sign-up events tracked in Kartra map to Odoo Partner records with a custom affiliate_type field, or to a dedicated affiliate partner category. If the customer uses Odoo Affiliation or a third-party affiliate module, we map the affiliate relationship accordingly. The customer specifies the target during scoping.

Kartra does not export membership access or course enrollment data in any standard CSV. This information is not available for migration unless the customer manually exported it or used behavioral tags to capture enrollment events. We audit the customer's tag taxonomy during scoping to identify whether any membership or course completion tags exist, and surface the gap in the migration inventory if no tag-based enrollment data is found.