Migrate from Kartra to HighLevel

Kartra Contacts map directly to GoHighLevel Contacts. Standard fields (first name, last name, email, phone, address) migrate to their GoHighLevel equivalents. Tags stored as comma-separated strings in Kartra are split into individual GoHighLevel tag records during import so they can trigger Workflows. Custom Field values map to GoHighLevel Custom Fields on the Contact object. GDPR Status and GDPR Status Date fields migrate as Contact custom fields; we recommend the customer verify consent validity against their legal obligations in the destination jurisdiction.

Kartra Companies map to GoHighLevel Accounts. The Kartra company name and domain become the Account name and website. We use the company domain as a dedupe key during import to prevent duplicate Accounts. Account is created before Contact import so the lookup relationship is satisfied at the moment of Contact insert. If the customer uses Kartra's agency sub-account structure internally, we discuss whether those map to GoHighLevel sub-accounts or are flattened into Account records.

Kartra Deals map to GoHighLevel Opportunities. The Kartra deal name, amount, stage, and close date migrate to GoHighLevel Opportunity name, amount, pipeline stage, and close date. We pre-create the GoHighLevel pipeline and stage values to match the Kartra pipeline structure before migration. Deal owner from Kartra resolves to a GoHighLevel user by email match.

Kartra tags are stored as comma-separated strings in the Contact CSV export. We parse and split each tag into an individual GoHighLevel tag record at import time. Individual tags in GoHighLevel can trigger Workflow automations, making the tag split essential for post-migration automation. We also inventory tags applied at the list, company, and deal level in Kartra for customers who want to preserve segment-level tagging logic.

Kartra custom fields (input_field, text_area, drop_down, radio_button, checkbox) are exported in the Contact CSV and read from Kartra's field schema. We create matching GoHighLevel Custom Fields on the Contact object with equivalent field types before import. Drop-down and radio-button fields require a value mapping step; checkbox fields map to GoHighLevel's boolean field type.

Kartra Lists are exported as comma-separated values per contact. We split list memberships into individual GoHighLevel Smart List memberships during import. If the customer has a large number of Lists, we discuss whether to map them as GoHighLevel Smart Lists (contact-filtered views) or as Tags for simpler Workflow triggering. GoHighLevel does not have a native List object equivalent, so list membership logic is reconstructed using Smart List filters or tag-based segmentation.

Kartra Transactions export as a separate CSV and map to GoHighLevel Opportunity records with transaction-level detail (amount, product name, transaction date, payment method, status). We create a dedicated pipeline in GoHighLevel for historical transactions so they do not mix with active sales Opportunities. Total spend per contact can be derived from the transaction history and stored as a custom field for segmentation. Kartra does not export subscription revenue totals separately from individual transaction records.

Kartra Subscriptions export separately from Contacts. Subscription status (active, cancelled, paused), start date, and associated product or membership map to GoHighLevel Opportunity records or a dedicated Subscription custom object depending on the customer's reporting needs. If the customer relies on subscription MRR tracking, we recommend a custom object with fields for plan name, status, start date, and renewal date rather than conflating subscriptions with transactional Opportunities.

Kartra memberships and course enrollments do not export as structured data. GoHighLevel has no native membership builder — this is a significant functional gap that requires a separate rebuild strategy. We export whatever membership data is available in Kartra's behavioral export (if tag-based triggers captured access events) and document the access levels and course structure so the customer can decide whether to rebuild inside GoHighLevel's membership workaround, use a third-party integration, or keep the membership content in Kartra as a connected platform.

Kartra Calendars map to GoHighLevel Calendars. Calendar names, availability windows, and booking configurations migrate as GoHighLevel Calendar resources. Historical appointment records require a separate Kartra export and can be imported into GoHighLevel as Opportunities or Tasks depending on the customer's reporting workflow. If the customer uses Kartra's calendar for client-facing booking, we recommend testing the full booking flow in GoHighLevel before decommissioning Kartra.

Kartra affiliate relationships export as events in Kartra's API events system or as tag-based records. We map affiliate IDs, commission rates, and referral source data to Contact-level custom fields in GoHighLevel. GoHighLevel does not have a native affiliate management object on the Starter or Unlimited plans, so the affiliate data lives as contact attributes. If the customer needs a dedicated affiliate tracking workflow, we recommend a custom object with lookup to Contact.