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

# Bitrix24 to HubSpot migration

Moving from Bitrix24 to HubSpot CRM consolidates your CRM data into a platform built for marketing-led growth. FlitStack AI maps every Bitrix24 lead, contact, company, and deal to HubSpot's object model, preserves original timestamps and owner assignments, and handles custom field translation across both platforms. Your team keeps working in Bitrix24 during the 24–48 hour delta window so nothing slips through during cutover.

Short answer

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

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

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

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

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

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

Contact Company Deal Engagement Custom Property

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

## What moves from Bitrix24 to HubSpot?

Bitrix24 stores CRM data across several interconnected objects — leads, contacts, companies, and deals — with custom fields attached to each.

Read the full summary

HubSpot's CRM object model is structurally similar but uses lifecycle\_stage on contacts, deal pipelines with stage probability, and a marketing contact billing flag that Bitrix24 doesn't replicate. We map Bitrix24 leads and contacts to HubSpot contacts (split by lifecycle stage where applicable), Bitrix24 companies to HubSpot companies, and Bitrix24 deals to HubSpot deals with pipeline and stage mapping. Activity history — calls, emails, meetings, and notes — migrates as engagements linked to the parent contact or company record. Bitrix24's REST API enforces rate limits of 2 requests per second on standard plans and 5 per second on Enterprise, which we navigate using batch endpoints and staggered polling. Custom fields in Bitrix24 translate to HubSpot custom properties using type-aware mapping; any workflow logic or automation rules must be rebuilt in HubSpot's automation tools after migration completes.

direct

### Lead → Contact

Bitrix24 leads map directly to HubSpot contacts.

How it maps

In HubSpot, leads that have progressed to a sales conversation route to the contact record directly. Original lead creation date is preserved as Original\_Create\_Date\_\_c (custom field). Source system ID stored for delta-run deduplication.

direct

### Contact → Contact

Bitrix24 contacts map 1:1 to HubSpot contacts.

How it maps

Email address serves as the primary identifier for matching and resolving the HubSpot owner. HubSpot's lifecycle\_stage property receives Bitrix24's contact status value; if no status exists, we default to 'subscriber' or your specified default. Custom fields on contacts translate to HubSpot custom properties using type-aware mapping. After migration, verify lifecycle\_stage assignments align with your marketing and sales stages.

direct

### Company → Company

Bitrix24 company records map to HubSpot company objects.

How it maps

The company domain is used for HubSpot's domain matching to associate incoming contacts with the parent company. Bitrix24 parent‑child hierarchies map to HubSpot's parent company field; the parent company must be migrated first to avoid orphaned records. Standard fields such as industry, employees, revenue, phone, and address migrate directly, and Bitrix24 custom fields on companies translate to HubSpot custom properties with type‑aware mapping.

direct

### Deal → Deal

Bitrix24 deals map to HubSpot deals.

How it maps

The Bitrix24 pipeline and stage names map to corresponding HubSpot deal pipeline and stage values. Deal amount, close date, and owner are migrated as-is. If Bitrix24 uses multiple pipelines, each becomes a separate HubSpot deal pipeline.

direct

### Activity (Call) → Engagement (Call)

Bitrix24 call logs migrate as HubSpot call engagements.

How it maps

Original call duration, timestamp, owner, direction (inbound/outbound), and associated contact or deal links are preserved. Call recordings stored in Bitrix24 are downloaded and re‑uploaded to HubSpot Files, attached to the engagement record. The call subject or title maps to HubSpot's call title field, and any Bitrix24 custom fields on call logs translate to HubSpot custom properties with type‑aware mapping.

direct

### Activity (Email) → Engagement (Email)

Bitrix24 email activities map to HubSpot email engagements.

How it maps

The email body (HTML or plain text), subject, sender, recipients, direction (inbound/outbound), and timestamp are preserved. Attachments are downloaded and re‑uploaded to HubSpot Files, linked to the engagement. Any Bitrix24 custom fields on email activities translate to HubSpot custom properties with type‑aware mapping, and the engagement associates to the relevant contact, company, or deal via HubSpot's linking model.

******What moves 12 objects

Bitrix24 HubSpot

- Lead Contact 1:1
- Contact Contact 1:1
- Company Company 1:1
- Deal Deal 1:1
- Activity Engagement 1:1
- Activity Engagement 1:1

\+ 6 more in the mapping below

## How Bitrix24 and HubSpot differ

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

| Dimension               | Bitrix24                                                                                                                         | HubSpot                                                                                                                       |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Pricing model           | Bitrix24 uses flat-rate per organization pricing — unlimited users on free tier, paid plans scale by feature depth not headcount | HubSpot charges per-seat and per-hub (Marketing, Sales, Service) with contact-based billing for marketing features            |
| Contact lifecycle model | Bitrix24 has separate Lead and Contact objects with manual status progression                                                    | HubSpot uses lifecycle\_stage property on contacts with automatic progression triggers (subscriber, lead, MQL, SQL, customer) |
| Deal pipelines          | Bitrix24 supports multiple CRM pipelines with customizable stages per pipeline                                                   | HubSpot uses deal pipelines with stage probability and forecast category; multiple pipelines available on Professional+       |
| API rate limits         | Bitrix24 REST API caps at 2 req/sec (standard) or 5 req/sec (Enterprise) with daily accumulated limits                           | HubSpot API allows 100 calls/sec on most tiers with daily rate limits based on tier (40,000–100,000/day)                      |
| Automation scope        | Bitrix24 includes workflow automation rules, business process templates, and RPA within the platform                             | HubSpot uses automation within each hub (workflows, sequences, multi-step actions) — rebuild required post-migration          |
| File storage            | Bitrix24 includes 5GB–3TB storage depending on plan with document management built in                                            | HubSpot Files storage starts at 10GB on Starter; attachments and documents migrate to HubSpot Files                           |

## Bitrix24 to HubSpot field mapping

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

******Field mapping 5 shown

Bitrix24 HubSpot

1. `NAME` Contact `firstname` Contact
2. `SECOND_NAME` Contact `middlename` Contact
3. `LAST_NAME` Contact `lastname` Contact
4. `EMAIL` Contact `email` Contact
5. `PHONE` Contact `phone` Contact

| Bitrix24 field            | HubSpot field                        | Mapping                 | Note                                                                                                                                                     |
| ------------------------- | ------------------------------------ | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Contact.NAME`            | `Contact.firstname`                  | direct                  |                                                                                                                                                          |
| `Contact.SECOND_NAME`     | `Contact.middlename`                 | direct                  |                                                                                                                                                          |
| `Contact.LAST_NAME`       | `Contact.lastname`                   | direct                  |                                                                                                                                                          |
| `Contact.EMAIL`           | `Contact.email`                      | direct                  |                                                                                                                                                          |
| `Contact.PHONE`           | `Contact.phone`                      | direct                  |                                                                                                                                                          |
| `Contact.MOBILE`          | `Contact.mobilephone`                | direct                  |                                                                                                                                                          |
| `Contact.POST`            | `Contact.jobtitle`                   | direct                  |                                                                                                                                                          |
| `Contact.ADDRESS`         | `Contact.address`                    | direct                  |                                                                                                                                                          |
| `Contact.CITY`            | `Contact.city`                       | direct                  |                                                                                                                                                          |
| `Contact.REGION`          | `Contact.state`                      | direct                  |                                                                                                                                                          |
| `Contact.POSTAL_CODE`     | `Contact.zip`                        | direct                  |                                                                                                                                                          |
| `Contact.COUNTRY`         | `Contact.country`                    | direct                  |                                                                                                                                                          |
| `Contact.SOURCE_ID`       | `Contact.hubspot_owner_id`           | transformed             | Owner resolved by email match to HubSpot user; unmatched owners flagged pre-migration.                                                                   |
| `Contact.DATE_CREATE`     | `Contact.original_create_date`       | custom\_field\_required | HubSpot CreatedDate set at migration time; original Bitrix24 create date stored in custom property.                                                      |
| `Contact.DATE_MODIFY`     | `Contact.original_lastmodified_date` | custom\_field\_required | Original modification date preserved in custom datetime property for audit continuity.                                                                   |
| `Contact.UF_*`            | `Contact.* (custom property)`        | custom\_field\_required | Bitrix24 custom fields (UF\_\*) migrate to HubSpot custom properties with type-aware mapping.                                                            |
| `Lead.TITLE`              | `Contact.subject`                    | direct                  |                                                                                                                                                          |
| `Lead.STATUS`             | `Contact.lifecyclestage`             | value\_mapping          | Bitrix24 lead status values map to HubSpot lifecycle stages. Map 'NEW' to 'lead', 'IN\_PROGRESS' to 'marketingqualifiedlead', 'CONVERTED' to 'customer'. |
| `Lead.SOURCE_DESCRIPTION` | `Contact.hs_analytics_source`        | direct                  |                                                                                                                                                          |
| `Company.TITLE`           | `Company.name`                       | direct                  |                                                                                                                                                          |
| `Company.WEB`             | `Company.domain`                     | direct                  |                                                                                                                                                          |
| `Company.INDUSTRY`        | `Company.industry`                   | value\_mapping          | Industry pick-list values mapped value-by-value. Unmapped values default to 'OTHER'.                                                                     |
| `Company.EMPLOYEES`       | `Company.numberofemployees`          | direct                  |                                                                                                                                                          |
| `Company.REVENUE`         | `Company.annualrevenue`              | direct                  |                                                                                                                                                          |
| `Company.PHONE`           | `Company.phone`                      | direct                  |                                                                                                                                                          |
| `Company.ADDRESS`         | `Company.address`                    | direct                  |                                                                                                                                                          |
| `Company.PARENT_ COMPANY` | `Company.parent_id`                  | transformed             | Bitrix24 parent-company link maps to HubSpot parent company field. Parent company must migrate first; circular references flagged.                       |
| `Company.UF_*`            | `Company.* (custom property)`        | custom\_field\_required | Bitrix24 company custom fields migrate to HubSpot company custom properties with type mapping.                                                           |
| `Deal.TITLE`              | `Deal.dealname`                      | direct                  |                                                                                                                                                          |
| `Deal.AMOUNT`             | `Deal.amount`                        | direct                  |                                                                                                                                                          |

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

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

high

### Bitrix24 API rate limits constrain batch extraction speed

Bitrix24 enforces 2 requests per second on standard plans and 5 per second on Enterprise accounts.

How we handle it

Each batch endpoint returns up to 50 records, so large datasets require thousands of API calls. We use batch list methods and staggered polling to respect limits without missing records, but datasets over 100,000 CRM objects take proportionally longer to extract. We surface estimated extraction time during the planning phase so cutover scheduling accounts for this constraint.

high

### Bitrix24 lead and contact objects lack a direct lifecycle stage equivalent

HubSpot's lifecycle\_stage property drives marketing automation, lead scoring, and reporting segmentation.

How we handle it

Bitrix24's Lead and Contact objects use a status field (NEW, IN\_PROGRESS, CONVERTED) that doesn't map cleanly to HubSpot's eight-stage model (subscriber, lead, MQL, SQL, opportunity, customer, evangelist, other). We map Bitrix24 statuses to the nearest HubSpot lifecycle stage but the semantic gap means your marketing team should review and adjust HubSpot lifecycle automation triggers post-migration to match your actual buyer journey.

medium

### Multi-pipeline setup in Bitrix24 requires explicit HubSpot pipeline mapping

Bitrix24 supports multiple simultaneous sales pipelines with independent stage sets.

How we handle it

HubSpot's deal pipelines are scoped per portal, and each pipeline can have its own stage probability curve. If your Bitrix24 instance uses more than one pipeline, each must be explicitly mapped to a corresponding HubSpot deal pipeline before migration. Stage probability and forecast category need to be re-applied per HubSpot pipeline. We deliver the pipeline mapping plan during the schema planning step so your HubSpot admin can pre-create pipelines before data lands.

medium

### Bitrix24 workflow rules and business process templates do not migrate

Bitrix24's automation rules (triggers, actions, notifications) and business‑process templates (approval chains, SLA workflows, request flows) are configuration‑bound and have no direct HubSpot equivalent at the data layer.

How we handle it

We export your Bitrix24 workflow definitions as a JSON reference file that preserves conditions, action sets, and field references. Your HubSpot admin can use this file to rebuild equivalent automation in HubSpot Workflows or Operations Hub, mapping each trigger to its nearest workflow trigger and replicating any custom field logic. The rebuild is a manual effort that typically requires 1–3 days, longer for complex interdependent automations.

medium

### HubSpot's marketing contact billing flag has no Bitrix24 equivalent

HubSpot bills based on marketing contact count on certain hub tiers.

How we handle it

Bitrix24 does not have an equivalent marketing contact distinction — all CRM contacts are treated uniformly. We cannot infer which contacts should carry HubSpot's marketing contact flag from Bitrix24 data alone. Your team should define the marketing contact criteria post-migration and apply the flag using a HubSpot list or workflow, or accept HubSpot's automatic classification based on engagement activity.

## How the migration runs

1. ### Assess Bitrix24 API quota and extract schema

   We connect to your Bitrix24 account via REST API using OAuth2 credentials.

   What this step covers

   We first measure your API rate-limit tier (standard or Enterprise) and test batch extraction endpoints. A schema scan enumerates all CRM objects, custom fields, pipeline configurations, and user accounts. This produces a migration plan document that maps each Bitrix24 object and custom field to its HubSpot equivalent before any data movement begins.

2. ### Resolve users and owners by email match

   Bitrix24 user accounts are matched to HubSpot user records by email address.

   What this step covers

   We generate a pre-migration owner resolution report listing matched users, unmatched Bitrix24 users, and HubSpot users with no Bitrix24 counterpart. Your team resolves unmatched owners by inviting them to HubSpot or assigning a fallback owner before the full migration run. No CRM record migrates without a valid HubSpot owner reference.

3. ### Create HubSpot deal pipelines and map stage values

   We review your Bitrix24 pipeline and stage configuration and deliver a pipeline mapping specification for your HubSpot admin.

   What this step covers

   Each Bitrix24 pipeline becomes a HubSpot deal pipeline; each stage maps to a HubSpot stage with probability and forecast category. The HubSpot admin creates pipelines and stages before data lands. We also map Bitrix24 custom fields to HubSpot custom properties, flagging any type conversions needed (date formats, pick-list values, numeric precision).

4. ### Run sample migration with field-level diff

   A representative slice of 100–500 records migrates first — covering contacts, companies, deals, and activity history.

   What this step covers

   We generate a field-level diff comparing source values against destination values so you can verify lifecycle stage mapping, pipeline assignment, owner resolution, and custom property translation. You approve the sample before the full run commits. This step surfaces any mapping corrections before volume migration.

5. ### Execute full migration with delta-pickup window

   The full migration runs against HubSpot's CRM API using batch inserts.

   What this step covers

   A delta-pickup window (24–48 hours after the primary run) captures any records created or modified in Bitrix24 during cutover. We use Bitrix24's API to fetch changes since the initial extraction timestamp. Audit logs capture every operation. One-click rollback is available if reconciliation identifies missing or misaligned records beyond acceptable thresholds.

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

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

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

Example run

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

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

Example

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

**48–72 hours for under 50,000 records** Typical, smaller accounts

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

A quote scales with record count, custom field volume, and data-model divergence between Bitrix24 and HubSpot. Bitrix24 setups with more than 20 custom CRM fields, multiple deal pipelines, or extensive activity history fall in the upper range because each pipeline requires separate stage-value mapping and activity attachments add file-transfer overhead. The API rate-limit constraint on Bitrix24's export side also affects batch sizing and can extend processing time for high-volume datasets. HubSpot tier (Starter through Enterprise) affects import API quotas but not the core migration cost. Every quote is scoped with you; there is no self-serve pricing.

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

## Why teams move from Bitrix24 to HubSpot

- Bitrix24's flat-rate pricing masks tier-gating that catches teams mid-growth — user caps, storage limits, and feature restrictions activate without warning on certain plan tiers. HubSpot's per-seat model is more predictable for teams that know their headcount. Multiple reviews cite unexpected bill shock when crossing Bitrix24 tier thresholds.
- Teams report that Bitrix24's all-in-one approach creates a steep initial learning curve with slower onboarding compared to HubSpot's guided setup. Reviewers on G2 and Capterra frequently mention that sales reps resist opening Bitrix24 daily because the interface feels cluttered when all modules are enabled simultaneously.
- HubSpot's native integration between marketing automation, sales CRM, and service hub eliminates the data-sync friction that Bitrix24 teams experience when connecting separate CRM and marketing tools. For marketing-led teams, HubSpot's built-in email sequences and lead scoring are a direct functional upgrade.
- Bitrix24's workflow and business‑process automation features demand configuration expertise and become a bottleneck when teams need to iterate quickly on process changes. HubSpot's visual workflow builder is more accessible to non‑technical users, offering a larger community of free templates, step‑by‑step guides, and a marketplace of pre‑built automation packs that can be duplicated and adapted without developer involvement. This lowers the barrier for rapid process iteration and reduces reliance on specialized configuration skills.

Questions, answered

## Bitrix24 to HubSpot migration questions

How long does a Bitrix24 to HubSpot CRM migration take?

Most Bitrix24-to-HubSpot migrations complete in 48–72 hours of clock time for under 50,000 CRM records. Large datasets with 500,000+ records or extensive activity history extend to 5–7 days. The API rate-limit constraint on Bitrix24's export side is the primary variable — Enterprise accounts export faster due to higher throughput. Mapping multiple Bitrix24 pipelines to HubSpot deal pipelines adds planning time but not migration duration.

Will my Bitrix24 workflow rules and business process templates migrate to HubSpot?

No. FlitStack AI migrates data and schema only. Bitrix24 workflow rules, automation triggers, approval templates, and business process configurations do not have a migration path to HubSpot — they must be rebuilt in HubSpot's workflow builder or Operations Hub. We export your Bitrix24 workflow definitions as a structured JSON reference file that your HubSpot admin can use to rebuild equivalent automation sequences after the data migration completes.

What happens to Bitrix24 leads and contact status fields in HubSpot?

Bitrix24 lead and contact status values (NEW, IN\_PROGRESS, CONVERTED) map to HubSpot's lifecycle\_stage property on the contact record. 'CONVERTED' maps to 'customer'; 'IN\_PROGRESS' typically maps to 'lead' or 'SQL' depending on your specified stage mapping. Bitrix24 contacts without a status field default to 'subscriber'. Since Bitrix24's status model is simpler than HubSpot's eight-stage lifecycle, your marketing team should review and adjust lifecycle automation triggers post-migration to align with your actual buyer journey.

Can I migrate Bitrix24 custom objects to HubSpot custom objects?

Yes. Bitrix24 custom CRM objects (Enterprise tier) map to HubSpot custom objects, which are available on HubSpot Enterprise and above. Custom-object field types are mapped type-by-type: string fields become single-line text, numeric fields become number properties, date fields become date-picker properties, and list fields become single or multi-select pick-lists. Relationships between custom objects and standard CRM entities are preserved using HubSpot's custom object association model. If your HubSpot portal is on a lower tier, custom objects are surfaced as custom properties on the nearest standard object.

How does the migration handle Bitrix24's API rate limits?

Bitrix24 REST API enforces 2 requests per second on standard plans and 5 per second on Enterprise. We use batch list endpoints that return up to 50 records per call and implement staggered polling to respect limits without data loss. Large datasets require proportionally more time to extract — we estimate extraction duration during the planning phase based on your record volume and plan tier. Enterprise accounts extract significantly faster due to the higher rate-limit ceiling.

Does the migration affect my Bitrix24 account during the cutover?

No. FlitStack AI uses scoped read access on Bitrix24 via the REST API — your team continues working in Bitrix24 throughout the migration. We capture a point-in-time snapshot of your data, then run a delta-pickup window (typically 24–48 hours) to catch any records created or modified during the cutover. The delta window ensures HubSpot reflects Bitrix24's final state at go-live without interrupting active sales and support workflows.

What happens to Bitrix24 activity history (calls, emails, meetings, notes)?

Bitrix24 call logs, emails, meetings, and notes migrate as HubSpot engagements linked to the parent contact, company, or deal record. Original timestamps, owners, and engagement direction are preserved. Call recordings are downloaded and re-uploaded to HubSpot Files attached to the call engagement. Email bodies and note content migrate in full. HubSpot's engagement timeline displays this history on the contact record so your team retains full conversation context after the switch.

## Related migrations

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

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

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

[See the service →](https://flitstack.ai/services/hubspot-implementation) [**Vinsolutions to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/vinsolutions/to/hubspot) [**Follow Up Boss to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/follow-up-boss/to/hubspot) [**Nutshell to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/nutshell/to/hubspot) [**folk to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/folk/to/hubspot) [**HoneyBook to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/honeybook/to/hubspot) [**Act-On to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/act-on/to/hubspot) [**Bitrix24 to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/bitrix24/to/salesforce-sales-cloud) [**Bitrix24 to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/bitrix24/to/dynamics-365-sales) [**Bitrix24 to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/bitrix24/to/odoo-crm)

## Sources: official documentation

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

Get a quote

## Moving from Bitrix24 to HubSpot?

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

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