Migrate from Kartra to Microsoft Dynamics 365 Sales

Kartra Contacts map to Dynamics 365 Contact records, with Company data mapped to a pre-created Account. We extract the company_name and company_phone fields from the Kartra CSV and create Account records first so that Contact.AccountId is resolved at insert time. If the Kartra contact has no associated company, we create a single-person Account or use a Household pattern depending on the customer's preference. Original contact creation dates migrate to Contact.CreatedOn for timeline audit.

Kartra Companies (if present as a separate export) map directly to Dynamics 365 Account. The Kartra company name becomes Account.Name, website becomes Account.Website, and any custom company fields map to Account custom fields. We deduplicate by name and domain during the transform phase. Account is the parent of Contact and is inserted before Contact to satisfy the required AccountId lookup on Contact.

We read Kartra's field schema via the Kartra UI during scoping to determine each custom field's type. Text inputs and text areas map to Dynamics 365 Text fields (max 255 or 16,000 characters). Drop-down and radio-button fields map to Picklist or Option Set fields with the Kartra options added as Dynamics 365 labels. Checkbox fields map to Two Option (boolean) fields. We create the custom fields in Dynamics 365 before migration and map them during the CSV transform.

Kartra Tags are stored as comma-separated strings in the CSV export. We parse and split them into individual tag values. Tags used for contact classification migrate to a Dynamics 365 multi-select picklist on Contact. Tags used for content or campaign classification migrate to Dynamics 365 Topics with TopicAssignment records linked to the Contact. The customer chooses tag strategy during scoping.

Kartra Lists are exported as comma-separated membership values per contact. We split list memberships into individual Dynamics 365 Marketing List records and populate the list membership via the ListMember entity. If the destination Dynamics 365 environment includes Dynamics 365 Marketing, we create segments; if not, we create static Marketing Lists within Sales and populate membership.

Kartra Transactions export as a separate CSV with transaction ID, amount, product, date, and payment method. We map transactions to Dynamics 365 Opportunity records with the Transaction Date mapped to Opportunity.CloseDate, Amount mapped to Opportunity.Amount, and the product name mapped to an OpportunityLineItem. Transaction status (completed, refunded, disputed) maps to Opportunity.StageName with a custom closed-won or closed-lost reason. For subscription-type transactions, we map to a custom Subscription entity if the customer has one configured.

Kartra Subscription records export separately with status (active, cancelled, paused), start date, and associated product. We map active subscriptions to Dynamics 365 Opportunity records with a custom subscription_status__c field and renewal date mapped to Opportunity.CloseDate. Cancelled and paused subscriptions migrate to a custom subscription_history__c field on the Contact for audit rather than as active Opportunities.

The Kartra CSV export includes GDPR Status and GDPR Status Date fields per contact. We map these to the Dynamics 365 consent tracking fields or a custom msdyn_gdprstatus__c field on Contact. We recommend the customer verify consent records against their actual legal obligations in the destination jurisdiction, as Dynamics 365 may interpret consent states differently than Kartra.

Kartra affiliate relationships are tracked via tags and the affiliate system. We map affiliate sign-up events to a custom affiliate_id__c field on Contact or a custom Affiliate entity with a lookup to Contact. The specific Kartra affiliate tracking fields determine the final mapping during scoping. We do not migrate affiliate payout history or commission data.