Migrate from Kartra to Salesforce Sales Cloud

Kartra Contacts map to Salesforce Contact as the primary record. Standard fields (FirstName, LastName, Email, Phone, MailingAddress) migrate directly. We export oldest-to-newest to preserve lead creation order using Kartra's createdate field. GDPR Status and GDPR Status Date from Kartra map to custom Salesforce fields for compliance audit. Note: Salesforce Contact requires either a LastName or CompanyName; Kartra records without a last name require a name-splitting transform during the extract phase.

Kartra company data (if present on contact records or as a separate company export) maps to Salesforce Account. The Kartra company name becomes Account Name; the company domain becomes the Website field and serves as the dedupe key during import. Account is created before any Contact import so that the AccountId lookup is satisfied at the moment of Contact insert.

Kartra supports five custom field types: input_field, text_area, drop_down, radio_button, checkbox. We read the Kartra field schema via the UI export to determine types, then create equivalent Salesforce custom fields before migration. Text areas map to Salesforce Long Text Area; drop-down and radio_button map to Picklist or Multi-Select Picklist depending on cardinality; checkboxes map to Checkbox. Input fields with no type spec are mapped as Text. All custom fields are created in the Salesforce Sandbox first and validated before production deployment.

Kartra Tags are stored as comma-separated strings in the CSV export. We parse and split them into individual values and map them to a Salesforce multi-select picklist field on Contact (e.g., kartra_tags__c). If the customer has more than 500 distinct tags, we recommend mapping the top 100 by frequency to the multi-select picklist and documenting the remainder as a separate text field for manual cleanup. Tags applied retroactively (e.g., form completed tags) reflect the tag name only, not the event that triggered it.

Kartra Lists are exported as comma-separated membership values per contact. We split list memberships into individual Salesforce Campaign membership records (CampaignMember with Status = Responded) or Public Group membership depending on whether the list represents a marketing audience or an operational segment. The customer chooses the strategy during scoping.

Kartra Transaction records (amount, product, date, payment method) map to Salesforce Opportunity if the transaction represents a sales deal. The Kartra transaction amount becomes Opportunity Amount; the product name becomes Opportunity Name or a custom field; the transaction date becomes CloseDate. If the customer uses Kartra's product-catalog features alongside transactions, we map Product2 and OpportunityLineItem. Total spend is explicitly NOT exported by Kartra and therefore cannot migrate.

Kartra Subscription records (status, start date, associated product/membership, recurring amount) map to Salesforce Opportunity with custom fields capturing subscription-specific data. Kartra does not export subscription revenue run rate or MRR; we map what is present. Subscription status (active, cancelled, paused) migrates to a custom picklist field.

Affiliate sign-up events tracked in Kartra's events system can be mapped to a Salesforce custom Account (for partner organizations) or a custom Affiliate__c object. Tag-based triggers used to track affiliate activity migrate as tag values on the corresponding Contact or Account record.

Kartra Calendar booking records can be mapped to Salesforce Event. Historical appointment records require a separate export and are not included in the standard contact CSV. We map calendar name, booking date, and attendee email where present in the export. Note: Kartra does not export a complete calendar history by default.

Kartra does not export membership access or course enrollment data in any standard CSV export. This information is not available for migration. If the customer's Kartra account used tags to track membership access (e.g., 'member_gold', 'course_completed'), those tag values migrate to the Contact record as part of the tag mapping. The actual membership access configuration must be rebuilt in Salesforce or a complementary platform post-migration.

Kartra Sequences are multi-step email automation flows with conditional branching, delays, and action triggers. This workflow logic does not exist as a data file that can be exported. Only the contacts themselves move. We deliver a written inventory of every active Kartra Sequence with its trigger, steps, and conditions so the customer's admin can rebuild them in Salesforce Flow, Salesforce Sales Engagement (if licensed), or a third-party cadence tool post-migration.

Form definitions and survey questions are not exported via Kartra's standard CSV. Form completion and survey response data is absent from the export unless each completion triggered a tag. Form structure and logic must be rebuilt at the destination using Salesforce Web-to-Lead, Experience Cloud forms, or a third-party form tool. Completion counts and behavioral signals can be approximated via the tag inventory if tags were pre-configured for each form event.