Skip to content
Get a quote

EspoCRM to HubSpot migration

Moving from EspoCRM to HubSpot connects your open-source, self-hosted CRM data to HubSpot's unified platform. FlitStack AI maps every EspoCRM entity — leads, contacts, accounts, opportunities, cases, and custom entities — into HubSpot's Contacts, Companies, Deals, and Tickets objects, preserving original timestamps and owner assignments while handling EspoCRM's Entity Manager custom fields as HubSpot custom properties.

Short answer

FlitStack AI migrates contacts, companies, deals, tickets and engagements from EspoCRM 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.

By

Source EspoCRM
DestinationHubSpot
ContactCompanyDealTicketEngagement
Mapped field by field · sample run · one-click rollback

What moves from EspoCRM to HubSpot?

EspoCRM's data model centers on Leads, Contacts, Accounts, Opportunities, Cases, and Activities — with the Entity Manager adding custom entities and fields through a non-code interface.

Read the full summary

HubSpot consolidates these into four core CRM objects (Contacts, Companies, Deals, Tickets) plus an engagement model for calls, emails, and meetings. FlitStack AI reads EspoCRM via its REST API (paginated at 200 records per call), extracting all standard and custom entity data including multi-enum and dynamic-logic fields. We map EspoCRM Leads and Contacts to HubSpot Contacts (routing by lifecycle stage if applicable), Accounts to Companies, Opportunities to Deals, and Cases to Tickets. Custom Entity Manager entities migrate as HubSpot custom objects (Enterprise tier) or as custom properties on standard objects. EspoCRM workflows and BPM processes cannot migrate — their definitions export as JSON for manual rebuild in HubSpot's automation tools. We sequence the migration so foreign-key dependencies resolve correctly: accounts first, then contacts, then deals and cases, then activities. A delta-pickup window (24–48 hours) captures in-flight changes during cutover, and a one-click rollback is available if reconciliation detects unexpected gaps.

direct

Lead → Contact

EspoCRM Leads map directly to HubSpot Contacts, preserving all standard fields such as name, email, phone, and title.

How it maps

If EspoCRM includes a lead-status picklist (new, assigned, converted), that status is transferred as a HubSpot custom property, allowing your team to recreate the original lifecycle progression within HubSpot after migration.

direct

Contact → Contact

Each EspoCRM Contact field—including name, email address, phone number, job title, street, city, state, postal code, country, and social URLs—maps directly to the corresponding HubSpot Contact property.

How it maps

The EspoCRM link to an Account converts to a HubSpot Company association once the Account entity has been loaded, ensuring the relationship appears in the HubSpot timeline.

direct

Account → Company

EspoCRM Accounts are translated into HubSpot Companies, where the account name populates the Company name, the domain field fills the website property, and address components (street, city, state, postal code, country) are consolidated into HubSpot's compound address field.

How it maps

Any parent-account hierarchy present in EspoCRM is reproduced as HubSpot parent-company associations, preserving the original corporate structure.

direct

Opportunity → Deal

EspoCRM Opportunities migrate to HubSpot Deals.

How it maps

Each EspoCRM pipeline maps to a HubSpot pipeline; stage names translate via value-by-value mapping. Amount, close date, probability, and owner transfer directly. The opportunity's linked account and contacts become the Deal's associated Company and Contact associations.

direct

Case → Ticket

EspoCRM Cases map to HubSpot Tickets.

How it maps

Case status (new, open, resolved, closed) translates to HubSpot ticket status via value mapping. Priority and case number migrate as custom properties for traceability. The original case ID is preserved as Source_Case_ID__c for reconciliation.

direct

Task → Engagement (Task)

EspoCRM Tasks are imported as HubSpot engagement tasks, copying the task subject, full description, due date, status, and priority fields directly.

How it maps

The assigned user is resolved by matching the EspoCRM user email to a HubSpot user record; any email that does not find a match is logged in the pre‑migration report, allowing your team to assign a fallback owner before the migration proceeds.

What moves15 objects
EspoCRMHubSpot
  • LeadContact1:1
  • ContactContact1:1
  • AccountCompany1:1
  • OpportunityDeal1:1
  • CaseTicket1:1
  • TaskEngagement1:1

+ 9 more in the mapping below

How EspoCRM 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.

DimensionEspoCRMHubSpot
Deployment modelSelf-hosted (AGPLv3) or Elestio cloud; server under your controlMulti-tenant SaaS; hosted and maintained by HubSpot
Contact modelSeparate Lead and Contact objects; lead can convert to ContactSingle Contact object with lifecycle_stage property tracking progression
Company/Account namingAccount entity with name, industry, employee countCompany object with name, industry, number of employees; domain field for web lookup
Deal/Opportunity namingOpportunity entity with stage, amount, probability, close dateDeal object with pipeline (multiple pipelines available), stage, amount, close date
Support case modelCase entity with status, priority, number; attached to account/contactTicket object with status, priority, source; attached to contact or company
Activity/engagement modelActivities (calls, emails, meetings, tasks) stored as separate entities linked to recordsHubSpot engagement model for calls, emails, meetings; logged as engagements with timestamps and owners
Customization approachEntity Manager for custom entities, fields, and relationships; no-code interfaceCustom properties on standard objects; custom objects (Enterprise) with schema defined in settings
AutomationWorkflows and BPM module for process automationWorkflows, Sequences, and Automation in HubSpot; rebuilt manually post-migration

EspoCRM to HubSpot field mapping

The 30 most-used fields of 66 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.

Field mapping5 shown
EspoCRMHubSpot
  1. first_nameLead firstnameContact
  2. last_nameLead lastnameContact
  3. email_addressLead emailContact
  4. phone_numberLead phoneContact
  5. mobile_phoneLead mobilephoneContact
EspoCRM fieldHubSpot fieldMappingNote
Lead.first_nameContact.firstnamedirect
Lead.last_nameContact.lastnamedirect
Lead.email_addressContact.emaildirect
Lead.phone_numberContact.phonedirect
Lead.mobile_phoneContact.mobilephonedirect
Lead.job_titleContact.jobtitledirect
Lead.lead_statusContact.hs_lead_statusvalue_mappingLead status pick-list values map value-by-value to HubSpot's hs_lead_status. Custom EspoCRM status values require HubSpot custom property creation.
Lead.created_atContact.original_createdatecustom_field_requiredHubSpot's createdate reflects migration timestamp. Original EspoCRM created_at preserved as custom datetime property for historical reporting continuity.
Lead.modified_atContact.original_lastmodifieddatecustom_field_requiredOriginal EspoCRM modified_at stored as custom datetime to preserve change history in HubSpot reports.
Lead.opportunity_amountContact.deals_amountcustom_field_requiredLinked opportunity amounts roll up as a custom number property on the Contact for quick reference.
Contact.first_nameContact.firstnamedirect
Contact.last_nameContact.lastnamedirect
Contact.email_addressContact.emaildirect
Contact.phone_numberContact.phonedirect
Contact.mobile_phoneContact.mobilephonedirect
Contact.job_titleContact.jobtitledirect
Contact.account_idContact.associatedcompanyidtransformedEspoCRM's account_id resolves to HubSpot's associatedcompanyid lookup after Account entity migrates to Company object.
Contact.address_streetContact.addressdirect
Contact.address_cityContact.citydirect
Contact.address_stateContact.statedirect
Contact.address_postal_codeContact.zipdirect
Contact.address_countryContact.countrydirect
Contact.created_atContact.original_createdatecustom_field_requiredHubSpot's native createdate is set at migration time; original EspoCRM created_at stored as a custom datetime property.
Contact.modified_atContact.hs_lastmodifieddatecustom_field_requiredOriginal EspoCRM modified_at preserved as custom datetime for audit and historical reporting.
Contact.idContact.source_system_idcustom_field_requiredEspoCRM record ID stored on the HubSpot Contact as a custom string field for traceability and delta-run de-duplication.
Account.nameCompany.namedirect
Account.websiteCompany.websitedirect
Account.industryCompany.industryvalue_mappingIndustry pick-list values mapped value-by-value. EspoCRM custom industry values require HubSpot custom property creation.
Account.employee_countCompany.numberofemployeesdirect
Account.annual_revenueCompany.annualrevenuedirect

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

EspoCRM REST API caps at 200 records per GET call, requiring batched pagination

EspoCRM's built-in REST API limits each response to 200 records per GET request — this is a hard-coded parameter configurable only in EspoCRM's config file (maxSize param).

How we handle it

During migration, FlitStack AI handles pagination internally, fetching all EspoCRM records in sequential batches. This does not affect data completeness but extends the extraction phase proportionally to your total record volume. For EspoCRM instances with heavy custom entity usage, the extraction phase may take longer because each custom entity type also paginates at 200 records. We recommend setting aside extraction time proportional to your total entity count.

medium

HubSpot's lifecycle_stage is a Contact property with no EspoCRM native equivalent

EspoCRM has no single field equivalent to HubSpot's lifecycle_stage — it uses separate Lead and Contact objects with status fields, but no unified lifecycle property tracking progression from Subscriber through Evangelist.

How we handle it

When migrating to HubSpot, your team decides which EspoCRM field drives lifecycle_stage population: the contact's most-recent activity date, the account type, or a custom field your admin has created in EspoCRM. We surface this decision point before the migration runs. If no suitable field exists, contacts land with a default lifecycle_stage value and your team sets it in HubSpot post-migration.

medium

EspoCRM multi-enum fields cap at 20 options by default

EspoCRM's multi-enum field type defaults to a 20-option maximum (enforced in the EspoCRM source code).

How we handle it

Teams that use multi-enum for fields like industry segments, product categories, or team assignments may have values exceeding this cap stored across multiple fields or in custom fields instead. HubSpot custom properties have no such cap, but the mapping from EspoCRM's multi-enum structure (which stores an array of values) to HubSpot's flat multi-select property requires flattening the array into HubSpot's pipe-delimited format during import. We handle this transformation automatically, but values above the EspoCRM 20-option limit need to be identified during the discovery phase.

medium

HubSpot has no native equivalent for EspoCRM Teams and Roles

EspoCRM's Teams and Roles model provides fine-grained record-level access control — a user can belong to multiple Teams, and Roles define field-level read/write permissions per entity.

How we handle it

HubSpot's permission model is role-based at the object level (free, starter, professional, and enterprise seat roles) but does not expose per-field read/write rules. Teams that rely on EspoCRM's access-control model need to plan how to map their permission structure: HubSpot Teams (Enterprise) provide group-level data visibility but not field-level restrictions. We document your EspoCRM role and team configuration during discovery so your HubSpot admin can design an access model that approximates your current security posture.

low

EspoCRM workflow definitions export as JSON, not as actionable automation

EspoCRM stores workflow definitions in its own internal format, including trigger conditions, filters, and action sequences.

How we handle it

HubSpot's automation engine (Workflows, Sequences) uses a completely different trigger-action model — there is no automated conversion. FlitStack AI exports your EspoCRM workflow JSON from the database as a reference artifact. Your HubSpot admin uses this export as a rebuild brief for HubSpot Workflows. We recommend prioritizing your five most-critical EspoCRM workflows for manual rebuild before go-live, with the rest migrated on a timeline that matches your team's capacity.

How the migration runs

  1. Extract EspoCRM data via REST API with batched pagination

    FlitStack AI connects to your EspoCRM instance via its REST API using your API credentials.

    What this step covers

    Because EspoCRM's API returns a maximum of 200 records per GET call, we paginate through every entity type in sequential batches: Leads, Contacts, Accounts, Opportunities, Cases, Tasks, Meetings, Calls, Emails, Notes, and each custom Entity Manager entity. We extract full record payloads including all custom fields, relationship IDs, and metadata (created_at, modified_at, assigned_user). The extraction runs in a read-only scope — no EspoCRM records are modified during this phase.

  2. Pre-create HubSpot custom properties and pipelines before data loads

    Before any data lands in HubSpot, we inspect EspoCRM's Entity Manager metadata to identify all custom fields and relationship types.

    What this step covers

    Custom fields that have no HubSpot standard equivalent are pre-created as HubSpot custom properties (in snake_case for internal naming). EspoCRM pipelines are pre-created as HubSpot pipelines. This step requires a HubSpot admin to confirm custom property names and pipeline configurations before the migration plan is finalized. We deliver a schema-setup checklist so HubSpot-side preparation runs in parallel with EspoCRM data extraction.

  3. Run a sample migration with field-level diff before full commit

    We migrate a representative slice of 100–500 EspoCRM records spanning each entity type and including edge cases (records with no linked account, records with multi-enum values, records owned by inactive EspoCRM users).

    What this step covers

    A field-level diff report compares source and destination field values side-by-side so your team can verify mapping correctness before the full run. This sample run also surfaces any EspoCRM multi-enum values exceeding the 20-option cap and any EspoCRM user emails that have no matching HubSpot user — both are resolved before the full migration executes.

  4. Execute full migration with dependency-ordered load sequence

    The full migration runs in dependency order: Accounts first (HubSpot requires Companies to exist before Contacts can link via associatedcompanyid), then Contacts and Leads, then Deals and Cases, then Activities.

    What this step covers

    Foreign keys resolve by matching EspoCRM record IDs to their newly created HubSpot record IDs in our mapping table. EspoCRM owners resolve to HubSpot owners by email match — unmatched owners are assigned to a designated fallback owner and flagged in the reconciliation report. All original EspoCRM timestamps (created_at, modified_at) are preserved in custom datetime fields on the HubSpot records.

  5. Cut over with delta-pickup window and one-click rollback

    Once the full migration completes and the sample validation passes, your team executes the cutover from EspoCRM to HubSpot.

    What this step covers

    A delta-pickup window (typically 24–48 hours) runs concurrently, capturing any EspoCRM records created or modified during the cutover window and syncing them to HubSpot. An audit log records every operation. If post-migration reconciliation reveals unexpected gaps — missing records, incorrect associations, or field-mapping errors — one-click rollback reverts the HubSpot environment to its pre-migration state so your team can investigate and re-run without data loss.

EspoCRM HubSpot
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · HubSpotRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

48–72 hours for under 50,000 recordsTypical, smaller accounts
7–10 days for over 200,000 records or heavy custom-entity / multi-team setupsLarge or heavily customised accounts

Pricing reflects record count, custom field count, and data-model divergence between EspoCRM and HubSpot. EspoCRM setups with extensive Entity Manager usage (custom entities, multi-enum fields, complex relationships) fall in the upper range because each custom entity type requires its own HubSpot schema pre-creation and field-level mapping validation. Workflow and BPM export-and-rebuild scoping adds planning time but does not inflate the data-migration cost itself — automation rebuild is a separate service. Historical activity migration (calls, emails, meetings with full engagement metadata) requires HubSpot engagement object creation per record and pushes scope toward the upper band. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for EspoCRM to HubSpot →

Why teams move from EspoCRM to HubSpot

  • EspoCRM requires self-hosted infrastructure and ongoing server maintenance — as your team grows, DevOps overhead competes with sales-focused work. You must handle provisioning, backups, security patches, and occasional downtime. HubSpot's SaaS model eliminates server management, provides automatic updates, and scales with your team without requiring internal IT capacity.
  • EspoCRM's integrations ecosystem is limited compared to HubSpot's marketplace of 1,000+ native connectors. Teams report that HubSpot's native integrations with marketing, support, and analytics tools reduce the need for custom API work that EspoCRM demands. Faster implementation, lower development costs, and a broader partner network accelerate ROI.
  • EspoCRM's reporting and dashboard capabilities are basic — built-in reports lack the customization and visual depth that sales leaders need at scale. HubSpot's analytics suite, including custom reports and revenue attribution, addresses reporting gaps that EspoCRM reviewers consistently flag. Interactive charts, drill-down filters, and scheduled email insights empower data-driven decisions.
  • HubSpot's inbound marketing and sales-enablement tools (Forms, Live Chat, email sequences, landing pages) integrate natively with the CRM object model — eliminating the gap that EspoCRM users encounter when they need marketing automation on top of their CRM data. Unified lead capture, automated nurture, and closed-loop reporting streamline the buyer journey.
  • EspoCRM's community-driven support model works well for technical users but lacks the enterprise-grade SLA and onboarding resources that growing teams need. HubSpot's documentation, customer success, and partner ecosystem provide structured support as headcount scales. Professional services, training portals, and 24/7 support tickets ensure rapid issue resolution.

Questions, answered

EspoCRM to HubSpot migration questions

How long does an EspoCRM to HubSpot migration take?

Most EspoCRM-to-HubSpot migrations complete within 48–72 hours for under 50,000 total records. Larger datasets exceeding 200,000 records or setups with extensive Entity Manager custom entities extend to 7–10 days. The longest planning step is mapping EspoCRM's custom fields and Entity Manager entities to HubSpot's custom property schema — this requires your HubSpot admin to pre-create properties before the data load phase begins.

Will my EspoCRM workflows and BPM processes migrate to HubSpot?

No. EspoCRM workflows and BPM module definitions are not migratable to HubSpot — the automation logic, triggers, conditions, and action sequences are stored in incompatible formats. FlitStack AI exports your EspoCRM workflow JSON as a reference document your HubSpot admin can use as a rebuild brief for HubSpot Workflows. This export is included in the migration package. Automations must be rebuilt manually in HubSpot's Workflow or Sequence builder, and we recommend prioritizing your five most-critical EspoCRM workflows before go-live.

What happens to my EspoCRM Cases in HubSpot?

EspoCRM Cases map to HubSpot Tickets. Case status values (new, open, resolved, closed) translate to HubSpot's ticket status via value mapping, and case priority translates to HubSpot ticket priority. The original EspoCRM case number is preserved as a custom property on each HubSpot ticket so your team can cross-reference historical support records. If your EspoCRM instance uses custom case fields, those map to HubSpot custom properties on the Ticket object.

Can I migrate EspoCRM Entity Manager custom entities to HubSpot?

Yes, if your HubSpot subscription is on the Enterprise tier — only HubSpot Enterprise supports custom objects. EspoCRM Entity Manager custom entities map 1:1 to HubSpot custom objects with their own schema. Custom entity relationships (one-to-many, many-to-many) translate to HubSpot associations. If your HubSpot plan is Starter, Professional, or Starter Suite, EspoCRM custom entity data maps as custom properties on standard HubSpot objects (Contact, Company, Deal) instead, which may require collapsing some fields or storing related data in a single multi-select property.

How does EspoCRM's account hierarchy translate to HubSpot Companies?

EspoCRM supports parent-account hierarchies — a parent Account can have multiple child Accounts. In HubSpot, parent-company associations use the parent_id field on the Company object. We migrate the hierarchy so the parent Account becomes the HubSpot parent Company, and child Accounts become child Companies under the parent. If EspoCRM uses circular or self-referencing parent IDs, these are flagged during discovery and resolved manually before the migration runs.

Does the migration affect my EspoCRM account during the cutover?

No. FlitStack AI uses read-only API access to EspoCRM during extraction — your team continues working in EspoCRM throughout the migration. A delta-pickup window (24–48 hours) runs after the initial bulk load, capturing any EspoCRM records created or modified during the cutover period and syncing them to HubSpot. This ensures HubSpot reflects EspoCRM's final state at go-live. No EspoCRM data is altered, deleted, or locked during the migration.

What happens to EspoCRM Call and Meeting records with original timestamps?

EspoCRM call and meeting records migrate as HubSpot engagement records (engagement type Call or Meeting) attached to the corresponding HubSpot Contact. The original EspoCRM call direction, duration, outcome, and meeting start/end timestamps all transfer directly. HubSpot's engagement timeline displays each call and meeting with its original timestamp, subject, and owner — giving your team a complete activity history visible alongside other HubSpot data.

Get a quote

Moving from EspoCRM 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