BSI CRM to HubSpot migration
Moving from BSI CRM to HubSpot consolidates your CRM onto a platform with native inbound marketing tools, a larger integration ecosystem, and a pricing model that scales with team size rather than feature complexity. FlitStack AI maps every BSI contact, company, deal, and custom entity into HubSpot's property system — preserving original create dates and owner assignments so your new HubSpot instance reflects the full customer history from day one.
FlitStack AI migrates contacts, companies, deals, engagements and notes from BSI CRM 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.

What moves from BSI CRM to HubSpot?
BSI CRM and HubSpot take different approaches to contact lifecycle modeling.
Read the full summary
BSI CRM stores contacts with a unified customer profile that includes industry-specific properties and supports on-premise deployments alongside cloud access. HubSpot uses a lifecycle_stage property to track where a contact stands in the buyer journey — from subscriber through customer — with separate association models for linking contacts to companies and deals. When migrating from BSI CRM to HubSpot, FlitStack AI extracts all standard BSI objects (contacts, companies, deals, activities, notes, attachments) via BSI's API, then maps each record into HubSpot's corresponding object using field-level name matching for standard fields and transformation logic for platform-specific types. Custom properties from BSI become HubSpot custom properties, and custom objects map 1:1 to HubSpot custom objects. BSI workflows, automations, and approval sequences do not migrate — FlitStack documents the export of these definitions as a reference for HubSpot automation rebuild. We sequence the migration so parent records (companies) load before child records (contacts) so that foreign-key resolution works correctly in HubSpot's association model. A delta-pickup window captures in-flight changes during cutover so HubSpot reflects BSI's final state at go-live.
Contact / Person → Contact
BSI CRM contact records map directly to HubSpot contacts.
How it maps
We preserve original create timestamps as a custom datetime property since HubSpot sets CreatedDate at import time. Owner resolution uses email matching against HubSpot users. BSI contacts without a primary company association land in HubSpot as contacts with no associated company.
Company / Organization → Company
BSI CRM company records map directly to HubSpot companies.
How it maps
BSI company hierarchies with parent/child relationships map to HubSpot's parent company association field. Multi-company affiliations per contact become HubSpot's primary company association, with secondary associations added through the contact record's company connections. We resolve the parent company first to ensure proper hierarchy construction during migration.
Deal / Opportunity → Deal
BSI CRM deals map to HubSpot deals with pipeline and stage values translated via value-mapping.
How it maps
Each BSI pipeline becomes a HubSpot pipeline; BSI deal stages map to corresponding HubSpot deal stages per pipeline. Deal amounts, close dates, owners, and custom deal properties migrate as-is or become HubSpot custom properties.
Activity (Calls, Emails, Meetings) → Engagement (Calls, Emails, Meetings)
BSI CRM activity records (logged calls, emails, meetings) map to HubSpot engagements.
How it maps
Each activity type becomes the corresponding HubSpot engagement type. Original timestamps, owners, and subject/body content preserve during migration. Associations to contacts and companies re-establish via HubSpot's association API.
Note → Note
BSI CRM notes migrate as HubSpot notes.
How it maps
Rich-text formatting from BSI converts to HubSpot's note format, preserving bold, italic, and list structures where supported. Notes linked to specific records (contacts, companies, deals) re-associate using HubSpot's association model after migration. Large notes that exceed HubSpot's character limits per note may require splitting across multiple note records to maintain complete content.
Attachment / File → File
BSI CRM file attachments re-upload to HubSpot's file storage with original filenames and file types preserved.
How it maps
Files associate to the parent record (contact, company, or deal) using HubSpot's file association API after upload completes. HubSpot's 25MB per-file size limit applies to all migrated files; files exceeding this threshold require chunking into smaller segments or re-hosting guidance for your team to store externally and link via URL.
- ContactContact1:1
- CompanyCompany1:1
- DealDeal1:1
- ActivityEngagementtransformed
- NoteNote1:1
- AttachmentFile1:1
+ 6 more in the mapping below
How BSI CRM 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 | BSI CRM | HubSpot |
|---|---|---|
| Deployment model | BSI CRM supports on-premise and cloud deployments; users in regulated industries (banking, insurance) often run on-premise with local data residency. | HubSpot is cloud-only SaaS with data stored on HubSpot's servers; no on-premise option available. |
| Contact lifecycle model | BSI CRM uses a unified contact profile with configurable lifecycle states; no strict buyer-journey stage enforcement. | HubSpot enforces lifecycle_stage as a required property with standard values (subscriber, lead, MQL, SQL, opportunity, customer, evangelist); drives marketing contact billing. |
| Deal tracking | BSI CRM deals include custom stage definitions per pipeline with configurable probability weighting; supports multi-currency at the deal level. | HubSpot deals have pipeline-specific stage names and probabilities; each pipeline is a separate deal record set with its own stage options. |
| Integration ecosystem | BSI CRM has approximately 3 native integrations listed; API available for custom connections but ecosystem is smaller. | HubSpot App Marketplace lists 2,400+ integrations including Salesforce, Zapier, Outlook, Gmail, and major marketing tools. |
| Offline access | BSI CRM supports offline mode for field service and mobile teams operating without constant connectivity. | HubSpot has restricted offline capabilities; mobile app requires connection for most write operations. |
| Industry focus | BSI CRM is positioned as a market leader for banking, insurance, and retail in the DACH region with pre-built compliance configurations. | HubSpot serves SMB to enterprise across all industries with horizontal CRM functionality; no pre-built banking or insurance compliance templates. |
BSI CRM to HubSpot field mapping
The 30 most-used fields of 44 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
firstnameContactfirstnameContact -
lastnameContactlastnameContact -
emailContactemailContact -
phoneContactphoneContact -
mobilephoneContactmobilephoneContact
| BSI CRM field | HubSpot field | Mapping | Note |
|---|---|---|---|
Contact.firstname | Contact.firstname | direct | |
Contact.lastname | Contact.lastname | direct | |
Contact.email | Contact.email | direct | |
Contact.phone | Contact.phone | direct | |
Contact.mobilephone | Contact.mobilephone | direct | |
Contact.jobtitle | Contact.jobtitle | direct | |
Contact.department | Contact.department | direct | |
Contact.address | Contact.address | direct | |
Contact.city | Contact.city | direct | |
Contact.state | Contact.state | direct | |
Contact.zip | Contact.zip | direct | |
Contact.country | Contact.country | direct | |
Contact.createdate | Contact.original_create_date | custom_field_required | HubSpot sets CreatedDate at import time; original BSI create date preserved as a custom datetime property for reporting continuity. |
Contact.updatedate | Contact.original_lastmodified_date | custom_field_required | HubSpot's LastModifiedDate updates on migration; original BSI update timestamp preserved as a custom field. |
Contact.bsi_contact_id | Contact.source_system_id | custom_field_required | BSI internal ID stored on HubSpot contact for traceability and delta-run de-duplication logic. |
Contact.owner_email | Contact.hubspot_owner_id | transformed | BSI owner email resolves to HubSpot user ID via email matching; unmatched owners flagged before migration. |
Contact.lifecycle_status | Contact.lifecyclestage | value_mapping | BSI lifecycle states map to HubSpot lifecycle_stage values. Non-matching values create as HubSpot custom property. |
Company.name | Company.name | direct | |
Company.domain | Company.domain | direct | |
Company.industry | Company.industry | value_mapping | Industry pick-list values mapped value-by-value; BSI industry codes translate to HubSpot's industry taxonomy where applicable. |
Company.numberofemployees | Company.numberofemployees | direct | |
Company.annualrevenue | Company.annualrevenue | direct | |
Company.phone | Company.phone | direct | |
Company.address | Company.address | direct | |
Company.city | Company.city | direct | |
Company.state | Company.state | direct | |
Company.zip | Company.zip | direct | |
Company.country | Company.country | direct | |
Company.bsi_company_id | Company.source_system_id | custom_field_required | BSI company ID preserved on HubSpot company record for traceability and association mapping. |
Company.parent_company_id | Company.parent_id | transformed | BSI parent/child company hierarchy maps to HubSpot's parent company association; parent company must migrate first to resolve the lookup. |
What to watch for in a BSI CRM to HubSpot migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
BSI lifecycle and contact-type properties need value-by-value mapping to HubSpot lifecycle_stage
BSI CRM stores contact lifecycle states as configurable properties that vary by BSI deployment and industry template.
How we handle it
HubSpot enforces its own lifecycle_stage taxonomy with specific values. Migrations that skip value-mapping create unmapped BSI lifecycle states that either drop or require HubSpot custom property creation. We read the BSI property configuration at the start of each project, enumerate every unique lifecycle value in your instance, and map each to a HubSpot lifecycle_stage or create a custom property for non-matching values. This prevents data loss on contacts that were at a non-standard lifecycle state in BSI.
BSI's on-premise export process may require additional authentication and file-transfer steps
If your BSI CRM instance runs on-premise (common in banking and insurance deployments for data-residency compliance), the export process differs from BSI's cloud API.
How we handle it
On-premise instances may require direct database access, file-system exports, or authentication tokens not needed for cloud tenants. We assess your BSI deployment model during discovery and adjust the export approach accordingly. This adds planning time but does not prevent migration — we work with BSI's API endpoints and export utilities regardless of hosting model.
HubSpot's marketing contact billing model activates when contacts enter lifecycle stages
HubSpot charges based on marketing contact count — contacts at lifecycle stages from 'lead' onward.
How we handle it
Migrating BSI contacts into HubSpot with active lifecycle stages may immediately trigger marketing contact billing for records that were not previously counted. We preserve the BSI lifecycle value and can set migrated contacts to 'subscriber' or a pre-billing stage temporarily, then update lifecycle stages in HubSpot after billing review. Your team controls when contacts enter the paid marketing-contact tier.
BSI industry-specific custom objects require schema mapping before HubSpot import
BSI CRM Enterprise deployments in banking, insurance, and retail often include industry-specific custom objects (policy holders, claims, coverage types, etc.) that have no direct HubSpot equivalent.
How we handle it
We map these to HubSpot custom objects, but custom object schemas must exist in HubSpot before data can land. We deliver a HubSpot custom object setup plan as part of the migration package so your HubSpot admin pre-creates the schema before the full migration run executes.
BSI workflows and approval sequences do not migrate and must be rebuilt manually
BSI CRM workflow definitions, approval chains, and automation rules exist in BSI's engine and do not export in a format compatible with HubSpot's workflow builder.
How we handle it
Migrating a BSI workflow to HubSpot Flow requires manual rebuild. FlitStack exports BSI workflow definitions as a structured reference document that lists each trigger, condition, and action so your HubSpot admin can replicate the logic. This documentation step is included in every BSI CRM migration project.
How the migration runs
Assess BSI CRM deployment model and API capabilities
FlitStack AI evaluates your BSI CRM instance to determine whether it runs on cloud or on-premise, identifies the API endpoints available for data extraction, and inventories all active custom objects and custom fields.
What this step covers
We also document BSI pipeline configurations, lifecycle property definitions, and any industry-specific schemas in use. This discovery phase produces the field mapping blueprint that drives the rest of the migration.
Map BSI objects and fields to HubSpot schema
We build a complete field-level mapping document that pairs every BSI CRM object (contacts, companies, deals, activities, notes, attachments, custom objects) to its HubSpot equivalent.
What this step covers
Value-mapping tables handle pick-list translations for lifecycle stages, industries, and deal stages across different pipelines. Transformation logic accommodates platform-specific field types and data formats. Any BSI field with no HubSpot equivalent becomes a HubSpot custom property — we generate the creation checklist with property types and validation rules for your HubSpot admin to pre-configure before migration.
Create HubSpot custom objects and properties before data lands
HubSpot custom objects and custom properties must exist before records can import.
What this step covers
FlitStack delivers a HubSpot setup plan listing every custom property to create, its type, expected values, and any validation rules required. Your HubSpot admin (or our team) creates the schema in a staging environment first to verify field configurations work correctly with sample data. We validate the setup including property associations and display logic before moving to the test migration phase, preventing schema conflicts during the full migration run.
Run sample migration with field-level diff
A representative slice of 100–500 records migrates first — covering contacts, companies, deals, and activities across your key data types.
What this step covers
We generate a field-level diff report comparing source values in BSI against landed values in HubSpot so you can verify lifecycle stage mapping, owner resolution, and association integrity before the full run commits. This sample run also validates that transformation logic handles your specific industry configurations and custom object relationships correctly.
Execute full migration with delta-pickup window
The full migration runs against HubSpot using BSI's API.
What this step covers
A delta-pickup window (typically 24–48 hours) captures any BSI records created or modified during the cutover so HubSpot reflects BSI's final state at go-live. FlitStack AI sequences the load correctly — companies first, then contacts, then deals with associations resolved at each step — to prevent orphaned records. Audit log records every operation.
Validate data and deliver migration package
Post-migration, we run reconciliation checks against BSI record counts, verify association integrity (contacts linked to correct companies, deals linked to correct contacts), and surface any records that failed to migrate with reason codes.
What this step covers
We deliver the complete migration package: field mapping document, workflow reference export, report-rebuild checklist, and rollback procedure. One-click rollback remains available for 30 days if reconciliation reveals systematic issues.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
BSI CRM to HubSpot migration pricing scales with record volume, custom property count, and data-model divergence between the platforms. Migrations with fewer than 20,000 total records and fewer than 30 custom properties typically fall in the lower range. BSI setups with industry-specific custom objects, complex multi-company contact associations, or large activity histories (call logs, meeting records) require additional transformation logic and extend into the upper range. BSI's on-premise data export process and API rate limits also affect execution time. FlitStack includes a sample migration and field-level diff in all projects so you verify mapping accuracy before the full run commits. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for BSI CRM to HubSpot →Why teams move from BSI CRM to HubSpot
- BSI CRM users consistently cite a steep learning curve and non-user-friendly interface as primary frustrations, with G2 reviews noting that adoption takes longer than expected and slows team productivity. HubSpot's onboarding experience and UI design attract teams seeking faster time-to-value from a CRM upgrade.
- HubSpot's all-in-one platform combines CRM, marketing automation, sales tools, and customer service in a single subscription with 2,400+ native integrations. BSI CRM's smaller ecosystem forces teams to maintain multiple disconnected tools, increasing total cost of ownership and creating data silos across sales, marketing, and service functions. Consolidation into HubSpot simplifies the tool stack and improves cross-team data visibility.
- BSI CRM's slow loading times during peak usage periods and occasional bugs reported by users create friction for sales teams that rely on real-time pipeline visibility. HubSpot's cloud infrastructure and modern frontend deliver faster page loads and more responsive deal tracking.
- Teams migrating from BSI CRM often cite HubSpot's free CRM tier as a low-risk starting point, with clear upgrade paths as the team scales. BSI CRM's pricing model lacks this flexibility, particularly for smaller teams in the SMB segment that want to evaluate the platform before committing.
Questions, answered
BSI CRM to HubSpot migration questions
How long does a BSI CRM to HubSpot migration take?
BSI CRM to HubSpot migrations typically complete in 48–72 hours for under 50,000 records. Larger datasets with 500,000+ records or complex custom-object schemas extend to 5–10 days. The longest planning step is mapping BSI's custom objects and lifecycle properties to HubSpot's schema — the actual data transfer moves quickly once the field map is validated. BSI's on-premise deployments may add 1–2 days for export configuration.
Will my BSI CRM workflows migrate to HubSpot?
No. BSI CRM workflows, approval sequences, and automation rules do not migrate. They exist in BSI's workflow engine and have no compatible export format for HubSpot's workflow builder. FlitStack AI includes a workflow-reference export as part of every BSI migration — we document each BSI workflow's triggers, conditions, and actions so your HubSpot admin can rebuild equivalent automations in HubSpot's workflow builder. This documentation step is manual but is included in the standard migration package.
What happens to BSI CRM contact lifecycle properties in HubSpot?
BSI CRM contact lifecycle properties map to HubSpot's lifecycle_stage field. If your BSI instance uses industry-specific or non-standard lifecycle values that don't match HubSpot's taxonomy, we create a HubSpot custom property to preserve the original value. HubSpot's marketing contact billing activates when contacts enter stages from 'lead' onward — we can temporarily set migrated contacts to 'subscriber' so your team controls when billing starts, then update lifecycle stages in HubSpot after review.
Can I migrate BSI CRM custom objects to HubSpot custom objects?
Yes. BSI CRM custom objects (available in Enterprise tiers, common in banking, insurance, and retail deployments) map 1:1 to HubSpot custom objects. Custom object schemas must exist in HubSpot before migration — FlitStack delivers a setup plan listing every custom object to create and its properties. N:N associations between BSI custom objects require HubSpot junction objects, which we surface in the mapping plan before migration runs.
How does BSI's on-premise deployment affect the migration process?
BFS I CRM on-premise instances (common for data-residency compliance in banking and insurance) may require direct database exports, file-system access, or authentication tokens not needed for BSI cloud tenants. We adjust the export approach during discovery. This adds planning time but does not block migration — FlitStack works with BSI's export utilities and API endpoints regardless of hosting model. Your data residency requirements are documented and respected throughout.
Does the migration affect my BSI CRM account during cutover?
No. FlitStack AI uses read-only API access to BSI CRM during migration — your team continues working in BSI throughout the process. A delta-pickup window (24–48 hours after the initial migration run) captures any records created or modified in BSI during cutover so HubSpot reflects the final state at go-live. BSI users can continue logging activities, updating contacts, and managing deals until the moment of switchover.
What happens to my BSI reports and dashboards?
BSI CRM reports and dashboards do not migrate — the report definitions are destination-side schema in HubSpot. However, the underlying data (contacts, companies, deals, activities) migrates completely. FlitStack delivers a report-rebuild reference sheet listing every BSI report, its intended metrics, and the HubSpot equivalents. Your HubSpot admin uses this as a checklist to recreate reports in HubSpot's reporting tools. We also preserve the original BSI field names as custom properties so metric definitions reference the same underlying data.
How does HubSpot's marketing contact billing affect migrated BSI contacts?
HubSpot charges for marketing contacts — contacts at lifecycle stages from 'lead' onward. Migrating BSI contacts into HubSpot with active lifecycle stages may immediately expand your marketing contact count and affect billing. We can set migrated contacts to 'subscriber' (outside the paid tier) temporarily, preserve their original BSI lifecycle value, and then update lifecycle stages in HubSpot on a schedule your team controls. This lets you audit migrated data before HubSpot's marketing contact billing activates.
Related migrations
HubSpot implementation
Set up HubSpot and migrate into it as one engagement.
See the service → Bigin by Zoho CRM to HubSpotMapping · history · rollbackMoEngage to HubSpotMapping · history · rollbackOntraport to HubSpotMapping · history · rollbackMyCase to HubSpotMapping · history · rollbackCreatio to HubSpotMapping · history · rollbackLess Annoying CRM to HubSpotMapping · history · rollbackSources: official documentation
- Format import files — HubSpot Knowledge Base
- Create and edit custom objects — HubSpot Knowledge Base
- Import objects programmatically — HubSpot Knowledge Base
- Understand property field types in HubSpot
- Associate records on CRM objects — HubSpot Knowledge Base
- Integration throughput and limits — HubSpot Knowledge Base
- HubSpot Cloud Infrastructure and Data Hosting FAQ
Get a quote
Moving from BSI CRM 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