CRM migration
Field-level mapping, validation, and rollback between Kartra and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Kartra
Source
Nutshell
Destination
Compatibility
7 of 8
objects map 1:1 between Kartra and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Kartra and Nutshell serve fundamentally different business models. Kartra bundles email marketing, funnels, memberships, checkout, and a basic CRM under one subscription, charging per contact. Nutshell is a dedicated sales CRM with pipeline management, engagement tracking, and per-user pricing. Teams move from Kartra to Nutshell when they want a purpose-built CRM rather than a jack-of-all-trades platform, and they need the contact and engagement data they have accumulated to transfer intact. The migration challenge is that Kartra has no bulk API — all data exits as CSV via the web UI — while Nutshell accepts import via REST API and a native Import2 connector. We extract Kartra contacts, transactions, tags, and custom fields, normalize the CSV, and ingest into Nutshell using the appropriate import method. We flag that Kartra behavioral data (form completions, survey results, membership access) does not export unless the account was configured to apply a tag on each event, and we audit the contact list before migration to surface inactive and bounced records that may trigger a Nutshell seat or pricing adjustment. Sequences, automations, and funnel logic do not migrate; we deliver a written inventory for the customer to rebuild in Nutshell or another automation tool.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Kartra object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Kartra
Contact (formerly Lead)
Nutshell
Person
1:1Kartra Contacts (renamed from Leads in October 2024) map to Nutshell Person records. Standard fields — first name, last name, email, phone, address — map cleanly. We export the Kartra CSV oldest-to-newest to preserve lead creation order and replay it as the person.joined_at timestamp in Nutshell. GDPR Status and GDPR Status Date from the Kartra CSV map to Nutshell's subscription tracking fields. The Kartra contact ID is preserved in a custom field for cross-reference during reconciliation.
Kartra
Company
Nutshell
Company
1:1Kartra does not have a native Company object, but contacts may contain a company name field. We extract company names from the Kartra contact CSV, deduplicate them, create Nutshell Company records, and link Person records to the corresponding Company via the person.company_id lookup. If the Kartra export does not contain company data, we flag this during scoping and the customer decides whether to populate it from another source or leave persons unlinked.
Kartra
Tag
Nutshell
Tag
1:1Kartra Tags are stored as comma-separated strings within the contact CSV. We parse and split them into individual Tag records in Nutshell, then create TagAssignment records linking each tag to the corresponding Person. We audit the customer's tag taxonomy during scoping to identify behavioral tags (form completed, webinar registered, membership accessed) that indicate engagement data that may otherwise be absent from the export. Tag names are normalized to lowercase with hyphens replacing spaces for consistency.
Kartra
List
Nutshell
List
1:1Kartra Lists are exported as comma-separated values per contact. We split list memberships and create Nutshell List records, then assign each Person to the relevant lists via List membership. If Nutshell Lists do not match the customer's segmentation logic, we document the gap and propose a List-to-Segment reconfiguration before migration so the segmentation model is intentional in the destination.
Kartra
Custom Field
Nutshell
Custom Field
1:1Kartra supports five custom field types: input_field (text), text_area, drop_down, radio_button, and checkbox. We read the Kartra field schema via the Kartra UI to determine types, then create matching Nutshell custom fields on the Person, Company, or Lead object before import. Drop-down and radio button fields map to Nutshell dropdown or multi-select picklist fields with the same value options. Checkbox fields map to Nutshell checkboxes. Note: Kartra's standard contact fields and custom field labels must be reviewed manually because field names in the CSV export header row may differ from the display labels.
Kartra
Transaction
Nutshell
Activity (Log Entry)
1:1Kartra exports transactions as a separate CSV from the contacts export. We map transaction fields — amount, product name, purchase date, and payment method — to Nutshell Activity log entries attached to the corresponding Person. The Kartra transaction ID is preserved in a custom field on the activity for reconciliation. Note: Kartra does not export total customer spend as a single field; if the customer requires a lifetime value calculation in Nutshell, we compute it from the transactions CSV and write it to a custom person.lifetime_value__c field.
Kartra
Subscription
Nutshell
Activity (Log Entry)
1:1Kartra Subscription records (active, cancelled, paused status with start date and associated product or membership) export separately from contacts. We map subscription status and start date to Nutshell Activity log entries on the Person record. Subscription revenue and MRR figures are not available in the Kartra export. We document this gap and recommend that the customer track subscription status manually in Nutshell or via a third-party integration if real-time subscription data is required.
Kartra
Affiliates
Nutshell
Tag or Custom Field
lossyKartra affiliate sign-up events are tracked via tags or the API events system. We map affiliate relationships to a dedicated Nutshell tag (e.g., affiliate) or a custom person.affiliate_status__c dropdown field, depending on whether the customer needs to track affiliate status as a label or a structured field. If the customer requires a full affiliate tracking system, we recommend a dedicated affiliate management tool post-migration.
| Kartra | Nutshell | Compatibility | |
|---|---|---|---|
| Contact (formerly Lead) | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Tag | Tag1:1 | Fully supported | |
| List | List1:1 | Fully supported | |
| Custom Field | Custom Field1:1 | Fully supported | |
| Transaction | Activity (Log Entry)1:1 | Fully supported | |
| Subscription | Activity (Log Entry)1:1 | Fully supported | |
| Affiliates | Tag or Custom Fieldlossy | Mapping required |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Kartra gotchas
Behavioral history is absent from Kartra exports unless tags were pre-set up
Contact-based pricing requires pre-migration record audit
No bulk or programmatic API for extraction
Sequences, automation logic, and workflows cannot be exported
GDPR status fields export but require manual review at destination
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Pre-migration profiling and scoping
We request read-only access to the Kartra account or a full CSV export from the customer. We audit the contact list for total count, bounced records, duplicates, and records with no email address. We review the Kartra custom field schema, tag taxonomy, list memberships, and transaction export. We identify behavioral tags (form completed, webinar registered) that indicate engagement data that may otherwise be absent. We deliver a written scoping document with the clean record count, objects available for migration, objects not available, and an estimated timeline. The customer approves scope before work begins.
CSV extraction and multi-file reconciliation
We guide the customer through the Kartra CSV export process for contacts, transactions, and subscriptions. For accounts with more than 10,000 contacts, we chunk the export into sequential batches using Kartra's date-range filters to avoid UI timeouts. We download the transaction CSV separately and cross-reference it against the contact list using email as the dedupe key. We flag any contact in the transaction CSV that does not appear in the contact export and include it as a supplemental record. The output is a unified, deduplicated contact dataset with transactions joined and tag/list fields parsed into individual values.
Nutshell schema preparation and custom field creation
We create all required Nutshell custom fields before import, matching Kartra field types to Nutshell field types. Drop-down fields get pre-populated value lists from the Kartra schema. Tags are created as Nutshell Tag objects in advance of import. Lists are created as Nutshell List objects. We verify the Nutshell account has sufficient user seats and storage before proceeding. If the customer has a Nutshell sandbox or trial account, we run a test import there first to validate field mapping before production import.
Production import with reconciliation
We import contacts (as Nutshell People) into Nutshell via the Import2 connector or REST API, preserving the Kartra contact ID in a custom field for cross-reference. We import transactions and subscriptions as Nutshell Activity log entries attached to the corresponding Person records. We apply tags and list memberships as separate post-import steps. After each import phase, we reconcile the Nutshell record count against the expected count from the scoping document. Any records that fail import (due to missing required fields, invalid email format, or API errors) are logged to a skipped-records report for customer review.
Cutover, final delta, and cleanup handoff
We freeze writes to the Kartra account during the cutover window, run a final delta export of any records modified since the initial export, and import the delta into Nutshell. We deliver a reconciliation summary comparing the Kartra source record counts to the Nutshell destination record counts for each object. We remove the Kartra contact ID custom field if the customer does not want to retain it. We do not cancel the Kartra account inside the migration scope; the customer manages account cancellation separately after verifying the Nutshell data is complete.
Platform deep dives
Kartra
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Kartra and Nutshell.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Kartra: Hardcoded ceiling of 20 inbound API calls per second per Kartra App..
Data volume sensitivity
Kartra doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Kartra to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Kartra to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Kartra
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.