---
title: "Migrate to HubSpot: CRM Migration Guide & Service"
description: "Migrating to HubSpot? Import limits, the full migration checklist and every source FlitStack AI moves into HubSpot, with history and rollback."
url: "https://flitstack.ai/migrations/crm/hubspot"
---

# Migrate to HubSpot

HubSpot is an inbound-marketing-native CRM whose import model rewards teams that pre-create properties, respect contact-tier batch caps, and design picklist internal values before the first row is uploaded.

Short answer

FlitStack AI migrates pipelines, contacts, and deals into HubSpot from 850+ CRMs, including Salesforce, Pipedrive, Mailchimp, Zoho CRM. Every field is mapped to HubSpot's objects, history and associations come across, the HubSpot setup is configured alongside, and the whole migration stays reversible in one click.

![](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) [HubSpot implementation service →](https://flitstack.ai/services/hubspot-implementation)

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

From Any source ![](https://flitstack.ai/platforms-trim/salesforce-sales-cloud.webp) ![](https://flitstack.ai/platforms-trim/pipedrive.webp) ![](https://flitstack.ai/platforms-trim/mailchimp.webp)

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

Salesforce Pipedrive Mailchimp Zoho CRM Zendesk Sell

850+ sources mapped into HubSpot

## Systems we move into HubSpot

The CRMs teams most often move from. Each page shows what moves, the field mapping and what to watch for.

[Salesforce to HubSpot](https://flitstack.ai/migrations/crm/salesforce-sales-cloud/to/hubspot) [Pipedrive to HubSpot](https://flitstack.ai/migrations/crm/pipedrive/to/hubspot) [Mailchimp to HubSpot](https://flitstack.ai/migrations/crm/mailchimp/to/hubspot) [Zoho CRM to HubSpot](https://flitstack.ai/migrations/crm/zoho-crm/to/hubspot) [Zendesk Sell to HubSpot](https://flitstack.ai/migrations/crm/zendesk-sell/to/hubspot) [Close to HubSpot](https://flitstack.ai/migrations/crm/close/to/hubspot) [Act! to HubSpot](https://flitstack.ai/migrations/crm/act/to/hubspot) [Sentia to HubSpot](https://flitstack.ai/migrations/crm/sentia/to/hubspot) [![](https://flitstack.ai/platforms-trim/nimble-crm.webp) Nimble CRM to HubSpot](https://flitstack.ai/migrations/crm/nimble-crm/to/hubspot) [Insightly CRM to HubSpot](https://flitstack.ai/migrations/crm/insightly-crm/to/hubspot) [Freshsales to HubSpot](https://flitstack.ai/migrations/crm/freshsales/to/hubspot) [Attio to HubSpot](https://flitstack.ai/migrations/crm/attio/to/hubspot) [Dentrix to HubSpot](https://flitstack.ai/migrations/crm/dentrix/to/hubspot) [Twenty CRM to HubSpot](https://flitstack.ai/migrations/crm/twenty-crm/to/hubspot) [Jobber to HubSpot](https://flitstack.ai/migrations/crm/jobber/to/hubspot) [Streak to HubSpot](https://flitstack.ai/migrations/crm/streak/to/hubspot) [![](https://flitstack.ai/platforms-trim/copper.webp) Copper to HubSpot](https://flitstack.ai/migrations/crm/copper/to/hubspot) [![](https://flitstack.ai/platforms-trim/sugarcrm.webp) Sugarcrm to HubSpot](https://flitstack.ai/migrations/crm/sugarcrm/to/hubspot) [GoldMine to HubSpot](https://flitstack.ai/migrations/crm/goldmine/to/hubspot) [![](https://flitstack.ai/platforms-trim/activecampaign.webp) ActiveCampaign to HubSpot](https://flitstack.ai/migrations/crm/activecampaign/to/hubspot) [![](https://flitstack.ai/platforms-trim/act-on.webp) Act-On to HubSpot](https://flitstack.ai/migrations/crm/act-on/to/hubspot) [HoneyBook to HubSpot](https://flitstack.ai/migrations/crm/honeybook/to/hubspot) [folk to HubSpot](https://flitstack.ai/migrations/crm/folk/to/hubspot) [![](https://flitstack.ai/platforms-trim/bitrix24.webp) Bitrix24 to HubSpot](https://flitstack.ai/migrations/crm/bitrix24/to/hubspot) [![](https://flitstack.ai/platforms-trim/vinsolutions.webp) Vinsolutions to HubSpot](https://flitstack.ai/migrations/crm/vinsolutions/to/hubspot) [Follow Up Boss to HubSpot](https://flitstack.ai/migrations/crm/follow-up-boss/to/hubspot) [Nutshell to HubSpot](https://flitstack.ai/migrations/crm/nutshell/to/hubspot) [Housecall Pro to HubSpot](https://flitstack.ai/migrations/crm/housecall-pro/to/hubspot) [![](https://flitstack.ai/platforms-trim/convertkit.webp) Convertkit to HubSpot](https://flitstack.ai/migrations/crm/convertkit/to/hubspot) [improveit 360 to HubSpot](https://flitstack.ai/migrations/crm/improveit-360/to/hubspot) [Gold-Vision to HubSpot](https://flitstack.ai/migrations/crm/gold-vision/to/hubspot) [ForceManager CRM to HubSpot](https://flitstack.ai/migrations/crm/forcemanager-crm/to/hubspot) [ServiceTitan to HubSpot](https://flitstack.ai/migrations/crm/servicetitan/to/hubspot) [Dubsado to HubSpot](https://flitstack.ai/migrations/crm/dubsado/to/hubspot) [Snovio to HubSpot](https://flitstack.ai/migrations/crm/snovio/to/hubspot) [![](https://flitstack.ai/platforms-trim/customer-io.webp) Customer.io to HubSpot](https://flitstack.ai/migrations/crm/customer-io/to/hubspot) [LeadSimple to HubSpot](https://flitstack.ai/migrations/crm/leadsimple/to/hubspot) [Odoo CRM to HubSpot](https://flitstack.ai/migrations/crm/odoo-crm/to/hubspot) [Aweber to HubSpot](https://flitstack.ai/migrations/crm/aweber/to/hubspot) [![](https://flitstack.ai/platforms-trim/clio.webp) Clio to HubSpot](https://flitstack.ai/migrations/crm/clio/to/hubspot) [monday CRM to HubSpot](https://flitstack.ai/migrations/crm/monday-crm/to/hubspot) [Dynamics 365 to HubSpot](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/hubspot) [![](https://flitstack.ai/platforms-trim/cision.webp) Cision to HubSpot](https://flitstack.ai/migrations/crm/cision/to/hubspot) [![](https://flitstack.ai/platforms-trim/yardi.webp) Yardi to HubSpot](https://flitstack.ai/migrations/crm/yardi/to/hubspot) [![](https://flitstack.ai/platforms-trim/sendcloud.webp) SendCloud to HubSpot](https://flitstack.ai/migrations/crm/sendcloud/to/hubspot) [Vendasta to HubSpot](https://flitstack.ai/migrations/crm/vendasta/to/hubspot) [Capsule CRM to HubSpot](https://flitstack.ai/migrations/crm/capsule-crm/to/hubspot) [Filevine to HubSpot](https://flitstack.ai/migrations/crm/filevine/to/hubspot) [HighLevel to HubSpot](https://flitstack.ai/migrations/crm/highlevel/to/hubspot) [Kartra to HubSpot](https://flitstack.ai/migrations/crm/kartra/to/hubspot) [Sharpspring to HubSpot](https://flitstack.ai/migrations/crm/sharpspring/to/hubspot) [Iterable to HubSpot](https://flitstack.ai/migrations/crm/iterable/to/hubspot) [![](https://flitstack.ai/platforms-trim/marketing-star.webp) Marketing Star to HubSpot](https://flitstack.ai/migrations/crm/marketing-star/to/hubspot) [![](https://flitstack.ai/platforms-trim/chartmogul.webp) ChartMogul to HubSpot](https://flitstack.ai/migrations/crm/chartmogul/to/hubspot) [![](https://flitstack.ai/platforms-trim/wise-agent.webp) Wise Agent to HubSpot](https://flitstack.ai/migrations/crm/wise-agent/to/hubspot) [Civicrm to HubSpot](https://flitstack.ai/migrations/crm/civicrm/to/hubspot) [Lime CRM to HubSpot](https://flitstack.ai/migrations/crm/lime-crm/to/hubspot) [![](https://flitstack.ai/platforms-trim/systeme-io.webp) Systeme IO to HubSpot](https://flitstack.ai/migrations/crm/systeme-io/to/hubspot) [Keap to HubSpot](https://flitstack.ai/migrations/crm/keap/to/hubspot) [![](https://flitstack.ai/platforms-trim/pipeline-crm.webp) Pipeline CRM to HubSpot](https://flitstack.ai/migrations/crm/pipeline-crm/to/hubspot) [Salesflare to HubSpot](https://flitstack.ai/migrations/crm/salesflare/to/hubspot) [Podio to HubSpot](https://flitstack.ai/migrations/crm/podio/to/hubspot) [Realvolve to HubSpot](https://flitstack.ai/migrations/crm/realvolve/to/hubspot) [Less Annoying CRM to HubSpot](https://flitstack.ai/migrations/crm/less-annoying-crm/to/hubspot) [Creatio to HubSpot](https://flitstack.ai/migrations/crm/creatio/to/hubspot) [MyCase to HubSpot](https://flitstack.ai/migrations/crm/mycase/to/hubspot) [![](https://flitstack.ai/platforms-trim/bsi-crm.webp) BSI CRM to HubSpot](https://flitstack.ai/migrations/crm/bsi-crm/to/hubspot) [Bigin by Zoho CRM to HubSpot](https://flitstack.ai/migrations/crm/bigin-by-zoho-crm/to/hubspot) [![](https://flitstack.ai/platforms-trim/moengage.webp) MoEngage to HubSpot](https://flitstack.ai/migrations/crm/moengage/to/hubspot) [![](https://flitstack.ai/platforms-trim/ontraport.webp) Ontraport to HubSpot](https://flitstack.ai/migrations/crm/ontraport/to/hubspot) [Mautic to HubSpot](https://flitstack.ai/migrations/crm/mautic/to/hubspot) [SuiteDash to HubSpot](https://flitstack.ai/migrations/crm/suitedash/to/hubspot) [Accelo to HubSpot](https://flitstack.ai/migrations/crm/accelo/to/hubspot) [Teamleader to HubSpot](https://flitstack.ai/migrations/crm/teamleader/to/hubspot) [BlinQ to HubSpot](https://flitstack.ai/migrations/crm/blinq/to/hubspot) [Brivity to HubSpot](https://flitstack.ai/migrations/crm/brivity/to/hubspot) [![](https://flitstack.ai/platforms-trim/entrata.webp) Entrata to HubSpot](https://flitstack.ai/migrations/crm/entrata/to/hubspot) [![](https://flitstack.ai/platforms-trim/monica-crm.webp) Monica CRM to HubSpot](https://flitstack.ai/migrations/crm/monica-crm/to/hubspot) [Cliniko to HubSpot](https://flitstack.ai/migrations/crm/cliniko/to/hubspot) [![](https://flitstack.ai/platforms-trim/boomtown.webp) BoomTown to HubSpot](https://flitstack.ai/migrations/crm/boomtown/to/hubspot) [![](https://flitstack.ai/platforms-trim/listrak.webp) Listrak to HubSpot](https://flitstack.ai/migrations/crm/listrak/to/hubspot) [Sage CRM to HubSpot](https://flitstack.ai/migrations/crm/sage-crm/to/hubspot) [![](https://flitstack.ai/platforms-trim/jobnimbus.webp) Jobnimbus to HubSpot](https://flitstack.ai/migrations/crm/jobnimbus/to/hubspot) [GoCanvas to HubSpot](https://flitstack.ai/migrations/crm/gocanvas/to/hubspot) [![](https://flitstack.ai/platforms-trim/espocrm.webp) EspoCRM to HubSpot](https://flitstack.ai/migrations/crm/espocrm/to/hubspot)

## What HubSpot supports, and where its import tools stop

- Lowest barrier to entry of any major CRM — the free tier with unlimited contacts lets teams validate fit before committing to a paid plan, according to G2 and Capterra reviewers.
- Native integration between the CRM and sales engagement tools (sequences, email tracking, dialer) means no separate sync configuration, a theme across G2 Sales Hub reviews.
- Pipeline visualization, deal tracking, and automated workflows are consistently praised as intuitive and easy to set up without developer involvement.
- Strong onboarding for new team members — reviewers on Capterra and G2 highlight how quickly new reps become productive without formal training.

**Bulk API** OAuth 2.0 (required for marketplace apps and recommended for all production integrations). Private app static auth tokens are supported for single-account installations. Legacy API keys are deprecated.

**Rate limits** 110 requests per 10 seconds per installed account for OAuth apps on the latest platform versions (2025.2 / 2026.03). Free accounts: 100 req/10s and 250,000 daily requests. Professional and Enterprise: 190 req/10s. The CRM Search API has a separate ceiling of 4 requests per second per auth token. 429 is returned on exhaust.

| Object                                      | Support | Note                                                                                                                                                                                                                                                                                                                    |
| ------------------------------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Contacts                                    | full    | HubSpot's foundational object. We migrate all standard and custom contact properties. We apply the marketing-contact billing flag at import time to prevent customers from being charged for contacts that should remain non-marketing records.                                                                         |
| Companies                                   | full    | Companies are linked to contacts via associations. We preserve all company properties and the contact-to-company associations during import. HubSpot allows personalized object names (e.g., 'Account' instead of 'Company'), which we map from the source schema.                                                      |
| Deals                                       | full    | We migrate deal records with all associated properties, pipeline stages, and owner assignments. We validate that the target plan supports the pipeline count: Professional allows 15 pipelines, Enterprise allows 100, Starter allows 1.                                                                                |
| Leads (Sales Hub Enterprise)                | mapped  | Leads is a distinct object introduced in 2023 and only available on Sales Hub Enterprise. Where the destination CRM does not have a separate Lead object, we merge Leads into Contacts and preserve Lead\_Status as a custom Contact property.                                                                          |
| Activities (Emails, Calls, Meetings, Tasks) | mapped  | Activities are first-class objects in HubSpot but are not supported by HubSpot's native CSV importer. We migrate them via the CRM API in chronological batches, handling token-bucket rate limits (100-200 req/10sec burst, 4 req/sec on search endpoints) to preserve the activity timeline for each contact and deal. |
| Custom Objects                              | mapped  | Custom objects are Enterprise-only in HubSpot. We can migrate custom object records via the v2 custom objects API, but the custom object schema must already exist in the target HubSpot portal. We create the schema definition before migrating any records.                                                          |
| Pipelines                                   | mapped  | We migrate pipeline configurations including all stages, stage probabilities, and custom pipeline properties. The target plan tier limits apply: Starter is capped at 1 pipeline, Professional at 15, Enterprise at 100.                                                                                                |
| Products and Line Items                     | full    | Products and line items are migrated as associated records linked to deals. We preserve the product catalog and all deal-product associations during import.                                                                                                                                                            |
| Tickets                                     | full    | Tickets migrate with all custom ticket fields, conversations, and team assignments. We handle the ticket pipeline stages separately from the deal pipeline.                                                                                                                                                             |
| Owners                                      | mapped  | Owner records must exist in HubSpot before deals and contacts can be assigned to them. We migrate owner records first and resolve any missing owner references before importing associated records.                                                                                                                     |
| Tags                                        | full    | HubSpot supports tag-based categorization across objects. We migrate tags as flat string arrays and apply them to the corresponding records during import.                                                                                                                                                              |
| Engagement Sequences                        | mapped  | Sequences are Professional-gated and are not data objects in the traditional sense — they are templates. We migrate sequence templates as configuration, not as enrolled records. Active enrollments are not migratable across CRMs.                                                                                    |

## The HubSpot migration guide

## Why teams migrate to HubSpot

*The four shapes a HubSpot migration takes, and what makes the platform easier — or harder — than the category average.*

HubSpot, Inc. was founded by Brian Halligan and Dharmesh Shah in 2006 and is headquartered in Cambridge, Massachusetts[1](https://flitstack.ai/migrations/crm/hubspot#source-1). Sales Hub is the sales-side product inside a broader suite that also includes Marketing Hub, Service Hub, Content Hub and Data Hub, all sharing the same underlying CRM.

The typical Sales Hub customer is a mid-market revenue team — 25 to 500 reps — that wants pipeline, sequences and reporting wired to inbound marketing without standing up a Salesforce-style admin function. Compared with Salesforce Sales Cloud, HubSpot positions itself on faster time-to-value and a flatter learning curve; compared with Pipedrive or Zoho, it positions on a deeper Marketing/Service overlay and a Custom Objects model that scales further on Enterprise tiers.

The shapes of migration that actually land on HubSpot tend to fall into four patterns. First, consolidation projects: a company replacing a stack of Pipedrive plus Mailchimp plus a Zendesk-style inbox with HubSpot's combined Smart CRM. Second, Salesforce exits, driven by total cost of ownership on smaller teams that never used Apex or flows heavily[26](https://flitstack.ai/migrations/crm/hubspot#source-26).

Third, legacy replacements — Act!, SugarCRM, Microsoft Dynamics on-prem, or homegrown databases — where the source schema is loose and the project is really a re-architecture. Fourth, M\&A integration, where an acquired business runs on a different CRM and the parent standardises on HubSpot. Each shape has a different difficulty profile: a Pipedrive migration usually has clean object parity but messy custom-field labels, while a Salesforce migration has rich automation that does not move across at all.

What makes migrating to HubSpot easier than the category average is the import tool itself — it accepts CSV and Excel, handles multi-object files via cross-reference columns, and has tier-scaled file and row limits that go up to 512 MB and 10 million rows per day on paid plans[2](https://flitstack.ai/migrations/crm/hubspot#source-2).

What makes it harder than the average is the contacts-based pricing model, which can punish teams that bring in stale lists or fail to set marketing-versus-non-marketing status correctly during the load[26](https://flitstack.ai/migrations/crm/hubspot#source-26), and the picklist (enumeration) value architecture, which uses internal values that diverge from display labels and will silently swallow any mismatch.

Workflows, sequences, reports and lead-scoring rules do not import — they are rebuilt from documentation. Teams that scope for that work up front finish on time; teams that assume parity do not.

> Teams that scope for the rebuild work up front finish on time; teams that assume parity do not.

## The HubSpot data model you need to map into

*Objects, properties, associations, and the upsert keys you'll wire on every field — the destination schema decoded.*

HubSpot's CRM is built around a small set of standard objects, each with default and custom properties, and associations that connect them. Sales Hub adds object access and pipeline behaviour on top of the same shared schema used by Marketing and Service Hubs.

Before you can map a field on the source side, you need to know exactly which destination object the row belongs on, what properties it requires, and which value will serve as its upsert key. The table below summarises the objects you will touch in a Sales Hub migration.

| Object                                             | What it stores                                   | Required                                        | Tier                                       |
| -------------------------------------------------- | ------------------------------------------------ | ----------------------------------------------- | ------------------------------------------ |
| Contacts                                           | Individual people — leads, prospects, customers  | One of: email, first name, last name            | All tiers                                  |
| Companies                                          | Organisations associated with contacts and deals | Name or domain                                  | All tiers                                  |
| Deals                                              | Revenue opportunities in a pipeline              | Deal name, pipeline, deal stage                 | All tiers                                  |
| Tickets                                            | Service / support issues                         | Ticket name, pipeline, status                   | All tiers (Service Hub for full tooling)   |
| Products                                           | Catalogue of sellable items                      | Name, unit price                                | All paid tiers                             |
| Line Items                                         | Product instances on a deal or quote             | Product ID, quantity, price                     | All paid tiers                             |
| Quotes                                             | Customer-facing quote documents                  | Quote name, deal association                    | Sales Hub Starter+                         |
| Activities (calls, emails, meetings, notes, tasks) | Engagement timeline events                       | Type, timestamp, owner                          | All tiers; bulk import limits per tier     |
| Custom Objects                                     | Customer-defined record types                    | Schema defined first; per-property requirements | Enterprise (and some Pro add-on scenarios) |

Contacts use email as the default unique identifier — two rows with the same email collapse into one record on import[2](https://flitstack.ai/migrations/crm/hubspot#source-2). Companies use company domain name as their default unique identifier.

Deals, Tickets and Custom Objects do not have a natural unique key, so you should plan to either let HubSpot assign Record IDs and store them back in the source, or create a custom property of type single-line text, mark it Require unique values for this property, and use it as your external ID.

Once a property is created, you cannot retroactively make it unique — you create a new property with the unique setting on and copy values into it via a workflow. Plan for this on day one of the project.

When you import, HubSpot upserts on the unique identifier column: if a matching record exists, it updates; if not, it creates. You can also import the HubSpot Record ID as the match key when re-importing your own export — Record ID is the canonical primary key and bypasses email/domain matching entirely. Custom property types determine validation and storage; the catalogue below covers what you can model and the limits you need to plan around.

| Field type                   | Limit                              | Notes                                                                                                                   |
| ---------------------------- | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Single-line text             | 65,536 chars via CRM/import        | Stores any alphanumeric string[6](https://flitstack.ai/migrations/crm/hubspot#source-6)                                 |
| Multi-line text              | 65,536 chars via CRM/import        | Line breaks unsupported in marketing emails, quotes, sequences[6](https://flitstack.ai/migrations/crm/hubspot#source-6) |
| Number                       | 17 significant digits              | Numeric filters: before/after/between                                                                                   |
| Date picker                  | Midnight UTC stored                | Date-only; timezone-stripped                                                                                            |
| Datetime                     | ISO-8601 with offset               | Required for programmatic loads; UI accepts looser formats                                                              |
| Single-select (enumeration)  | 1,000 options                      | Internal value differs from display label                                                                               |
| Multi-select (checkbox)      | 1,000 options                      | Semicolon-delimited on import                                                                                           |
| Calculation / score          | Enterprise only for advanced types | Does not import — rebuild as formula property                                                                           |
| Custom properties per object | Max 1,000 per object               | Across all custom property types                                                                                        |

Relationships in HubSpot are modelled as associations with optional association labels (for example, a contact labelled Decision Maker on a deal)[9](https://flitstack.ai/migrations/crm/hubspot#source-9). Associations support cardinality limits per association type — HubSpot recently lifted the per-record association cap from 10,000 to 50,000 in most cases, but high-volume B2C wholesale scenarios still bump that ceiling and require splitting[10](https://flitstack.ai/migrations/crm/hubspot#source-10).

**50,000** Associations per record Raised from 10,000 in late 2025. Still bites B2C wholesale (60,000+ orders per company) and deep account hierarchies — additional associations silently fail once you cross the ceiling.

Custom Objects (Enterprise) participate in associations the same way standard objects do, including the same upsert and label semantics. There is no native master-detail cascade-delete: deleting a parent does not delete children, which is a behaviour you need to reproduce in workflows if your source platform relied on it.

## Pre-migration prep — the work before you touch HubSpot

*What must be true on the source, the destination, and across the team before the first row hits the import tool.*

The single best predictor of a clean Sales Hub migration is how much work you do on the source side before the first import button is pressed. HubSpot publishes its own warning that more than half of CRM data quality issues trace to the initial import, and the fix is almost always pre-processing rather than post-cleanup.

> The single best predictor of a clean migration is how much work you do before the first import button is pressed.

Treat the source export as raw material that needs to be shaped to HubSpot's expected formats — email lowercased, phone normalised to E.164, picklist values converted to HubSpot internal values, dates rewritten to ISO-8601, owners resolved to HubSpot user IDs or emails.

### Source-side prep

- Audit and dedup the source database before export — third-party tools like Insycle and Koalify are built specifically for HubSpot-bound dedup and can find email-case-only duplicates that HubSpot's importer will silently merge.
- Normalise emails to lowercase, trim whitespace, and strip role-based addresses (info@, sales@) that you do not want flooding marketing contacts. HubSpot lowercases on import but matches before you can intervene.
- Convert picklist display labels to HubSpot internal values for every enumeration field — lifecycle stage, deal stage, lead status, custom dropdowns. HubSpot rejects display labels silently on programmatic loads and partially against the UI.
- Stamp a stable external ID on every record in the source export — a UUID or the source platform's primary key — so re-runs and reconciliation are deterministic.
- Decide what is in scope for historical activities. Calls, emails, meetings, notes and tasks can be imported with a backdated Activity Date, but each row costs an activity create call and counts against daily import limits[2](https://flitstack.ai/migrations/crm/hubspot#source-2).

### Destination-side prep

- Create a sandbox from Settings → Account Management → Sandboxes (Enterprise) or use a standard development account on lower tiers. A sandbox is a full copy of production used to dry-run the import end-to-end.
- Provision users first, ideally with automated provisioning through Okta, Microsoft Entra ID or another identity provider, and create permission sets before importing — owner assignment fails silently if a referenced owner does not exist in HubSpot[13](https://flitstack.ai/migrations/crm/hubspot#source-13).
- Pre-create every custom property on the right object with the right type — single-line text vs multi-line text vs single-select matters because HubSpot will not let you change a created property's type later for many combinations.
- Build pipelines and deal stages before importing any deals — HubSpot rejects deal rows whose Deal Stage internal value does not exist on the specified pipeline.
- Define Custom Objects, their unique-ID properties, and their associations before importing. Custom Object schemas have to exist before records of that type can be created.

### People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — typically 24 to 72 hours — and communicate it to every department that touches the CRM. Train sales reps on HubSpot daily-workflow tasks, deal management and pipeline reporting before go-live, not after. A typical small-business migration runs one to two business days; a complex multi-pipeline, multi-team migration runs two to four weeks of elapsed time even when the technical work is faster. Build the human runway accordingly.

## Import mechanisms: UI wizard, CSV, and programmatic loads

*Several paths in, each with different limits and shapes. Picking the wrong one is how mid-migrations stall at scale.*

HubSpot exposes several load paths and the right one depends on dataset size, object mix, and whether you need to re-run idempotently. The UI Import Tool covers most one-shot migrations under a few hundred thousand records. Programmatic loads handle large, repeatable volumes. Third-party tools sit on top of both and add staging, transformation and dedup layers.

### UI Import Tool

The native import lives at Settings → Data Management → Data Integration → Import, or by clicking Import in the top right of any object index page. There are two modes: Quick Import for a single object with auto-mapped property names, and Advanced Import for full mapping control, multi-object files, and association creation. Quick Import requires one of First Name, Last Name, or Email in the file. Advanced Import accepts CSV, XLS and XLSX.

Limits are tier-scaled: free accounts get 20 MB files, 50 imports/day and 500,000 rows/day; Starter, Professional and Enterprise accounts get 512 MB files, 500 imports/day, 10,000,000 rows/day, and up to 1,048,576 rows per individual file[2](https://flitstack.ai/migrations/crm/hubspot#source-2). Up to three imports run simultaneously, and only two can exceed 10,000 rows[2](https://flitstack.ai/migrations/crm/hubspot#source-2). The right call: UI for one-shot loads under 100k records on standard objects, or any time you want a visual mapping review before commit.

### Programmatic CRM imports and batch operations

There are two programmatic patterns. The Imports surface takes a metadata payload plus a file upload and runs the same engine as the UI — same mapping model, same daily limits, except programmatic imports can push up to 80,000,000 rows/day on paid tiers[2](https://flitstack.ai/migrations/crm/hubspot#source-2) [5](https://flitstack.ai/migrations/crm/hubspot#source-5).

The second pattern is per-object batch operations: create, update, and upsert. Batch calls accept up to 100 records per call for most objects, but contacts are limited to 10 records per call for create and update[14](https://flitstack.ai/migrations/crm/hubspot#source-14). Batch upsert requires the request to specify which property is the unique identifier; missing that property returns `Updates in a single batch must specify its unique property.` [16](https://flitstack.ai/migrations/crm/hubspot#source-16).

**100 / 10** Records per batch call 100 for most objects, but contacts cap at 10 per call for create and update — a constraint that catches teams who size parallelism off the more generous number.

The platform-wide throughput ceiling on paid Marketing/CMS/Sales/Service Hubs is roughly 100 operations per 10 seconds on private-app tokens; respect the throttle response headers and back off on too-many-requests responses[15](https://flitstack.ai/migrations/crm/hubspot#source-15). Choose the programmatic path when the load is over 100k records, when Custom Objects are involved, or when the migration needs to be repeatable and audit-logged from your side.

### Third-party staging tools

Tools like Fivetran, Airbyte, Stitch, Integrate.io and Workato sit between the source and HubSpot. They are commonly used in two ways: (a) reverse-ETL where the source database is loaded into a warehouse, transformed in SQL, then synced into HubSpot programmatically; and (b) staging-and-validate, where the tool handles file generation, type coercion and dedup before the result is fed to HubSpot.

For one-time migrations, the value is in repeatability under failure; for ongoing syncs (the post-migration phase), they become the system of integration.

Under 10,000 records on standard objects → UI Import Tool. 10,000–100,000 → UI Advanced Import in batches. Over 100,000, any Custom Objects, or any re-runnable load → programmatic imports or batch operations.

## Mapping your data into HubSpot

*The longest section — because field mapping is where almost every migration that fails actually breaks.*

Mapping is where every migration earns its scars. The schema decisions you make in your mapping spreadsheet determine whether reports work on day two, whether automations fire correctly on day five, and whether your sales team trusts the data on day thirty.

Work object by object, top to bottom of the import order: Companies first (so deals and contacts can associate to them), then Contacts, then Deals, then Activities, then Custom Objects and Line Items.

### Contacts

| Source                   | Destination                              | Note                                                                                             |
| ------------------------ | ---------------------------------------- | ------------------------------------------------------------------------------------------------ |
| email                    | email (unique identifier)                | Lowercased on import; upsert key by default                                                      |
| first\_name / last\_name | firstname / lastname                     | Underscores are stripped in HubSpot internal names                                               |
| phone                    | phone                                    | Normalise to E.164 before import                                                                 |
| owner / account\_owner   | hubspot\_owner\_id                       | Map by user email or HubSpot user ID; pre-provision users                                        |
| lifecycle / status       | lifecyclestage                           | Map to internal values (lead, marketingqualifiedlead, opportunity, customer), not display labels |
| created\_at              | Capture in a custom property             | createdate is system-managed and cannot be overwritten on standard import                        |
| source / utm\_source     | hs\_analytics\_source or custom property | Original-source properties are HubSpot-managed for tracked visitors                              |
| marketing opt-in flag    | Marketing contact status                 | Drives billing — set during import or risk tier upgrade                                          |

### Companies

| Source           | Destination                | Note                                                              |
| ---------------- | -------------------------- | ----------------------------------------------------------------- |
| company\_name    | name                       | Required if domain is absent                                      |
| website / domain | domain (unique identifier) | HubSpot strips http(s):// and www. on match                       |
| industry         | industry                   | Single-select; map to HubSpot enum values                         |
| annual\_revenue  | annualrevenue              | Number; strip currency symbols and thousands separators           |
| parent account   | Parent company association | Use Record ID or domain in a second import to set the association |

### Deals and pipelines

Recreate every pipeline and every deal stage in HubSpot before importing deals. Each deal stage has an internal value (often `appointmentscheduled`, `qualifiedtobuy`, `closedwon`, `closedlost`) and a numeric probability. Build the mapping table source-stage → HubSpot-pipeline + HubSpot-stage-internal-value. Deals that target a non-existent stage on the named pipeline are rejected with `INVALID_DEAL_STAGE`.

If you are consolidating multiple source pipelines, the cleanest approach is to keep them as separate HubSpot pipelines for at least 90 days post-migration, then merge once reporting has stabilised.

| Source                         | Destination         | Note                                                             |
| ------------------------------ | ------------------- | ---------------------------------------------------------------- |
| deal\_name / opportunity\_name | dealname            | Required                                                         |
| stage / pipeline\_stage        | dealstage           | Use internal value, not label                                    |
| amount                         | amount              | Number; respect deal currency and precision                      |
| close\_date                    | closedate           | ISO-8601 with timezone for programmatic loads; epoch ms accepted |
| owner                          | hubspot\_owner\_id  | Map by user email; deal owner controls forecasting               |
| primary\_contact               | Contact association | Set via cross-reference column in multi-object import            |
| account / organisation         | Company association | Use company domain or Record ID                                  |

### Custom-field mapping strategy

Resist the urge to map every source custom field one-to-one. Migrate only the custom properties used by an active process or report in the last 12 months. Excess properties weaken governance, slow down workflows, and make Breeze AI and HubSpot's reporting less effective.

For picklist fields whose source values do not match the destination, either: (1) extend the destination picklist with the missing internal values, (2) collapse adjacent values during transform, or (3) introduce a parallel custom property that holds the legacy value verbatim. Calculation properties (formulas) do not import — HubSpot recomputes them on-platform — so any source formula must be rebuilt as a HubSpot calculation property on Enterprise or replicated via workflow on lower tiers.

### Historical activities — emails, calls, meetings, notes, tasks

HubSpot supports importing activities with their original timestamps via the Activity Date property — this is the field that determines where the engagement appears on the contact timeline[23](https://flitstack.ai/migrations/crm/hubspot#source-23). For Gmail-resident historical email, HubSpot ships a dedicated Historical email import onboarding tool that pulls threads from Gmail and attaches them to the matching contact.

For calls and meetings logged in a source CRM, build a multi-object import where each row carries the activity body, owner, Activity Date, Activity Type, and the contact email/Record ID it associates with. Meetings additionally require an owner column mapped to Activity assigned to or the row is rejected. Email body fields will accept HTML; rich-text formatting from sources like Outlook may need to be converted to plain text first to avoid display issues.

### Files and attachments

Attachments do not import in bulk via the CSV UI flow. The supported path is the Files surface, which uploads a binary and returns a file ID that can then be attached to a Note and associated with the parent record[18](https://flitstack.ai/migrations/crm/hubspot#source-18). Individual document size cap is 250 MB for trackable documents[18](https://flitstack.ai/migrations/crm/hubspot#source-18); one-to-one email attachments are capped at around 20 MB.

Plan for storage tier consumption — Files counts against the account's overall file storage allowance, which is tier-dependent. For large attachment estates (hundreds of GB), the pattern most teams adopt is: keep originals in S3 or Google Drive, store a deep link in a custom URL property on the HubSpot record, and only inline-upload the most recent or most-referenced subset.

### Audit trail, ownership and original timestamps

Standard `createdate`, `hs_object_id`, `hs_createdate` and `hs_lastmodifieddate` are HubSpot-managed system properties — they cannot be overwritten during import[3](https://flitstack.ai/migrations/crm/hubspot#source-3). If you need to preserve the original audit trail, the pattern is to create two custom properties per object, Legacy Created Date and Legacy Created By, and populate them from the source export.

Owner assignment during import works only if the owner email or HubSpot user ID exists at the moment of import; rows whose owner cannot be resolved are imported with no owner set, which silently breaks downstream owner-based workflows.

Account-level activity audit logging is Enterprise-only[25](https://flitstack.ai/migrations/crm/hubspot#source-25) — lower tiers can see import-level history in Settings → Imports but not granular per-property change history.

### CRM-specific: lead scoring, sequences, email/calendar sync

Lead-scoring models do not import — they are rebuilt in HubSpot's score property type, configurable in Settings → Properties → HubSpot Score. Plan to recreate the rule logic from your source platform documentation rather than trying to migrate accumulated score values; if you must preserve historical scores, put them in a Legacy Lead Score custom number property and leave the new HubSpot score to accrue forward.

Sequences (the cadence tool) do not have an import mechanism either — recreate the structure manually and re-enroll active prospects post-cutover.

Email and calendar sync (Gmail/Outlook) is set up per user under Settings → General → Email and Calendar after users are provisioned; do not enable it during the import window or you will get a flood of duplicate emails as the connector backfills against the same contacts you are loading.

## The pitfalls that derail HubSpot migrations

*Nine specific failure modes — ranked by impact, each tied to the exact HubSpot mechanism that breaks.*

**high Picklist display labels imported instead of internal values**

HubSpot enumeration properties — lifecycle stage, deal stage, lead status, every custom dropdown — store an internal value distinct from the display label. The label is `Appointment Scheduled`; the internal value is `appointmentscheduled`. Programmatic loads reject label-only payloads silently with no field-level error message, and the UI import accepts some labels case-sensitively but not others. Build your transform layer against the destination property's internal values, never against what an admin sees in the UI.

**high Batch upsert without a unique identifier**

The contact batch upsert operation requires the request to declare which property is the unique identifier. Forgetting it returns `Updates in a single batch must specify its unique property.` and the entire batch is rejected. The same payload via the create-only operation will instead create duplicate contacts for any record that already existed. Use contact batch upsert with `idProperty=email` (or your custom unique property) and validate with a 10-row dry run before scaling[16](https://flitstack.ai/migrations/crm/hubspot#source-16).

**high Contact-tier billing trip from marketing-contact mis-flagging**

HubSpot bills based on marketing contacts — contacts you actively email or market to. If you import a stale list and forget to set Marketing contact status to non-marketing on rows that should not count, your contact tier silently increases on the next billing cycle and you are billed the annual amount at the next tier with no clean way to undo the upgrade until renewal. Always import with an explicit marketing-contact column and audit the count against your contract tier before the import.

**high 10-record cap on contact create/update batch**

Most CRM batch operations accept 100 records per call, but contacts create and update are limited to 10 per call — a long-standing platform-wide constraint that catches teams who size their parallelism off the more generous 100-record cap[14](https://flitstack.ai/migrations/crm/hubspot#source-14). A migration loop tuned to 100 will return an error or partial-success response on every contact call. Drop the contact batch to 10 and increase parallelism to compensate, respecting the per-private-app throughput ceiling[15](https://flitstack.ai/migrations/crm/hubspot#source-15).

**high createdate cannot be overridden**

Standard `createdate`, `hs_object_id`, `hs_createdate` and `hs_lastmodifieddate` are HubSpot-managed and ignored if you send them during import. Teams discover this on day two when reports filtered by Created Date return everything stamped to import day. The mitigation is to create Legacy Created Date and Legacy Modified Date custom datetime properties on every object, populate them from the source export, and rewrite all historical-period reports to use the legacy fields[3](https://flitstack.ai/migrations/crm/hubspot#source-3).

**medium Associations capped at 50,000 per record on most types**

HubSpot raised the per-record association cap from 10,000 to 50,000 in late 2025, but the ceiling still exists and bites wholesale B2C scenarios where one company has 60,000+ orders, or large account hierarchies with very high contact counts per parent[10](https://flitstack.ai/migrations/crm/hubspot#source-10). Once you hit the cap, additional associations silently fail. Detect this in advance: count associations per parent in the source export and split the parent or restructure the relationship before importing.

**medium Search throughput drag during reconciliation**

Practitioners pulling Deals, Companies, Contacts and Associations in parallel for daily-refresh reconciliation report 2–3 hour runs even on small databases. The CRM Search surface carries tighter throughput ceilings than basic list reads, and naive code that uses Search where List would do gets throttled fast. Use list reads with cursor pagination for full-table pulls, reserve Search for filtered queries, and respect the response headers[15](https://flitstack.ai/migrations/crm/hubspot#source-15).

**medium EU data residency cannot be flipped after account creation**

HubSpot offers a Frankfurt data centre for EU customers and a US centre for everyone else[20](https://flitstack.ai/migrations/crm/hubspot#source-20). New accounts choose at signup. Existing customers can request a one-time migration via a HubSpot-run data migration tool, but this is scheduled by HubSpot, not initiated on demand. If your migration is into an account already created in the wrong region, plan for the regional migration before the data migration, or you will move 500,000 rows twice[21](https://flitstack.ai/migrations/crm/hubspot#source-21).

**low Free-tier 30-day activity retention loses historical timeline**

HubSpot's free Smart CRM now caps activity retention at 30 days, meaning calls, emails and meetings older than 30 days disappear from the contact timeline on free accounts[22](https://flitstack.ai/migrations/crm/hubspot#source-22). If your migration target is the free tier or a downgrade is plausible, your historical activity import is effectively temporary. Either land on a paid tier, or treat free as a transient staging environment and plan paid-tier activation before activity data ages out.

## Validation and cutover

*What to verify after the import job, in what order — and how to fail safely when something is wrong.*

Validation is the bridge between the import finishing and users being allowed in. HubSpot's own field engineers recommend a three-stage validation: a test load of 10 percent of records with stakeholder spot-checks, the full load with real-time monitoring of record counts and association integrity, and a 30-day post-migration data-quality audit. The most reliable signal is having department reps verify their own records — they know what right looks like better than any reconciliation script.

Build a reconciliation queries spreadsheet that compares source and destination on each of these counts. Anything outside a 0.5 percent variance gets investigated before users get login access.

- Total contacts imported vs source — minus deliberately excluded rows (role-based emails, bounced lists, opt-outs).
- Total companies imported vs source — checking that domain-based collapse did not over-merge.
- Total deals per pipeline per stage vs source, plus sum of amount per pipeline — a non-trivial dollar variance usually signals a stage-mapping error or a currency-precision drop.
- Total activities per type (calls, emails, meetings, notes, tasks) imported vs source — and a date-bucketed comparison to confirm Activity Date round-tripped.
- Associations per object type — count contact→company, contact→deal and company→deal associations and compare against the source-derived expected counts.
- Owner distribution — `GROUP BY hubspot_owner_id` and confirm no record landed unowned that should not have.
- Unique-identifier integrity — count distinct emails on contacts, distinct domains on companies; any duplicates indicate the dedup transform missed cases.

On top of reconciliation, run a manual spot-check protocol: pick 30 random records across objects and verify each field against the source UI. Pick five high-value deals and trace the full association graph — contact, company, line items, activities. If a non-trivial discrepancy shows up in three or more of the 30, halt the load, fix the root cause, and re-import the affected rows by Record ID.

HubSpot now ships Restore CRM Properties and Records, which captures the last 20 versions of every CRM property change (45 for contacts) and lets super admins undo changes from the last 14 days via Settings → Data Management → Backup and Restore[24](https://flitstack.ai/migrations/crm/hubspot#source-24). This is the closest thing to a native undo, but it is not a bulk-rollback button — it works property-by-property.

The real rollback strategy remains: export everything to S3 before the import starts, stamp every imported row with an Import Batch ID custom property, and if catastrophe strikes, bulk-delete by that batch ID and re-import from the cleaned source.

Cutover sequencing: (1) source goes read-only and the team is notified; (2) final delta export captures everything that changed during the test-import window; (3) delta is imported; (4) reconciliation runs; (5) users get login access and a 48-hour hyper-care window with the migration lead on call; (6) source decommission is scheduled for 30 to 90 days out, never the same day.

## Migration partners and tools

*Elite Partners, iPaaS vendors, specialist migration shops — what each is good for and how to choose.*

The HubSpot Solutions Partner Program tiers Elite, Diamond, Platinum and Gold partners by certifications, customer count and revenue. For Sales Hub migrations specifically, partners with explicit Salesforce-to-HubSpot, Marketo-to-HubSpot or Pipedrive-to-HubSpot practices tend to ship cleaner than generalist implementation shops.

SmartBug Media (Elite), Hyperscayle (Platinum), Incremental (Platinum), TransFunnel and Integrate IQ are commonly named in the migration corner of the market and each offers fixed-scope migration packages alongside ongoing managed services. HubSpot also runs an in-house Onboarding service with a published fee of roughly $3,000–$7,000 depending on tier; some partners waive that fee in exchange for the implementation contract.

On the ETL and iPaaS side, Fivetran, Airbyte, Stitch, Integrate.io, Workato and MuleSoft all have HubSpot connectors. Their role in a migration is rarely the migration itself — it is the staging layer that lands source data into a warehouse, the transformation layer that converts picklist values and resolves owner IDs, and the ongoing-sync layer that takes over once the one-time migration is complete.

Airbyte and Fivetran are common picks for warehouse-first teams; Workato is common where the migration is bundled with workflow automation rebuilds.

Managed-migration cost ranges vary widely. A clean Pipedrive-to-HubSpot move of under 25,000 contacts with no historical activities and standard objects only often lands in the £2,500–£7,500 / $3,000–$10,000 range with a setup fee plus per-object pricing. A Salesforce-to-HubSpot project with deal history, custom objects, historical activities and Marketo decoupling typically runs $25,000–$120,000, with the upper end driven by record count, custom-field complexity, historical-data depth and the number of integrations that need rebuilding rather than re-pointed.

For teams that want to outsource the migration end-to-end, FlitStack specialises in HubSpot migrations and handles the field mapping, historical-data preservation, picklist internal-value conversion, and validation work described in Sections 5 and 7 of this guide. Pricing is fixed-fee, based on record count and source platform, with separate line items for Custom Objects and historical activity depth so the scope is transparent before signature.

This is one of several legitimate paths — the right choice for any given team depends on whether they want an Elite Partner, an in-house onboarding service, an iPaaS-first approach, or a specialist migration vendor. \[Explore FlitStack →]\(/contact)

In this guide

## HubSpot migration checklist

A phased punch list for migrating contacts, companies, deals, tickets, custom objects, activities, and files into HubSpot using its native Import Tool. Typical timeline: 4–12 weeks.

0\. Decide & Plan 9 tasks

- **Define migration scope by HubSpot object.** List every object in scope: Contacts, Companies, Deals, Tickets, Products, Line Items, Quotes, Custom Objects, and activities (notes, calls, emails, meetings, tasks). Document each as in-scope or out-of-scope in writing.*If skipped: Unscoped objects surface mid-migration and force re-export, re-mapping, and an extended freeze window.*
- **Decide historical-activity scope and time horizon.** Pick a hard cutoff (for example: last 24 months of emails, calls, notes, meetings). Activities can be imported but timestamps and threading behave differently per type.*If skipped: Loading all-time activity history multiplies row counts and can push the project past contact-tier limits without warning.*
- **Confirm HubSpot subscription tier and Marketing Contacts allocation.** Marketing Contacts and overall contact ceilings are billed per tier. Overage triggers an immediate tier upgrade that cannot be reversed until renewal.*If skipped: Importing past the Marketing Contacts ceiling auto-bills the next tier for the full annual term.*
- **Choose data residency: US (na1) or EU (Frankfurt) data center.** New portals can be provisioned in the EU data center. Existing portals require an opt-in residency migration. Decide before provisioning the destination portal.*If skipped: Provisioning in the wrong region forces a separate residency migration after cutover, doubling the project.*
- **Document success criteria for the migration.** Define falsifiable acceptance tests: per-object row count match, total pipeline value parity, association integrity sample pass rate, and UAT sign-off from named owners.
- **Set cutover date, freeze window, and rollback decision point.** Pick the freeze date for source-system writes, the cutover weekend, and the hour by which a no-go call must be made if validation fails.*If skipped: Without a pre-agreed rollback gate, teams push through partial loads and create reconciliation work that takes weeks.*
- **Assign a single accountable owner (DRI) and stakeholder list.** Name one DRI for the migration plus named owners for sales ops, marketing ops, RevOps, IT/security, and legal/compliance.
- **Identify legal and compliance constraints.** Capture GDPR data-residency requirements, HIPAA BAA scope if healthcare data is in play, SOC 2 evidence needs, and any per-jurisdiction retention rules.*If skipped: Late-discovered HIPAA scope can force a portal rebuild because Sensitive Data settings cannot be retro-applied to all properties.*
- **Document explicit out-of-scope items.** Write down what is NOT migrating (dead leads older than X, deprecated custom fields, archived tickets, etc.) so it does not creep back in.

1\. Pre-Migration Prep 22 tasks

- **Export baseline record counts per source object.** Capture a snapshot of contact, company, deal, ticket, activity, and attachment counts on a known date. This is the reconciliation anchor for Phase 6.*If skipped: Without a baseline, post-migration delta investigation has nothing to compare against.*
- **Run dedup analysis on source contacts using email as match key.** Lowercase emails and trim whitespace before matching. Resolve duplicates in the source so HubSpot does not auto-merge or silently drop on import.*If skipped: HubSpot uses email as the contact unique key — duplicates in the source collapse on import and history attaches to the wrong record.*
- **Run dedup on source companies using primary domain.** HubSpot deduplicates companies on Company Domain Name by default. Standardize domains (strip www, lowercase) before export.*If skipped: Multiple source companies sharing a domain merge into one HubSpot company, losing per-entity context.*
- **Standardize email casing, phone formats, and country codes.** Lowercase all emails, normalize phone numbers to E.164, and use ISO-3166 country codes. HubSpot validation rules reject mis-typed values on import.
- **Identify and fix records missing HubSpot-required fields.** Contacts require at least one of First Name, Last Name, or Email. Companies require Name or Domain. Deals require Deal Name, Pipeline, and Deal Stage.*If skipped: Rows missing required fields are rejected silently into an error file and never reach the destination.*
- **Re-encode all source text exports as UTF-8.** Non-UTF-8 characters (smart quotes, em dashes, Latin-1 accents) cause row rejection or character corruption in the Import Tool parser.
- **Provision the production portal in the chosen data center.** Confirm hosting region (US na1 or EU Frankfurt) is correct before any configuration. Region change post-provisioning requires a separate residency migration.*If skipped: Wrong region locks the portal to a residency that may violate procurement or contract clauses signed with EU customers.*
- **Create a standard (CRM-only) sandbox from production settings.** Use Settings → Account Setup → Sandboxes → Create Sandbox. Name it 'Migration-Staging'. The sandbox clones structure but is empty by default.*If skipped: Testing in production guarantees that data corruption from a bad mapping cannot be reversed cleanly.*
- **Configure account currency, fiscal year, and timezone.** Settings → Account Defaults. These affect how Deal amounts, Close Date, and activity timestamps render and import.*If skipped: Changing currency after deals load forces a portal-wide re-derivation of historical amounts.*
- **Provision all destination users with the correct permission sets.** Use Settings → Users & Teams. Deal/contact owners cannot be assigned to users that do not yet exist.*If skipped: Imported records with unknown owners default to the importer, mis-attributing pipeline ownership.*
- **Create all custom properties before any record import.** For each source custom field, create the matching HubSpot property under Settings → Properties with the correct field type (Single-line text, Dropdown select, Multi-checkbox, Date picker, Number, etc.).*If skipped: Properties that do not exist at import time cause those columns to be silently dropped — data loss with no error.*
- **Create custom objects and define their associations.** Settings → Data Management → Data Model → Create object. Define singular and plural names, primary display property, and required properties at creation. Required properties can be loosened later but type cannot change.*If skipped: Wrong primary display property forces a costly rebuild because that field is immutable after creation.*
- **Create association labels for custom relationships.** Define labels like Decision Maker, Influencer, Billing Contact for Contact↔Deal associations under Settings → Data Model. Each label can carry per-side cardinality limits.
- **Mark migration-source identifier properties as Unique.** Create a custom 'External ID' property per object with the Unique setting enabled at creation. Unique cannot be retroactively set on an existing property.*If skipped: Without a unique External ID, re-running an import creates duplicates instead of upserting.*
- **Build all sales pipelines and deal stages in HubSpot.** Settings → Objects → Deals → Pipelines. Create the destination pipeline structure with stage internal values that match your mapping table.*If skipped: Importing deals into a non-existent stage rejects the row.*
- **Build ticket pipelines and Lifecycle Stage / Lead Status picklist values.** Configure Service Hub ticket pipelines and align Contact Lifecycle Stage and Lead Status picklist values to source-system equivalents.
- **Configure HubSpot duplicate-detection settings.** Review default contact/company dedup keys (email, domain) and decide whether bulk-merge tooling will run before or after the migration.
- **Pause all workflows, sequences, and integrations on the destination portal.** Turn off active workflows, marketing automation, sequence enrollment, and third-party integrations until cutover. Mass-imported records trigger enrollment unless paused.*If skipped: Sequences fire welcome emails to migrated contacts who were never opted in, generating spam complaints and deliverability damage.*
- **Disable Restore CRM Properties auto-rollback only after a backup snapshot is captured.** HubSpot's Restore CRM Properties auto-captures the last 20 versions (45 for contacts) for 14 days. Confirm it is on before import in case rollback is needed.
- **Communicate the source-system freeze window to all users.** Send the date and time when source writes will stop and HubSpot becomes the system of record. Include a designated channel for last-minute questions.*If skipped: Late writes in the source create a delta that is not captured in the final export.*
- **Schedule role-specific HubSpot training before cutover.** Run separate sessions for sales reps (deals, sequences), marketing (lists, workflows), and service (tickets, conversations).
- **Designate first-responder owners for the first 48 hours post-cutover.** Name 2–3 people who triage HubSpot user issues immediately after go-live. Publish their contact info before cutover day.

2\. Source Export 12 tasks

- **Export contacts as CSV with all standard and custom fields.** Include source record ID, email (lowercased), first/last name, phone, lifecycle stage equivalent, owner email, created date, and every custom field.*If skipped: Omitting source record ID makes idempotent re-runs impossible — re-loads create duplicates.*
- **Export companies as CSV with all standard and custom fields.** Include source ID, normalized domain, legal name, address, industry, owner email, and parent/child company linkage if used.
- **Export deals with full property set and pipeline metadata.** Include source ID, deal name, amount, currency, close date, pipeline name, stage name, owner email, and associated contact/company IDs.
- **Export tickets, products, and line items as separate files.** Each object type has its own schema and required fields. Do not merge them into one sheet.
- **Export custom-object records, one file per object type.** Include the source ID, the field that will become the unique External ID in HubSpot, and all associations to standard objects.
- **Export contact↔company, contact↔deal, and company↔deal association tables.** Export junction tables as two-column CSVs (source contact ID, source deal ID) per association type. Capture association labels where the source supports them.*If skipped: Missing association exports break the parent/child relationships that HubSpot uses for reporting and roll-ups.*
- **Export activities — notes, calls, emails, meetings, tasks — as separate files.** Each activity type has different required fields in HubSpot. Capture activity timestamp, owner email, body/notes, and the source ID of every associated record.
- **Export file attachments — both metadata index and binaries.** Export the file-to-record join table (which file is attached to which contact/deal/ticket) and the binary files themselves into a folder structure mirroring the index.*If skipped: Losing the join table means files can be re-uploaded but not re-linked to their owning records.*
- **Export the source user list with roles and reporting structure.** Capture each user's email (the matching key in HubSpot), role, and team. This is the owner-mapping source.
- **Export pipeline, stage, and picklist definitions.** Document every source pipeline name, stage name, stage probability, and every picklist option with both display label and internal value.
- **Capture screenshots and configs of source automations, reports, and dashboards.** Workflows, reports, and dashboards do not transfer. Document them now so they can be rebuilt in HubSpot post-cutover.
- **Record the exact timestamp of every export.** Note the wall-clock time each export file was generated. This is the delta-window anchor for the final cutover export.*If skipped: Without per-file timestamps the delta export at cutover may miss or double-count records changed during the export window.*

3\. Transform & Map 24 tasks

- **Build a master mapping spreadsheet, one tab per object.** Columns: source field, source type, source sample value, HubSpot property internal name, HubSpot field type, transformation rule, required flag, nullability.*If skipped: Without a single source of truth, transform code and import templates drift and silently disagree.*
- **Resolve every picklist value mismatch against HubSpot internal values.** HubSpot enumeration properties match on internal value (for example: 'appointmentscheduled'), not the display label ('Appointment Scheduled'). Map source values to internal values.*If skipped: Mapping to display labels causes silent value drops because the import engine does not recognize the string.*
- **Decide the upsert key per object.** Contacts: Email. Companies: Company Domain Name. All others: a custom Unique External ID property created in Phase 1b.
- **Decide handling for orphan source fields.** For source fields with no HubSpot equivalent, choose: drop, concatenate into a Notes property, or create a new custom property. Document the call per field.
- **Document character-length truncation rules per text field.** HubSpot single-line and multi-line text fields cap at 65,536 characters. Define truncation or split rules for long source values.
- **Convert all dates and timestamps to ISO-8601 with explicit timezone.** HubSpot accepts ISO-8601 (for example: 2026-05-27T14:30:00Z) on import. Convert epoch timestamps, DD/MM/YYYY, and locale-specific formats.*If skipped: Ambiguous date formats (03/04/2026) are interpreted under the portal's date locale and can land months off.*
- **Normalize currency values and split multi-currency exports.** Set decimal precision, strip thousands separators, and tag rows with currency code. Multi-currency HubSpot portals require the currency column on every monetary field.
- **Lowercase and trim all email addresses.** HubSpot stores contact email lowercased and matches case-insensitively. Pre-normalize to control merge behavior.
- **Normalize phone numbers to E.164.** Strip parentheses, spaces, and dashes. Add country code prefix. HubSpot phone validation rejects malformed values when rules are active.
- **Strip or escape commas, quotes, and newlines in CSV cells.** Wrap any value containing a comma, quote, or newline in double quotes and escape inner quotes. The Import Tool parser fails rows with unescaped delimiters.*If skipped: A single un-escaped comma in a Notes field shifts every subsequent column for that row, scrambling the entire record.*
- **Convert rich-text and HTML body fields to HubSpot-compatible markup.** Strip non-allowed HTML tags; convert remaining markup to inline HTML or plain text per field type. Multi-line text fields preserve line breaks in records but not in marketing emails.
- **Re-encode every file as UTF-8 with no BOM.** Save CSVs as UTF-8 without byte-order-mark. Excel's default ANSI export corrupts non-ASCII characters at import.
- **Split large files to stay under HubSpot import limits.** Paid plans cap files at 512 MB and 1,048,576 rows per file. Free tier caps at 20 MB. Split by row count, not random chunking.*If skipped: A file that exceeds the row cap is rejected outright with no partial-load option.*
- **Decide the historical-timestamp strategy.** HubSpot does not let you override Create Date for many record types via standard import. Accept today's stamp and store the original date in a custom 'Original Create Date' property.*If skipped: Accepting the default re-stamps every record to cutover day, breaking historical pipeline-velocity and tenure reporting.*
- **Decide the record-ownership strategy.** Map source owner email → HubSpot owner. For unmapped owners, route to a single 'Migration' user instead of leaving blank, which defaults ownership to the importer.
- **Decide the activity-timestamp strategy.** For notes, calls, and emails, the Activity Date property accepts the original timestamp on import. Map source created\_at → Activity Date so the timeline reflects history.
- **Decide the attachment strategy.** Choose between (a) re-upload binaries to HubSpot Files and link via Notes, or (b) preserve as external storage URLs in a custom Link property. Each has trade-offs on access and search.
- **Map source pipeline stages to HubSpot deal-stage internal values.** Build the source-stage → HubSpot-stage-internal-value table. Set the destination probability (0.0–1.0) per stage. Validate that every source stage has a destination.*If skipped: Unmapped stages cause deal rows to reject and break weighted-pipeline reporting on day one.*
- **Decide deal Close Date handling for won, lost, and open deals.** Closed deals keep the source close date. Open deals need a forward-dated Close Date — pick a default (90 days out) or carry the source-system estimate. Lost deals retain their original close.*If skipped: Open deals imported with past Close Dates show as overdue and pollute forecast reports.*
- **Re-derive lead scores from raw signals, do not migrate scores.** HubSpot's scoring engine (HubSpot Score, predictive lead scoring) computes scores from native engagement signals. Carry source scores into a custom 'Legacy Score' property and let HubSpot re-derive its own.*If skipped: Migrated numeric scores from another system have no meaning in HubSpot's model and mislead reps.*
- **Map source lifecycle states to HubSpot Lifecycle Stage internal values.** Lifecycle Stage internal values are: subscriber, lead, marketingqualifiedlead, salesqualifiedlead, opportunity, customer, evangelist, other. Match against internal values not labels.*If skipped: Bulk imports often default everyone to 'subscriber' regardless of true state, silently downgrading SQLs and customers.*
- **Map source lead-status values to HubSpot Lead Status picklist internals.** HS\_Lead\_Status is a separate property from Lifecycle Stage. Document each source status's destination internal value and create new picklist options as needed.
- **Decide contact-merge strategy for known cross-source duplicates.** If two source systems have the same person, decide: merge before import using source-system tooling, or import both and run HubSpot's duplicate-management tool post-load. The latter is destructive on workflow enrollment.*If skipped: Post-import merges in HubSpot can break workflow enrollment history and attribution on the surviving record.*
- **Plan sequence and workflow rebuild, not migration.** Sequences, workflows, and saved views do not import. Build a rebuild backlog from the Phase 2 screenshots and prioritize the top 20% that handle 80% of volume.

4\. Sandbox Test Migration 11 tasks

- **Load a 1–5% representative sample of each object into the sandbox.** Use stratified sampling: include records from each pipeline, lifecycle stage, owner, and time period. Random 1% can miss edge cases.*If skipped: A non-representative sample passes validation but production load hits unknown edge cases.*
- **Test the Import Tool wizard path via Settings → Data Management → Data Integration.** Walk through Advanced Imports for multi-object files. Validate column-to-property mapping, association mapping, and the 'Prevent property overwrite' option.
- **Validate field-by-field on 10 random sandbox records per object.** Open each record in the HubSpot UI and compare every property value against the source. Spot-check date fields, picklists, and multi-checkbox values.
- **Test edge cases: long strings, special characters, NULL, blank vs. missing.** Verify a 60,000-character note imports, that em-dashes and emojis survive, and that blank-vs-missing distinction matches expectations.
- **Verify parent-child and many-to-many associations preserved.** Spot-check 20 contact-to-company and contact-to-deal associations. Confirm association labels (Decision Maker, etc.) landed on the right side.*If skipped: Reversed association direction is silent and only surfaces when a report shows zero linked records.*
- **Stress-test against the 50,000 associations-per-record ceiling.** If any source object has more than 50,000 associations of a single type, design a chunking strategy or shard the data. This is a hard platform ceiling.*If skipped: Hitting the 50k ceiling mid-load rejects associations silently and reports show under-counted relationships.*
- **Verify activity timestamps and ownership.** Open 10 imported notes/calls/emails and confirm Activity Date and Activity assigned to land correctly. Meetings require an owner column mapped to Activity assigned to.
- **Run a full-volume test or the largest sample the sandbox allows.** Time the load. Extrapolate to production volume and confirm the cutover window is realistic.
- **Test the error-file workflow.** Download a deliberately-bad row's error file from the Import Tool. Confirm the team can read it, fix the source, and re-import only failed rows.
- **Get a sales-ops or RevOps domain expert to spot-check sandbox data.** Have a power user open 25 deals across pipelines and confirm amounts, stages, close dates, and associations look right.
- **Sign off the sandbox test results in writing before Phase 5.** Get the migration sponsor's documented approval. Capture the sandbox import IDs and row counts as evidence.*If skipped: Skipping written sign-off lets ambiguity about 'good enough' bleed into the production go/no-go call.*

5\. Production Cutover 12 tasks

- **Confirm source-system freeze and verify zero new writes in the last hour.** Check source audit logs. If writes are still happening, halt and escalate to the freeze owner.*If skipped: Writes during cutover create a delta that the final export misses, leaving records behind in the source.*
- **Take a final full export of source data as the delta against Phase 2 baseline.** Export every object again. Diff against Phase 2 to find created/updated/deleted records during the prep window. Apply only the delta to the prepared transform.
- **Disable destination workflows, sequences, and integrations one final time.** Re-verify the pause set from Phase 1b is still in place. New workflows may have been created since.*If skipped: A workflow created mid-project that no one paused fires on every imported contact and triggers notification spam.*
- **Load users and Owners first.** Use the Import Tool with the Owners object. All owner-mapped records depend on these existing.
- **Load parent objects: Companies, then Contacts.** Companies before contacts so the contact-to-company association can resolve on contact load. Use upsert on Company Domain Name and Email respectively.
- **Load Deals and Tickets.** Both depend on Contacts and Companies existing. Use the External ID upsert key per object. For deals, confirm pipeline and stage internal values resolve.
- **Load Custom Objects and their associations to standard objects.** Custom objects with associations must be loaded after their associated standard objects.
- **Load activities last: notes, calls, emails, meetings, tasks.** Activities require existing records to associate with. Include the Activity assigned to and Activity Date properties so timestamps and ownership land correctly.
- **Load file attachments and link them to records via Notes.** Upload each binary into HubSpot Files, then attach via a note on the associated record.
- **Capture import job IDs, row counts, and error files for every step.** Save the import ID, requested row count, succeeded count, and downloadable error file URL per load. This is the audit trail for Phase 6.*If skipped: Without per-step row counts, reconciliation in Phase 6 becomes guesswork.*
- **If any load step fails partway, stop and diagnose before continuing.** Do not push forward with partial data hoping to fix it later. Fix the transform, run an idempotent re-load using the upsert key, then continue.*If skipped: Pushing through partial loads creates orphan records and double-counted rows that take weeks to untangle.*
- **Re-enable workflows, sequences, and integrations only after all loads complete.** Turn integrations back on one at a time and monitor for unexpected enrollment or notification traffic.

6\. Validate 16 tasks

- **Compare total record count per object against the Phase 1a baseline.** Pull HubSpot counts from each object's index view. Investigate any delta greater than the known dedup expectation.*If skipped: Silent row drops show up as a count delta with no error file — the only way to catch them is the reconciliation step.*
- **Compare total pipeline value: source vs. HubSpot.** Sum Deal Amount across all in-scope deals in both systems, converted to a single currency. Variance over 1% means a transform error.*If skipped: Currency normalization bugs only surface in totals — per-record spot checks miss them.*
- **Compare active deal count by stage.** For each pipeline, count deals per stage in both systems. Mismatches reveal stage-mapping errors.
- **Cross-check 25–50 randomly-selected records field-by-field.** Stratified random sample: at least 25 contacts, 25 companies, 25 deals, 25 activities. Open each in HubSpot UI and compare every property against the source.
- **Verify all custom field values on the sample.** Custom property silent drops happen when the property was not pre-created or when the internal name does not match. Check every custom property's values.*If skipped: Standard fields look fine in spot checks while custom properties show as blank, and the issue surfaces weeks later.*
- **Verify contact-to-company associations on a 50-record sample.** For each sampled contact, confirm it is associated with the right company and that the association label (if any) is correct.
- **Verify contact-to-deal and company-to-deal associations.** Confirm decision-maker, influencer, and other labels landed on the correct side. Verify deal-to-contact count matches source.
- **Verify activity-to-record associations.** Open 20 imported notes/calls/emails and confirm they are attached to the right contact, deal, or ticket — not to an orphan record.*If skipped: Activities attached to the wrong record corrupt the timeline view that reps rely on for context.*
- **Verify file attachments are accessible and correctly linked.** Open 20 file attachments via their associated record and confirm the file downloads and the linkage is to the correct parent.
- **Verify the historical-timestamp strategy held.** If using the 'Original Create Date' custom property approach, confirm 10 sampled records show the original date there and the current date on Create Date.
- **Pull a centralized audit log from Settings → Account & Billing → Account Activity.** Enterprise-tier portals expose the audit log. Export the cutover-window log as evidence for SOC 2 / internal audit.
- **Confirm data residency placement.** Check Settings → Account Defaults for data-center region. Capture a screenshot for the compliance record if EU residency is required.*If skipped: EU customer contracts often demand documented residency evidence; missing it surfaces during a customer audit later.*
- **Confirm subprocessor list matches the signed DPA.** Verify the HubSpot subprocessor list at legal.hubspot.com matches the DPA on file. Flag any new subprocessor for legal review.
- **Recruit 3–5 power users to validate their own day-to-day workflows.** Each user spends 60 minutes opening their own records and walking through a typical day. They know what 'correct' looks like better than anyone.*If skipped: QA by the migration team alone misses the subtle business-context mistakes that real users spot immediately.*
- **Document every data issue surfaced by UAT in a triage log.** Categorize each issue: blocker (fix before go-live), high (fix in first week), low (backlog). Get the sponsor's call on each blocker.
- **Get written go/no-go sign-off from the migration sponsor.** Sponsor signs off in writing referencing the reconciliation report, the UAT log, and the compliance evidence. File the signed document.

7\. Post-Migration Cleanup 12 tasks

- **Send go-live communication to all end users.** Include the HubSpot login URL, the SSO instructions, the where-to-get-help contact, and the freeze date on the source.
- **Run role-specific HubSpot training sessions in the first week.** Separate sales-rep, marketing, and service sessions covering the Lifecycle Stage and Lead Status conventions chosen in Phase 3.
- **Set the source system to read-only and announce the date.** Switch source-system permissions to read-only on the announced date so accidental writes do not happen during the dual-state window.*If skipped: Leaving the source writable invites confusion about which system is the truth.*
- **Rebuild reports and dashboards in HubSpot.** Use the screenshots and configs captured in Phase 2 as the source. Prioritize the top 10 dashboards used by leadership.
- **Rebuild workflows, sequences, and saved views.** Recreate the prioritized 20% of workflows from Phase 3d. Defer the long tail to a 30-day backlog.
- **Re-establish integrations to other systems.** Reconnect calendar sync, email sync, BI tools, and any system-of-record integrations. Test each before unpausing.
- **Configure the HubSpot data-retention policy for inactive contacts.** Settings → Data Management → Privacy & Consent. Decide whether to enable auto-deletion of contacts inactive over a set window (default 365 days).*If skipped: Auto-deletion turned on too aggressively after a migration removes recently-loaded but as-yet-unengaged records.*
- **Run a HubSpot duplicate-management pass on contacts and companies.** Settings → Data Quality Command Center or the native duplicate-management tool. Resolve any cross-source duplicates that survived the import.
- **Schedule a 30-day post-migration retrospective.** Capture what went well, what broke, what was missed, and what the team would do differently. File the document in the project archive.
- **Document the source-system decommission date.** Typically 90 days after cutover, aligned with the data-retention window. Get the call documented in writing by the data owner.
- **Archive all source-system exports and HubSpot import error files to cold storage.** Move CSVs, binaries, and import error files to long-term object storage with a retention tag aligned to legal hold requirements.*If skipped: Deleting source exports too early leaves no recovery path if a data issue surfaces in month four.*
- **Close out the project formally.** Final status report, lessons-learned document, sponsor sign-off on closure. Release the migration team.

Questions, answered

## Migrating to HubSpot: questions

How long does migration to HubSpot take?

A small-business migration with under 5,000 contacts and standard objects runs one to two business days end-to-end. A mid-market project with deal history, Custom Objects and historical activities runs two to four weeks of elapsed time, including preparation, dry runs in a sandbox, validation, training and a 48-hour hyper-care window.

Can I migrate from Salesforce to HubSpot?

Yes — Salesforce is the most common Sales Hub migration source. Standard objects map cleanly, but Apex code, Flows, Process Builder and Reports do not transfer and need to be rebuilt as HubSpot workflows and reports. Plan for picklist internal-value conversion and Salesforce User ID to HubSpot owner-email mapping.

Can I migrate from Pipedrive to HubSpot?

Yes, and Pipedrive-to-HubSpot is usually the cleanest migration shape because the object models align almost one-to-one — People, Organisations, Deals, Activities and Notes correspond to Contacts, Companies, Deals, Activities and Notes in HubSpot. Watch picklist value casing and rebuild Pipedrive workflows as HubSpot workflows from scratch.

Does HubSpot preserve original timestamps on import?

Partially. Activity Date on calls, emails, meetings, notes and tasks can be backdated and shows up correctly on the contact timeline. But system properties like createdate, hs\_createdate and hs\_lastmodifieddate cannot be overridden — they are stamped to import day. Use custom Legacy Created Date properties to preserve the original audit trail.

What's the difference between using the UI import and programmatic loads for HubSpot?

The UI Import Tool handles up to 1,048,576 rows per file on paid tiers and is best for one-shot loads under 100,000 records with a visual mapping step. Programmatic CRM imports and per-object batch operations handle larger volumes, Custom Objects, and repeatable loads but require code and respect tighter batch caps.

Can I migrate Custom Objects to HubSpot?

Yes, but Custom Objects require an Enterprise subscription on most products. You must define the Custom Object schema, its unique-ID property and its associations to standard objects before importing any records of that type. Custom Object records are loaded via Advanced Import or programmatically.

What happens to deal history and pipeline stages during migration?

Recreate every pipeline and every deal-stage internal value in HubSpot before importing deals — rows targeting non-existent stages are rejected. Deal stage history is not auto-preserved; if you need it for reporting, export stage transition timestamps from the source and store them in custom datetime properties such as Stage Entered Date.

Is there an undo or rollback for HubSpot imports?

HubSpot offers Restore CRM Properties and Records, which captures the last 20 property versions per record (45 for contacts) and lets super admins undo changes from the last 14 days via Settings, Data Management. It is not a bulk-rollback button — stamp every imported row with an Import Batch ID instead.

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

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

[See the service →](https://flitstack.ai/services/hubspot-implementation)

### [All crm migrations](https://flitstack.ai/migrations/crm)

[Every destination we migrate pipelines, contacts, and deals into.](https://flitstack.ai/migrations/crm)

[Back to CRM →](https://flitstack.ai/migrations/crm)

## Sources

1. [HubSpot — Wikipedia](https://en.wikipedia.org/wiki/HubSpot)
2. [Format import files — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
3. [Create and edit custom objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/object-settings/create-custom-objects)
4. [Import objects programmatically — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/import-objects)
5. [Understand property field types in HubSpot](https://knowledge.hubspot.com/properties/property-field-types-in-hubspot)
6. [Associate records on CRM objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/records/associate-records)
7. [HubSpot Ideas — Increase Association Limit](https://community.hubspot.com/t5/HubSpot-Ideas/Increase-Association-Limit/idi-p/943077)
8. [Provision HubSpot users through Okta](https://knowledge.hubspot.com/user-management/provision-hubspot-users-with-scim-through-okta)
9. [HubSpot Community — Batch operation per-call limits](https://community.hubspot.com/t5/Help/Batch-Limit-for-Batch-Operations/m-p/401309)
10. [Integration throughput and limits — HubSpot Knowledge Base](https://knowledge.hubspot.com/integrations/integration-throughput-and-limits)
11. [HubSpot Community — Contact batch upsert unique property](https://community.hubspot.com/t5/Help/Contact-batch-upsert-unique-property/m-p/1008345)
12. [Supported file types and sizes — HubSpot Knowledge Base](https://knowledge.hubspot.com/files/supported-file-types)
13. [HubSpot Security Program](https://legal.hubspot.com/security)
14. [HubSpot Cloud Infrastructure and Data Hosting FAQ](https://knowledge.hubspot.com/account-security/hubspot-cloud-infrastructure-and-data-hosting-frequently-asked-questions)
15. [HubSpot Community — Activity information lost after 30 days on free plan](https://community.hubspot.com/t5/CRM/Activity-information-lost-after-30-days-on-free-plan/td-p/1238513)
16. [HubSpot Community — Importing Company Data with activity timestamps](https://community.hubspot.com/t5/CRM/Importing-Company-Data-with-activity-timestamps/m-p/9511)
17. [HubSpot Community — Reverse a recent import / Restore CRM Records](https://community.hubspot.com/t5/CRM/Reverse-a-recent-import-or-restore-all-content-to-the-most/m-p/366863)
18. [View the account history in HubSpot — HubSpot Knowledge Base](https://knowledge.hubspot.com/account-management/view-the-account-history-in-hubspot)
19. [We ditched HubSpot at $2M revenue and saved $12K/year — r/CRMSoftware](https://www.reddit.com/r/CRMSoftware/comments/1seflc1/we_ditched_hubspot_at_2m_revenue_and_saved_12kyear/)

Get a quote

## Moving to HubSpot?

Tell us where your data lives today and roughly how much there is. We scope the migration and the HubSpot setup with you, then send a quote.

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