---
title: "Civicrm to HubSpot Migration: Field Mapping & Rollback"
description: "Migrate Civicrm 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/civicrm/to/hubspot"
---

# Civicrm to HubSpot migration

Moving from CiviCRM to HubSpot is a common path for nonprofits outgrowing self-hosted infrastructure and seeking native integrations. FlitStack AI maps contacts, organizations, activities, and custom data while preserving membership type and contribution history — then routes each record into HubSpot's lifecycle stage and deal pipeline model so your team works from a complete dataset on day one.

Short answer

FlitStack AI migrates contacts, companies, deal + custom fields, custom fields on contacts and custom properties on contact/company/deals from Civicrm 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 50,000 records.

![](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/civicrm/to/hubspot#field-mapping)

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

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

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

Contact Company Deal + custom fields Custom fields on Contact Custom properties on Contact/Company/Deal

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

## What moves from Civicrm to HubSpot?

CiviCRM is an open-source, self-hosted CRM built for nonprofits, advocacy groups, and civic organizations.

Read the full summary

Its data model covers contacts, organizations, activities, contributions, memberships, events, and cases — many of which have no direct equivalent in HubSpot's commercial SaaS model. HubSpot natively supports contacts, companies, deals, tickets, and activities, but represents CiviCRM-native concepts like membership type and contribution amounts as HubSpot custom properties on those objects. FlitStack AI migrates contacts, organizations, and activities via the HubSpot CRM API, transforming contributions into deals with custom fields for financial details and preserving membership records as custom contact properties. Workflows, CiviRules, and custom PHP extensions that define business logic in CiviCRM do not migrate — they must be rebuilt in HubSpot's automation tools. The migration uses a sequenced load: contacts and organizations first (to resolve foreign keys), then activities, then contributions as deals, with owner resolution by email match against HubSpot users. A delta-pickup window captures any records modified in CiviCRM during cutover.

direct

### Contact (Individual) → Contact

CiviCRM Individual contacts map directly to HubSpot Contacts via the HubSpot CRM API.

How it maps

Email serves as the primary deduplication key to prevent duplicate records. The CiviCRM contact\_subtype field is preserved as a HubSpot custom property to maintain segmentation data. Standard fields including names, phone numbers, and physical addresses map directly to their HubSpot equivalents without transformation.

direct

### Contact (Organization) → Company

CiviCRM Organization contacts map to HubSpot Companies using the HubSpot Companies API.

How it maps

The organization name field maps directly to the HubSpot Company Name property. Industry classification, website URL, and address information map to their HubSpot equivalents. When CiviCRM stores a main branch with sub-branches, the hierarchy is preserved in HubSpot using parent-company relationships to maintain organizational structure.

direct

### Activity (Email) → Contact (email timeline)

CiviCRM email activities that are attached to contacts map to HubSpot's contact engagement timeline using the HubSpot Engagements API.

How it maps

The email subject line and body content transfer as engagement notes on the contact record. File attachments from CiviCRM emails are re-uploaded to HubSpot Files and linked back to the respective contact timeline entry to preserve the complete communication history.

direct

### Activity (Call) → Contact (call timeline)

CiviCRM call activities are mapped to HubSpot's call log feature on the contact timeline using the HubSpot Calls API.

How it maps

Call duration, subject line, and outcome status fields transfer directly to their HubSpot counterparts. The original CiviCRM call date and time are preserved as the engagement timestamp in HubSpot to maintain accurate historical recordkeeping for audit purposes.

direct

### Activity (Meeting/Event attendance) → Contact (meeting timeline)

CiviCRM meeting activities and event attendee records map to HubSpot's meeting log on the contact timeline via the HubSpot Meetings API.

How it maps

The CiviCRM event name field becomes the meeting subject in HubSpot. Attendance status values such as Registered, Attended, and No-show are stored as a custom property on the HubSpot meeting record to preserve the original attendance data for reporting purposes.

direct

### Activity (Note) → Contact (note)

CiviCRM notes attached to contacts map to HubSpot engagement notes on the contact timeline using the HubSpot Notes API.

How it maps

The original note create date and author information are preserved as metadata on the HubSpot engagement note. Rich-text formatting present in CiviCRM notes is converted to plain text for consistency, or kept as-is if the formatting is simple enough to transfer without data loss, based on complexity assessment during the migration.

******What moves 16 objects

Civicrm HubSpot

- Contact Contact 1:1
- Contact Company 1:1
- Activity Contact 1:1
- Activity Contact 1:1
- Activity Contact 1:1
- Activity Contact 1:1

\+ 10 more in the mapping below

## How Civicrm 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           | Civicrm                                                                                                                                             | HubSpot                                                                                                                                                                                   |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Contact model       | CiviCRM uses a unified contact record with a contact\_type field (Individual/Organization) and a subtype system for additional segmentation.        | HubSpot separates contacts and companies into distinct objects. Contact type does not exist — CiviCRM contact\_type routes to HubSpot lifecycle\_stage or a custom property.              |
| Financial records   | CiviCRM stores contributions as standalone Contribution records linked to contacts, with financial type, amount, currency, and receipting built in. | HubSpot has no contribution object. Contributions become Deals with custom fields for amount, currency, contribution type, and date.                                                      |
| Memberships         | CiviCRM has a dedicated membership entity with type, status, start/end dates, and renewal history.                                                  | HubSpot has no native membership object. Membership data migrates as custom contact properties: membership\_type, membership\_status, member\_since.                                      |
| Activity linking    | CiviCRM activities can link to multiple contact records and optionally to cases, contributions, and events simultaneously.                          | HubSpot engagements attach to a single contact, company, deal, or ticket record. Linked-contact data is preserved as a custom multi-select property.                                      |
| Custom data         | CiviCRM custom fields (custom\_123 style) attach to any entity via custom groups. Multi-record custom data sets are first-class API entities.       | HubSpot custom properties attach to contacts, companies, deals, tickets, and custom objects. Multi-record CiviCRM data migrates to a HubSpot custom object or JSON-serialized text field. |
| Case management     | CiviCase provides full case management with client, status, type, opened/closed dates, and linked activities.                                       | HubSpot has no native case management object. Cases migrate as HubSpot tickets with custom fields for case type, status, and duration, or as custom objects.                              |
| Workflows and rules | CiviCRM workflows are defined via CiviRules extension and custom PHP hooks. No native visual workflow builder.                                      | HubSpot workflows (Automation) are native visual builders. All CiviCRM workflow logic must be manually rebuilt in HubSpot.                                                                |
| Hosting model       | CiviCRM is self-hosted or hosted by the organization. You own the server, database, and PHP runtime.                                                | HubSpot is a fully managed SaaS platform. No server maintenance, no PHP, no version upgrades. Billing is per-seat with a free CRM tier.                                                   |

## Civicrm to HubSpot field mapping

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

******Field mapping 5 shown

Civicrm HubSpot

1. `first_name` Contact `firstname` Contact
2. `last_name` Contact `lastname` Contact
3. `email` Contact `email` Contact
4. `phone` Contact `phone` Contact
5. `mobile_phone` Contact `mobilephone` Contact

| Civicrm field                      | HubSpot field                            | Mapping                 | Note                                                                                                                                                            |
| ---------------------------------- | ---------------------------------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Contact.first_name`               | `Contact.firstname`                      | direct                  |                                                                                                                                                                 |
| `Contact.last_name`                | `Contact.lastname`                       | direct                  |                                                                                                                                                                 |
| `Contact.email`                    | `Contact.email`                          | direct                  |                                                                                                                                                                 |
| `Contact.phone`                    | `Contact.phone`                          | direct                  |                                                                                                                                                                 |
| `Contact.mobile_phone`             | `Contact.mobilephone`                    | direct                  |                                                                                                                                                                 |
| `Contact.job_title`                | `Contact.jobtitle`                       | direct                  |                                                                                                                                                                 |
| `Contact.birth_date`               | `Contact.hs_date_of_birth`               | direct                  |                                                                                                                                                                 |
| `Contact.contact_type`             | `Contact.contact_type__c`                | custom\_field\_required | CiviCRM contact\_type (Individual/Organization) becomes a custom property since HubSpot uses the Contact vs. Company object distinction instead.                |
| `Contact.source`                   | `Contact.hs_analytics_source`            | direct                  |                                                                                                                                                                 |
| `Contact.external_identifier`      | `Contact.civicrm_id__c`                  | custom\_field\_required | CiviCRM internal contact ID stored on HubSpot for traceability and delta-run de-duplication.                                                                    |
| `Contact.created_date`             | `Contact.original_civicrm_createdate__c` | custom\_field\_required | HubSpot sets CreatedDate at migration time. Original CiviCRM create date preserved as a custom datetime field for reporting continuity.                         |
| `Contact.modified_date`            | `Contact.hs_lastmodifieddate`            | direct                  |                                                                                                                                                                 |
| `Organization.organization_name`   | `Company.name`                           | direct                  |                                                                                                                                                                 |
| `Organization.website`             | `Company.website`                        | direct                  |                                                                                                                                                                 |
| `Organization.industry`            | `Company.industry`                       | value\_mapping          | Industry pick-list values mapped value-by-value to HubSpot's industry options. Non-matching values applied as HubSpot's 'Other' option.                         |
| `Organization.number_of_employees` | `Company.numberofemployees`              | direct                  |                                                                                                                                                                 |
| `Organization.annual_revenue`      | `Company.annualrevenue`                  | direct                  |                                                                                                                                                                 |
| `Organization.external_identifier` | `Company.civicrm_org_id__c`              | custom\_field\_required | CiviCRM internal organization ID stored on HubSpot Company for traceability and delta-run de-duplication.                                                       |
| `Contribution.total_amount`        | `Deal.amount`                            | transformed             | Contribution amount becomes the Deal amount. Currency code preserved in a separate contribution\_currency custom property since HubSpot amount is numeric only. |
| `Contribution.currency`            | `Deal.contribution_currency__c`          | custom\_field\_required | CiviCRM currency ISO code stored as a custom text property on the Deal since HubSpot deals do not have a native currency field.                                 |
| `Contribution.financial_type`      | `Deal.contribution_type__c`              | custom\_field\_required | CiviCRM financial type (Donation, Event Fee, etc.) stored as a custom pick-list property on the Deal for filtering and reporting.                               |
| `Contribution.receive_date`        | `Deal.closedate`                         | transformed             | Contribution receive date maps to Deal close date. Deals are created in Won status to represent closed contributions.                                           |
| `Contribution.contribution_status` | `Deal.dealstage`                         | value\_mapping          | Completed contributions map to 'Closed Won'. Pending, Failed, and Refunded contributions map to 'Closed Lost' or a dedicated stage per the migration plan.      |
| `Contribution.trxn_id`             | `Deal.contribution_trxn_id__c`           | custom\_field\_required | CiviCRM transaction ID preserved as a custom text property for payment reconciliation reference.                                                                |
| `Contribution.external_identifier` | `Deal.civicrm_contribution_id__c`        | custom\_field\_required | CiviCRM internal contribution ID stored on HubSpot Deal for traceability and delta-run de-duplication.                                                          |
| `Membership.membership_type`       | `Contact.membership_type__c`             | custom\_field\_required | HubSpot has no native membership object. Membership type stored as a custom text property on the HubSpot Contact.                                               |
| `Membership.status`                | `Contact.membership_status__c`           | custom\_field\_required | Membership status (Current, Expired, Pending) stored as a custom pick-list property on the HubSpot Contact.                                                     |
| `Membership.start_date`            | `Contact.membership_start_date__c`       | custom\_field\_required | Original membership join date preserved as a custom date property on the HubSpot Contact for tenure reporting.                                                  |
| `Membership.end_date`              | `Contact.membership_end_date__c`         | custom\_field\_required | Membership expiration date stored as a custom date property. Null end date indicates lifetime membership.                                                       |
| `Activity (Call).subject`          | `Contact.hs_call_title`                  | direct                  |                                                                                                                                                                 |

## What to watch for in a Civicrm 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

### CiviCRM contact\_type maps to a HubSpot custom property, not a native object split

CiviCRM's contact\_type (Individual vs.

How we handle it

Organization) is a field on a unified contact table. HubSpot separates contacts and companies into distinct objects by design — there is no contact\_type field on HubSpot contacts. We migrate CiviCRM Individuals as HubSpot Contacts and CiviCRM Organizations as HubSpot Companies, then store the original contact\_type as a custom property on both for audit and reporting. If your migration relies on filtering reports by contact\_type, those reports need to be rebuilt using the custom property in HubSpot's report builder.

high

### HubSpot deal amount is a plain number — currency and multi-currency contributions need custom field treatment

CiviCRM contributions track currency per record (USD, GBP, EUR, etc.) because CiviCRM is built for international nonprofits receiving donations in multiple currencies.

How we handle it

HubSpot's native deal amount field (amount) is a single numeric field with no currency dimension. We handle this by mapping contribution amount to deal amount and storing the currency code in a contribution\_currency custom property. If your organization receives contributions in more than one currency, all non-base-currency amounts are stored as-is but cannot be summed natively in HubSpot deal reports — your team should use HubSpot's custom report builder or a revenue intelligence tool to aggregate multi-currency data.

medium

### Membership renewal history collapses to a single current-status snapshot

CiviCRM tracks full membership history — every renewal, lapse, and status change is a dated event with its own record.

How we handle it

HubSpot has no native membership object. We represent membership as custom contact properties: membership\_type, membership\_status, membership\_start\_date, and membership\_end\_date. These fields capture the current (most recent) state. Renewal history beyond the current record is summarized as a membership\_renewal\_summary custom text field containing a condensed history string. If your team relies on detailed renewal cadence reporting, that analysis needs to be rebuilt using the summary text or an external BI tool connected to HubSpot data.

medium

### CiviCRM CiviCase linked activities cannot preserve case-to-activity relationship chains in HubSpot

CiviCase activities in CiviCRM carry a dual linkage: they are attached to both a contact and a case record, and cases themselves can link to multiple contacts (client, case manager, external parties).

How we handle it

HubSpot engagements attach to a single contact, company, deal, or ticket record. When migrating CiviCase records, we attach the activities to the primary contact in HubSpot and store the case ID in a civicrm\_case\_id\_\_c custom property for reference. However, the case-to-activity chain — where one case groups multiple activities across different contacts — cannot be reproduced natively in HubSpot without a custom object hierarchy that your admin must design and approve during the migration plan phase.

low

### CiviCRM tags require upfront mapping to HubSpot properties before migration loads

CiviCRM tags are a flat namespace applied across all entity types — a single tag can label both a contact and a contribution.

How we handle it

HubSpot's tag equivalent is a contact or company property, not a cross-object label. We pre-scan all CiviCRM tags, identify which ones apply to contacts and organizations, and create corresponding HubSpot contact or company properties as multi-checkbox or text fields. Tags that apply to contributions are mapped to custom deal properties. Tags that span multiple entity types are mapped to the primary entity (usually contact) and the others are noted as lost associations in the migration plan. This pre-mapping step adds planning time but prevents orphaned tag data at migration completion.

## How the migration runs

1. ### Audit CiviCRM data model and document HubSpot custom field plan

   FlitStack pulls the full CiviCRM field inventory via the API — every custom field, custom data group, activity type, and financial type.

   What this step covers

   We map each field to a HubSpot standard property, custom property, or note it as requiring a design decision. For contributions, we identify the financial type to deal stage mapping strategy. For memberships, we define which contact properties receive the membership data. The output is a field mapping document your team reviews and approves before any data moves.

2. ### Create HubSpot custom properties and configure owner matching

   Before records are loaded, FlitStack creates the HubSpot custom properties identified in the audit: membership\_type\_\_c, membership\_status\_\_c, contribution\_amount\_\_c, contribution\_currency\_\_c, contribution\_type\_\_c, civicrm\_id\_\_c, and any object-specific custom fields.

   What this step covers

   We also configure owner resolution by email — CiviCRM users are matched to HubSpot users by email address. Unmatched users are flagged so your team either creates HubSpot seats for them or assigns a fallback owner before migration day.

3. ### Run a sample migration with field-level diff

   A representative slice of records migrates first — typically 100–500 records spanning contacts, organizations, contributions, and activities.

   What this step covers

   We generate a field-level diff report comparing source values to destination values for every mapped field. Your team reviews the diff to confirm contact\_type handling, contribution amount and currency mapping, and membership status placement before the full run commits. Issues identified here drive adjustments to the mapping plan.

4. ### Execute full migration in dependency order

   The full migration runs in the correct sequence: CiviCRM Organizations first (to create HubSpot Companies), then CiviCRM Individual contacts (resolving the primary organization link), then activities, then contributions as deals with all custom financial fields, and finally memberships as contact custom properties.

   What this step covers

   Foreign key relationships (contact-to-organization, contribution-to-contact) resolve within the same migration run as long as parent records land before children. FlitStack's audit log tracks every record operation.

5. ### Delta-pickup cutover and rollback readiness

   After the full migration completes, a delta-pickup window (24–48 hours) captures any records created or modified in CiviCRM during the cutover.

   What this step covers

   Your team continues working in CiviCRM throughout this period. FlitStack provides a rollback script that restores HubSpot to its pre-migration state if reconciliation uncovers data integrity issues. Once delta records land and your team confirms the data matches expectations, the migration is complete.

![](https://flitstack.ai/platforms/civicrm.svg) Civicrm ![](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 50,000 records** Typical, smaller accounts

**5–7 days for over 500,000 records or complex custom-field setups** Large or heavily customised accounts

CiviCRM-to-HubSpot migrations land in the lower-to-middle range when they involve standard contacts and activities with straightforward custom fields. The main cost drivers are record volume (contacts, organizations, contributions, and activities all count separately), the number of CiviCRM custom fields and custom data groups that need HubSpot custom properties created, and how far the data model diverges — particularly the contribution-to-deal transformation and membership handling, which require custom field setup on both contacts and deals. CiviCRM instances with multiple contribution financial types, complex multi-record custom data, or case management history push toward the upper end of the range because each non-equivalent object requires a custom mapping design and additional validation passes. A test migration slice is included in every scope to catch mapping issues before the full run. Every quote is scoped with you; there is no self-serve pricing.

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

## Why teams move from Civicrm to HubSpot

- CiviCRM requires custom PHP code for automations that most platforms handle out of the box — lead assignment, follow-up triggers, and renewal reminders all depend on a developer or a CiviRules consultant. HubSpot's native automation builder removes that dependency entirely, and organizations consistently cite this as the breaking point in G2 nonprofit reviews.
- Exporting data from CiviCRM reliably requires API access or custom database queries — the built-in export tools are limited to small batches and lack a clean bulk-export function. Teams report spending days cleaning CSV exports before any import work can start, which adds unexpected labor costs before migration tooling is even evaluated.
- CiviCRM's self-hosted model means the organization owns server maintenance, security patches, PHP version upgrades, and CiviCRM version upgrades. Smaller nonprofits report that hosting overhead consumes staff time that should go toward mission work — HubSpot's managed SaaS model eliminates that operational burden.
- HubSpot's reporting and dashboard tools are purpose-built for non-technical users — drag-and-drop report builders, pre-built nonprofit templates, and native integrations with email and web analytics. CiviCRM reporting requires SQL knowledge or expensive third-party tools that most small nonprofits cannot staff.
- As nonprofits grow and add fundraising events, recurring giving programs, and grant management, CiviCRM's data model requires increasingly complex custom fields to track the same information that HubSpot handles with standard deal properties and custom objects natively. This complexity increases maintenance overhead and requires developer assistance for changes, whereas HubSpot's native objects allow non-technical staff to manage data structures independently.

Questions, answered

## Civicrm to HubSpot migration questions

How long does a CiviCRM to HubSpot migration take?

Most CiviCRM-to-HubSpot migrations complete in 48–72 hours for under 50,000 total records. Larger instances with 500,000+ records, extensive contribution history, or multiple CiviCase types extend to 5–7 days. The longest planning step is the custom field audit — mapping CiviCRM contribution financial types and membership properties to HubSpot custom properties takes 3–5 business days before the first data moves. Timeline depends on data complexity more than raw volume.

Will my CiviCRM workflows and CiviRules migrate to HubSpot?

No. CiviCRM workflows and CiviRules are defined in PHP hooks and the CiviRules extension — they do not have an API-export format and cannot be read by migration tooling. They must be rebuilt in HubSpot's Automation tools. We provide an export of your CiviRules configuration as a structured reference document your HubSpot admin or our team can use to rebuild equivalent logic in HubSpot Workflows. This is a manual step your team should budget for alongside the data migration.

What does a CiviCRM contribution become in HubSpot?

CiviCRM contributions become HubSpot Deals with custom fields capturing the original financial data: contribution\_amount (mapped to deal amount), contribution\_currency, contribution\_type (the CiviCRM financial type), contribution\_date, and the CiviCRM transaction ID. Each migrated contribution deal is named with a configurable prefix so it is distinguishable from standard sales deals in HubSpot reports. Currency codes are stored as a custom text property because HubSpot deals have no native multi-currency support.

Can I migrate CiviCRM custom fields and custom data groups to HubSpot?

Yes. Single-record CiviCRM custom fields attach to contacts, organizations, or contributions and map directly to HubSpot custom properties on the corresponding object. Field types (text, date, pick-list, checkbox) are converted to their HubSpot equivalents. Multi-record custom data sets — such as employment history or volunteer history stored as CiviCRM multi-record groups — are migrated to a HubSpot custom object with a foreign key back to the parent contact, or serialized as JSON into a custom text field if your team prefers a simpler structure.

What happens to CiviCRM membership records in HubSpot?

HubSpot has no native membership object, so membership data attaches to the HubSpot Contact as custom properties: membership\_type\_\_c, membership\_status\_\_c, membership\_start\_date\_\_c, and membership\_end\_date\_\_c. The current membership status and type are always available for use in HubSpot lists, workflows, and reports. Full renewal history is summarized as a membership\_renewal\_summary\_\_c text field containing a condensed dated record of past renewals and status changes. Detailed renewal cadence reports should be built using the summary text or a connected BI tool.

Does the migration affect my CiviCRM account during cutover?

No. FlitStack AI uses scoped read-only API access to CiviCRM — your team keeps working in CiviCRM throughout the migration. A delta-pickup window of 24–48 hours after the full migration captures any new contributions, contacts, or activity records created or modified during the cutover. Your organization enters HubSpot with the complete final state from CiviCRM. There is no downtime window and no risk of data being locked in either system during the switch.

How does CiviCRM's CiviCase (case management) map to HubSpot?

CiviCase has no native equivalent in HubSpot. We migrate CiviCase records as HubSpot Tickets with custom fields for case\_type, case\_status, case\_opened\_date, and case\_closed\_date, or as a dedicated HubSpot custom object if your instance has complex case types and linked relationships. Case-linked activities migrate as standard HubSpot engagements attached to the primary contact. The case-to-activity grouping — where one case ties together multiple activities across different contacts — is broken in HubSpot's flat engagement model and requires a custom object design decision before migration day.

How are CiviCRM tags handled in the migration?

CiviCRM tags are a flat namespace shared across contacts, organizations, and contributions. We pre-scan all tags, split them by entity type, and create HubSpot custom properties for contact and company tags as multi-checkbox fields. Contribution tags are mapped to custom deal properties. Tags that span multiple entity types are flagged in the mapping plan as associations that cannot be fully preserved — your team decides whether to store the tag on the primary entity only or accept the partial mapping. This upfront decision prevents orphaned tag data at migration completion.

## 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) [**Lime CRM to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/lime-crm/to/hubspot) [**Systeme IO to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/systeme-io/to/hubspot) [**Keap to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/keap/to/hubspot) [**Wise Agent to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/wise-agent/to/hubspot) [**ChartMogul to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/chartmogul/to/hubspot) [**Marketing Star to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/marketing-star/to/hubspot) [**Civicrm to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/civicrm/to/dynamics-365-sales) [**Civicrm to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/civicrm/to/salesforce-sales-cloud) [**Civicrm to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/civicrm/to/pipedrive)

## 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 Civicrm 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)
