Migrate from Kartra to Pipedrive

Kartra Contacts map to Pipedrive People. Standard fields (first_name, last_name, email, phone, address) map directly. We preserve the original Kartra contact creation date as a custom field kartra_created_date__c for audit and reporting. Kartra's GDPR Status and GDPR Status Date fields migrate to Pipedrive's opt_in_status and a custom gdpr_consent_date__c field. We export oldest-to-newest to preserve lead creation order and replay it in Pipedrive.

If Kartra contacts include a Company field, we map to Pipedrive Organization. The Organization is created before Person import so the org_id lookup is satisfied at insert time. Organizations without a company name in Kartra are created as single-person orgs in Pipedrive to avoid orphan records.

Kartra Transactions map to Pipedrive Deals. Transaction fields map as follows: amount becomes Deal value, product_name becomes Deal title (with transaction_id appended for uniqueness), transaction_date becomes expected_close_date, payment_method becomes a custom field, and transaction status (completed, refunded, pending) becomes Deal status. Kartra transactions without a linked contact are flagged for manual review before import.

Kartra Subscription records (active, cancelled, paused) map to Pipedrive Deals with a custom subscription_status__c field. Subscription start date and associated product/membership migrate as custom fields. Note: Kartra does not export subscription revenue MRR or ARR as a computed field; we extract what is available in the CSV and flag the gap.

Kartra tags stored as comma-separated strings in the CSV are parsed and split into individual Pipedrive tags. We use Pipedrive's tag creation API to upsert tags before attaching them to People and Deals. Tags that represent behavioral events (form completed, email clicked) without a corresponding record in Pipedrive are preserved as tags but noted as informational — Pipedrive does not have an equivalent behavioral event log.

Kartra list memberships export as comma-separated values per contact. We split list memberships and create corresponding tags in Pipedrive with a list_ prefix for discoverability. The customer chooses at scoping whether to use Pipedrive tags or to pre-create Person Groups in Pipedrive and map list memberships accordingly.

Kartra's five custom field types (input_field, text_area, drop_down, radio_button, checkbox) map to Pipedrive's text, varchar, int, double, date, datetime, enum, set, and bool types. We read Kartra's field schema during discovery to determine types before creating Pipedrive custom fields. Drop-down and radio_button fields in Kartra map to Pipedrive enum fields with the same picklist values preserved.

Kartra owner email references are matched to Pipedrive Users by email during migration. Owners without a matching Pipedrive User are placed in a reconciliation queue for the customer to provision before Person import. This is a common gap when migrating from Kartra because Kartra team members may not have been set up as Pipedrive users at the destination.

Kartra Calendar appointments (booking records) map to Pipedrive Activities. We map calendar name, appointment time, and attendee to a Pipedrive Activity with type=Meeting or type=Call. Historical appointment records require a separate Kartra export and are not included in the standard contact CSV; we flag this and include it in the scope if the customer requests it during discovery.

Kartra affiliate relationships tracked in the API events system map to Pipedrive as custom fields on Person (affiliate_id__c, affiliate_status__c) or as a Partner Organization type if the customer uses Pipedrive's partner management setup. We determine the strategy during scoping based on the customer's affiliate volume and whether they actively manage affiliate relationships in the CRM.

Kartra's GDPR Status field per contact migrates to Pipedrive's opt_in_status flag. GDPR Status Date migrates to a custom consent_date__c field. We preserve original values but recommend the customer verify consent records against their actual legal obligations in the destination jurisdiction, as Pipedrive may interpret consent states differently than Kartra's internal flags.