---
title: "Kartra to HubSpot Migration: Field Mapping & Rollback"
description: "Migrate Kartra to HubSpot with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/kartra/to/hubspot"
---

# Kartra to HubSpot migration

Moving from Kartra to HubSpot CRM consolidates your marketing automation, membership, and sales data into HubSpot's unified contact-object model. FlitStack AI maps every Kartra lead property, custom field, tag, and list to HubSpot contacts, companies, deals, and custom properties — preserving original create dates, lifecycle transitions, and association chains so your HubSpot reporting reflects the full customer journey from day one.

Short answer

FlitStack AI migrates contacts, companies, contact + deals, hubspot lists and hubspot contact properties from Kartra to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 25,000 records with under 30 custom fields.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See the field mapping →](https://flitstack.ai/migrations/crm/kartra/to/hubspot#field-mapping)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Kartra ![](https://flitstack.ai/platforms-trim/kartra.webp)

Destination HubSpot ![](https://flitstack.ai/platforms-trim/hubspot.webp)

Contact Company Contact + Deal HubSpot List HubSpot Contact property

Mapped field by field · sample run · one-click rollback

## What moves from Kartra to HubSpot?

Kartra and HubSpot CRM take fundamentally different approaches to contact data architecture.

Read the full summary

Kartra stores everything on a single Lead object with tags, lists, and custom fields as properties — it does not have a separate Company object by default, and deals are handled through Kartra's product and transaction engine. HubSpot separates Contacts, Companies, and Deals into distinct objects with a lifecycle\_stage property that drives reporting, automation, and marketing-contact billing. The migration must therefore restructure Kartra's flat lead model into HubSpot's relational graph, splitting address data into HubSpot's structured address fields, extracting company names into a Companies object, and mapping Kartra deal/product data into HubSpot Deals with pipeline and stage mapping. Tags and lists require resolution: HubSpot Lists are used for segmentation but do not carry the same automation-trigger semantics as Kartra's lists. Custom fields translate by type — Kartra radio buttons and drop-downs become HubSpot picklists, text areas become long-text fields, and checkboxes map to multi-checkbox or boolean properties. We use Kartra's export CSV as the primary data source (not their API, due to documented rate limits), enrich it with custom field definitions, and load through HubSpot's native import API with field-level validation before committing to the full migration.

direct

### Lead (Contact) → Contact

Kartra's Lead object maps directly to HubSpot Contact.

How it maps

All standard fields (firstname, lastname, email, phone, address components) map to HubSpot's corresponding contact properties. The Kartra Lead ID is preserved as a custom Source\_System\_ID\_\_c field on each HubSpot contact for traceability and delta-run deduplication.

transformed

### Lead.company (property) → Company

Kartra stores company name as a property on the Lead.

How it maps

We extract unique company names from all Kartra leads, create a corresponding HubSpot Company record for each unique name, and link the Contact to that Company via HubSpot's 'Associated Company' property. This restructures Kartra's flat model into HubSpot's relational Contact-Company graph.

merged

### Lead (contact with product purchase history) → Contact + Deal

If a Kartra Lead has associated product purchases or subscriptions, we create a HubSpot Deal linked to the Contact.

How it maps

The Kartra product name becomes the Deal name, purchase amount maps to Deal amount, and subscription start dates map to the Deal's close date. Each product purchase can generate one Deal, preserving the transactional context in HubSpot's pipeline model.

transformed

### Kartra List membership → HubSpot List

Kartra Lists are automation-triggered segments that define who receives sequences and broadcasts.

How it maps

We create a corresponding HubSpot List for each Kartra list and add all Kartra contacts that were members of that list. Note that HubSpot Lists are static by default when populated via import — dynamic list behavior requires HubSpot list-filter setup post-migration.

direct

### Kartra Tag → HubSpot Contact property (tags)

Kartra's tag field contains comma-separated tags per lead.

How it maps

We map these to HubSpot's native 'tags' property on the Contact, preserving the full tag vocabulary. Tags serve as flat labels in both platforms, though HubSpot's tag automation triggers require post-migration configuration in HubSpot workflows.

value\_mapping

### Kartra Custom Fields (drop\_down, radio\_button) → HubSpot Contact custom properties (picklist)

Kartra drop-down and radio-button custom fields map to HubSpot single-select picklist properties.

How it maps

Each Kartra pick-list value requires explicit mapping to the corresponding HubSpot pick-list option. We preserve the original Kartra option labels and flag any unmapped values for your team to resolve before migration commits.

******What moves 14 objects

Kartra HubSpot

- Lead Contact 1:1
- Lead.company Company transformed
- Lead Contact merged
- Kartra List membership HubSpot List transformed
- Kartra Tag HubSpot Contact property 1:1
- Kartra Custom Fields HubSpot Contact custom properties transformed

\+ 8 more in the mapping below

## How Kartra and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension           | Kartra                                                                                                                   | HubSpot                                                                                                                                                         |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Contact model       | Kartra uses a single Lead object; company name stored as a property on the lead record, not a separate object.           | HubSpot separates Contacts and Companies into distinct objects with a lookup relationship via the associated company property.                                  |
| Deal/Pipeline model | Kartra handles transactions and products; no native deal pipeline with stages exists for standard contacts.              | HubSpot Deals have dedicated pipelines with configurable stages, probabilities, and forecast categories per pipeline.                                           |
| Lifecycle tracking  | Kartra tracks lead status changes via tags and list subscriptions; no unified lifecycle stage property.                  | HubSpot has a native lifecycle\_stage property (subscriber, lead, MQL, SQL, customer, evangelist) that drives reporting and automation.                         |
| Segmentation model  | Kartra Lists are automation-triggered segments; tags serve as flat labels assignable to any lead.                        | HubSpot Lists are static or dynamic segments used for marketing and reporting; tags exist as a separate property for labeling.                                  |
| Custom field types  | Kartra supports input\_field, text\_area, drop\_down, radio\_button, and checkbox custom field types on leads.           | HubSpot supports single-line text, multi-line text, number, date, datetime, file, single-checkbox, multi-checkbox, dropdown, radio, and calculation properties. |
| Association model   | Kartra leads can belong to multiple lists; N:N relationships handled via list membership, not explicit junction records. | HubSpot supports explicit contact-to-company associations (primary + additional) and contact-to-deal associations via deal roles.                               |
| GDPR tracking       | Kartra exports GDPR status and GDPR status date as properties on each lead record.                                       | HubSpot stores GDPR consent as a boolean or multi-checkbox property; consent communications tracked via a separate GDPR field set.                              |

## Kartra to HubSpot field mapping

The 30 most-used fields of 32 mapped for this pair. Custom fields are added from your own schema during scoping. [Download the full mapping (CSV) ↓](https://flitstack.ai/migrations/crm/kartra/to/hubspot.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

Kartra HubSpot

1. `First Name` Lead `firstname` Contact
2. `Middle Name` Lead `middlename` Contact
3. `Last Name` Lead `lastname` Contact
4. `Last Name 2` Lead `lastname` Contact
5. `Email` Lead `email` Contact

| Kartra field                                   | HubSpot field                            | Mapping                 | Note                                                                                                                                              |
| ---------------------------------------------- | ---------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Lead.First Name`                              | `Contact.firstname`                      | direct                  |                                                                                                                                                   |
| `Lead.Middle Name`                             | `Contact.middlename`                     | direct                  |                                                                                                                                                   |
| `Lead.Last Name`                               | `Contact.lastname`                       | direct                  |                                                                                                                                                   |
| `Lead.Last Name 2`                             | `Contact.lastname`                       | transformed             | Kartra's Last Name 2 appends to Last Name for cultures with two-surname conventions. We concatenate into a single lastname value.                 |
| `Lead.Email`                                   | `Contact.email`                          | direct                  |                                                                                                                                                   |
| `Lead.Phone Country Code`                      | `Contact.phone`                          | transformed             | Kartra stores country code and phone separately. We prepend country code to the phone number for E.164 format compatibility.                      |
| `Lead.Phone Number`                            | `Contact.phone`                          | direct                  |                                                                                                                                                   |
| `Lead.Company`                                 | `Contact.associatedcompanyid`            | transformed             | Kartra company name becomes HubSpot Company lookup. We create the Company record first, then link the Contact.                                    |
| `Lead.Address`                                 | `Contact.address`                        | transformed             | Kartra's combined address field parsed into HubSpot's structured address1 and address2 sub-fields.                                                |
| `Lead.City`                                    | `Contact.city`                           | direct                  |                                                                                                                                                   |
| `Lead.Zip`                                     | `Contact.zip`                            | direct                  |                                                                                                                                                   |
| `Lead.Country`                                 | `Contact.country`                        | direct                  |                                                                                                                                                   |
| `Lead.State`                                   | `Contact.state`                          | direct                  |                                                                                                                                                   |
| `Lead.Website`                                 | `Contact.website`                        | direct                  |                                                                                                                                                   |
| `Lead.Facebook`                                | `Contact.facebook`                       | direct                  |                                                                                                                                                   |
| `Lead.Twitter`                                 | `Contact.twitter`                        | direct                  |                                                                                                                                                   |
| `Lead.LinkedIn`                                | `Contact.linkedin`                       | direct                  |                                                                                                                                                   |
| `Lead.Instagram`                               | `Contact.instagram`                      | direct                  |                                                                                                                                                   |
| `Lead.GDPR Status`                             | `Contact.gdpr_consent_to_communicate__c` | custom\_field\_required | HubSpot has no native GDPR status field. We create a custom single-checkbox property to preserve Kartra's GDPR status.                            |
| `Lead.GDPR Status Date`                        | `Contact.gdpr_date__c`                   | custom\_field\_required | Maps to a custom date field on HubSpot Contact, preserving when GDPR consent was last updated.                                                    |
| `Lead.Tags`                                    | `Contact.tags`                           | direct                  |                                                                                                                                                   |
| `Lead.Lists`                                   | `Contact.hs_list_memberships`            | transformed             | Kartra's comma-separated list memberships become HubSpot List enrollments. We create a HubSpot List per Kartra list and enroll matching contacts. |
| `Lead.IP`                                      | `Contact.kartra_ip_address__c`           | custom\_field\_required | HubSpot has no native IP address field. Preserved as a custom property for geo-targeting and compliance.                                          |
| `Lead.IP Country`                              | `Contact.kartra_ip_country__c`           | custom\_field\_required | Maps to a custom single-line text property, preserving the country derived from lead's IP address.                                                |
| `Lead.Sales Tax ID`                            | `Contact.tax_id__c`                      | custom\_field\_required | Preserved as a custom text property on HubSpot Contact since HubSpot has no native tax ID field.                                                  |
| `Lead.Lead create date (system)`               | `Contact.original_create_date__c`        | custom\_field\_required | HubSpot sets CreatedDate at import time. Original Kartra create date preserved in a custom datetime field for reporting continuity.               |
| `Lead.Kartra Lead ID`                          | `Contact.source_system_id__c`            | custom\_field\_required | Kartra's internal lead ID stored for traceability, delta-run deduplication, and cross-reference during the cutover window.                        |
| `Lead (custom).drop_down type custom field`    | `Contact.custom_dropdown__c`             | value\_mapping          | Kartra drop-down maps to HubSpot picklist. Each option value requires explicit mapping to the HubSpot picklist option label.                      |
| `Lead (custom).radio_button type custom field` | `Contact.custom_radio__c`                | value\_mapping          | Kartra radio button maps to HubSpot single-select picklist with exclusive option selection.                                                       |
| `Lead (custom).checkbox type custom field`     | `Contact.custom_checkbox__c`             | direct                  | Maps to HubSpot single-checkbox (boolean) property. True/false values translate directly.                                                         |

## What to watch for in a Kartra to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Kartra's flat Lead model requires structural transformation into HubSpot's relational Contact-Company graph

Kartra stores company name as a property on the Lead object rather than maintaining a separate Company record.

How we handle it

HubSpot separates Contacts and Companies into distinct objects with explicit lookup associations. When migrating, we must first extract all unique company names from Kartra leads, create the corresponding HubSpot Company records, and then link each Contact to its primary Company via HubSpot's associatedcompanyid property. This means the migration cannot load contacts in a single batch — it must first stage the company extraction, create the Companies object, then resolve the foreign key on each Contact during the contact load. If your Kartra data has leads without a company name, those contacts will land in HubSpot without a company association and will need manual association or a default company record created.

medium

### Kartra lists have automation semantics that HubSpot lists do not replicate automatically

Kartra Lists are more than static segments — they trigger automation sequences when a lead joins or leaves a list.

How we handle it

In HubSpot, Lists are used for segmentation and reporting, and workflow enrollment is handled separately via HubSpot workflows with list-based triggers. When we migrate Kartra list memberships to HubSpot, we create static HubSpot Lists and enroll the contacts. However, the automation logic that fires when a contact enters or exits a Kartra list does not migrate — it must be rebuilt as HubSpot workflow enrollments. We surface the Kartra list-to-automation mappings in the migration plan so your team can rebuild those automations in HubSpot workflows before or shortly after go-live.

high

### Kartra sequences and enrollment state have no HubSpot equivalent and must be rebuilt

Kartra Sequences are multi-step email automation programs with enrollment tracking, pause/resume state, and per-step timing logic.

How we handle it

HubSpot workflows serve a similar function but use different trigger types and timing models. We cannot carry over which step of which sequence a contact was on when migration occurs. We preserve sequence enrollment history as a custom text property listing the sequences each contact was enrolled in, but the active sequence state — paused, resumed, waiting at a specific step — is lost and must be restarted in HubSpot. For contacts mid-sequence at the time of migration, your team should communicate the reset to affected contacts or configure a HubSpot workflow to re-enroll them based on the preserved sequence history.

medium

### Kartra's transactional product/membership access data requires a separate rebuild strategy

Kartra tracks which products and membership levels a lead has purchased access to.

How we handle it

HubSpot CRM does not have a native product-access or membership-level field on the Contact object. We preserve product and membership access names and dates as custom text fields on the Contact record, but this is a reference snapshot, not a live access management system. If your business relies on Kartra's membership access control to gate content or course enrollment, the access management logic must be rebuilt using HubSpot's custom objects feature or a third-party membership management tool integrated with HubSpot.

medium

### HubSpot's marketing contact billing model is not replicated from Kartra

Kartra does not differentiate between marketing contacts and sales contacts in its billing model — contact count is the flat limit.

How we handle it

HubSpot charges based on marketing contact count above a threshold, separate from total CRM contacts. Contacts migrated from Kartra land as standard HubSpot contacts. Your team will need to evaluate which migrated contacts should be designated as marketing contacts in HubSpot based on your email marketing usage. We flag all migrated contacts as non-marketing by default and provide a list of contacts who had email activity in Kartra (opens, clicks, broadcast sends) as candidates for the marketing contact designation.

## How the migration runs

1. ### Export Kartra data and build the field mapping plan

   We extract your Kartra data using Kartra's native CSV export for Leads, capturing all standard fields, custom fields, tags, list memberships, GDPR properties, and social profile URLs.

   What this step covers

   We retrieve Kartra's custom field definitions via Kartra's API (type, label, options) to build a type-aware mapping table. We then analyze the extracted data for duplicates, missing required fields, and data quality issues — identifying records that will need a default company association in HubSpot and contacts with unmapped tag values. The field mapping plan documents every Kartra field's destination in HubSpot, including custom field creation requirements and value-mapping for pick-list fields.

2. ### Create HubSpot Companies from Kartra company-name data

   Before loading any Contacts, we extract unique company names from all Kartra leads and create the corresponding HubSpot Company records.

   What this step covers

   This step establishes the Company object so that HubSpot's foreign-key constraints are satisfied when we link Contacts to their primary company. We also populate each Company's website, industry (if inferable from domain), and country fields during this step. Companies are created in HubSpot via the native API with batch processing for efficiency. Any Kartra leads without a company name are flagged — your team decides whether to create a default 'No Company' placeholder Company or leave those contacts unassociated.

3. ### Create custom properties in HubSpot and run the sample migration

   We create all required HubSpot custom contact properties — for IP address, IP country, GDPR consent fields, original create date, source system ID, and all Kartra custom field translations (picklists, checkboxes, text fields).

   What this step covers

   We then run a sample migration using 100–300 representative Kartra records spanning different tag combinations, list memberships, and custom field values. The sample migration generates a field-level diff report showing every mapped value in Kartra alongside its HubSpot destination. Your team reviews the diff to verify custom field type mapping, pick-list value mapping, and company association accuracy before we commit to the full migration.

4. ### Load all Contacts with full field mapping and list enrollments

   With the mapping plan approved from the sample, we load all Contacts into HubSpot using HubSpot's native import API with field-level validation.

   What this step covers

   Each Contact receives its mapped standard properties, custom properties, tag assignments, and company association. List memberships are processed by creating a HubSpot List per Kartra list and enrolling the matching contacts. We preserve the original Kartra create date in a custom field since HubSpot's CreatedDate is set at import time. All Kartra lead IDs are stored in the source\_system\_id\_\_c property for traceability and to support delta-run deduplication.

5. ### Capture delta records and validate the full migration

   After the initial full migration load, we open a delta-pickup window (typically 24–48 hours) during which any new Kartra records or modified Kartra records are captured and migrated to HubSpot.

   What this step covers

   This ensures that contacts added or updated in Kartra during the cutover window are reflected in HubSpot at go-live. We run a post-migration validation comparing record counts by object, checking for duplicate contacts (matched by email address), verifying custom property completeness, and spot-checking tag and list enrollment accuracy. The audit log captures every operation for reconciliation. One-click rollback is available if validation reveals critical data issues before you confirm acceptance.

![](https://flitstack.ai/platforms/kartra.png) Kartra ![](https://flitstack.ai/platforms/hubspot.svg) HubSpot

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · HubSpot Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**48–72 hours for under 25,000 records with under 30 custom fields** Typical, smaller accounts

**5–10 days for over 100,000 records or heavy custom-field / list-segment complexity** Large or heavily customised accounts

Kartra-to-HubSpot migration pricing reflects three primary cost drivers: record volume (contact count drives extraction and import time), custom field count (Kartra's custom field type diversity — radio buttons, drop-downs, checkboxes — requires type-aware mapping logic per field, and each pick-list type needs explicit value mapping), and data-model divergence complexity (Kartra's flat Lead model requires restructuring into HubSpot's Contact + Company + Deal graph, with company-name extraction and address-field splitting adding mapping overhead). HubSpot's marketing-contact billing model is not replicated — contacts that would have been marketing contacts in Kartra land as standard HubSpot contacts and are flagged for your team to manage within HubSpot's contact management. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Kartra to HubSpot →](https://flitstack.ai/contact)

## Why teams move from Kartra to HubSpot

- Kartra's all-in-one model works while your business is small, but as contact volume grows and sales processes mature, the flat Lead object without a dedicated deal pipeline creates reporting blind spots. HubSpot's separate Deals object with pipeline stages gives sales managers the deal-stage visibility they need to forecast accurately — a gap Kartra users consistently report as their breaking point.
- HubSpot's native lifecycle\_stage property and the associated reporting dashboards provide marketing attribution that Kartra's tag-based tracking cannot match without extensive custom reporting. Teams moving to HubSpot gain access to revenue attribution by lifecycle stage and source without building custom reports from exported CSV data.
- HubSpot's ecosystem of native integrations with tools like Salesforce, Slack, and Zapier — plus a marketplace of 1,000+ third-party apps — exceeds what Kartra's closed ecosystem offers. Businesses outgrowing Kartra's native capabilities find HubSpot's extensibility removes the need to switch tools again.
- When a business needs HubSpot's free CRM tier as a starting point and a clear upgrade path through Sales Hub Professional and Enterprise, Kartra's flat pricing tiers can become cost-prohibitive at scale. The migration to HubSpot is driven by a long-term cost and capability calculation, not just a feature comparison.
- Acquired companies or partner organizations frequently standardize on HubSpot post-M\&A. For businesses already using HubSpot in one division, consolidating Kartra's customer data into the existing HubSpot account eliminates the operational overhead of maintaining two CRM systems with no native sync.

Questions, answered

## Kartra to HubSpot migration questions

How long does a Kartra to HubSpot CRM migration take?

Most Kartra-to-HubSpot migrations complete within 48–72 hours for setups under 25,000 records with fewer than 30 custom fields. Larger migrations with 100,000+ records or complex custom-field type diversity (radio buttons, checkboxes, drop-downs) extend to 5–10 days. The Kartra data export and custom field definition retrieval typically takes 1–2 business days, followed by the mapping plan and sample migration review (1–2 days), then the full load and delta pickup (2–5 days depending on record volume). The primary time variable is how quickly your team reviews the sample migration field-level diff.

Will my Kartra sequences and automation workflows migrate to HubSpot?

No. FlitStack AI migrates data and schema only — Kartra sequences, automation workflows, broadcast settings, and tag-based automation triggers do not transfer to HubSpot. They must be rebuilt in HubSpot's workflow engine. We provide a workflow rebuild reference document that lists each Kartra sequence and automation with its trigger conditions and step logic so your HubSpot admin can recreate them. Contacts' sequence enrollment history is preserved as a custom property listing the sequences they were enrolled in, but the active sequence state (paused, current step, timing) is reset at migration and must be restarted as a HubSpot workflow enrollment.

What happens to my Kartra tags and list memberships in HubSpot?

Kartra tags migrate directly to HubSpot's native tags property on each Contact — the full tag vocabulary is preserved and contacts retain their tag assignments. Kartra list memberships are translated to HubSpot Lists: we create a HubSpot List for each Kartra list and enroll all contacts that were members. However, HubSpot Lists are static when populated via import — the automation triggers that fire when a contact enters or exits a Kartra list must be rebuilt as HubSpot workflow enrollments using HubSpot's list-based trigger conditions. We surface the full list-to-automation mapping in the migration plan.

Can I migrate Kartra custom fields to HubSpot custom properties?

Yes. Kartra custom fields of type input\_field and text\_area map to HubSpot text and long-text properties. Kartra radio\_button and drop\_down fields map to HubSpot single-select picklist properties, with each Kartra option mapped to a corresponding HubSpot picklist option. Kartra checkbox fields map to HubSpot single-checkbox boolean properties. We retrieve Kartra's custom field definitions via Kartra's API before migration so we can create the matching HubSpot custom properties with the correct field type, label, and option values before the data load begins. Any unmapped pick-list values are flagged for your team to resolve.

How does Kartra's company-less Lead model translate to HubSpot's Contact-Company architecture?

Kartra stores company name as a property on the Lead record; there is no separate Company object. HubSpot requires Contacts and Companies as separate objects with an explicit lookup association. Our migration extracts all unique company names from your Kartra leads, creates the corresponding HubSpot Company records first, and then links each Contact to its primary Company via HubSpot's associatedcompanyid property. This two-phase approach (Companies load first, then Contacts with company lookup) is required to satisfy HubSpot's referential integrity constraints. Leads without a company name in Kartra will land as unassociated Contacts in HubSpot — your team decides whether to create a default placeholder Company or associate them manually.

Does the migration affect my Kartra account during the cutover?

No. FlitStack AI uses Kartra's export CSV and read-only API access to extract your data. Your team continues operating in Kartra throughout the migration. A delta-pickup window (24–48 hours after the initial full load) captures any new Kartra records or modifications made during the cutover period. These delta records are migrated to HubSpot before go-live so that HubSpot reflects Kartra's final state at the moment of switchover. Your Kartra account remains fully functional until you confirm HubSpot is live and decide when to reduce or sunset your Kartra subscription.

What Kartra data cannot be migrated to HubSpot CRM?

Kartra data that has no HubSpot CRM equivalent includes: user passwords (not exported by Kartra), total spend and points balances (Kartra does not export these fields), membership access and course enrollment state (preserved as a text snapshot only, not as live access management), and active sequence enrollment state (which step of which sequence a contact was on). Workflows, sequences, broadcasts, and tag-based automation triggers also do not migrate and must be rebuilt. We provide a complete inventory of unmigratable data in the migration plan and offer a workflow rebuild reference to support your team's HubSpot automation rebuild.

How does the migration handle contacts without email addresses?

HubSpot requires an email address to create a Contact record. Contacts in Kartra without an email address are flagged during the data audit phase. Your team decides how to handle these: options include creating a placeholder email (firstname.lastname\@placeholder.local) with a note in a custom property, merging them into a Company-level record without a Contact, or excluding them from the migration with a list provided for manual follow-up. We recommend resolving email-less records before migration to avoid data loss and to ensure your HubSpot contact count aligns with your HubSpot pricing tier.

## Related migrations

[![](https://flitstack.ai/platforms-trim/hubspot.webp) Migrate to **HubSpot** Every source we move into HubSpot, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/hubspot)

### [HubSpot implementation](https://flitstack.ai/services/hubspot-implementation)

[Set up HubSpot and migrate into it as one engagement.](https://flitstack.ai/services/hubspot-implementation)

[See the service →](https://flitstack.ai/services/hubspot-implementation) [**Sharpspring to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/sharpspring/to/hubspot) [**Iterable to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/iterable/to/hubspot) [**Marketing Star to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/marketing-star/to/hubspot) [**HighLevel to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/highlevel/to/hubspot) [**Filevine to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/filevine/to/hubspot) [**Capsule CRM to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/capsule-crm/to/hubspot) [**Kartra to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/kartra/to/salesforce-sales-cloud) [**Kartra to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/kartra/to/zoho-crm)

## Sources: official documentation

1. [Format import files — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
2. [Create and edit custom objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/object-settings/create-custom-objects)
3. [Import objects programmatically — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/import-objects)
4. [Understand property field types in HubSpot](https://knowledge.hubspot.com/properties/property-field-types-in-hubspot)
5. [Associate records on CRM objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/records/associate-records)
6. [Integration throughput and limits — HubSpot Knowledge Base](https://knowledge.hubspot.com/integrations/integration-throughput-and-limits)
7. [HubSpot Cloud Infrastructure and Data Hosting FAQ](https://knowledge.hubspot.com/account-security/hubspot-cloud-infrastructure-and-data-hosting-frequently-asked-questions)

Get a quote

## Moving from Kartra to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
