Migrate from EspoCRM to HubSpot

EspoCRM Leads map directly to HubSpot Contacts, preserving all standard fields such as name, email, phone, and title. 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.

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

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. Any parent-account hierarchy present in EspoCRM is reproduced as HubSpot parent-company associations, preserving the original corporate structure.

EspoCRM Opportunities migrate to HubSpot Deals. 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.

EspoCRM Cases map to HubSpot Tickets. 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.

EspoCRM Tasks are imported as HubSpot engagement tasks, copying the task subject, full description, due date, status, and priority fields directly. 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.

EspoCRM Meetings become HubSpot engagement meetings, transferring the start and end timestamps, subject line, and detailed body text. All related contacts or deals are linked to the meeting in HubSpot so the context appears on the record’s timeline. The original creation and modification timestamps are stored on the HubSpot engagement, keeping the historical record accurate.

EspoCRM Call records are imported as HubSpot call engagements, preserving call direction, duration, subject, and disposition outcome. The original call start time and owner are transferred to HubSpot, so each call appears with its timestamp and assigned user in the contact’s activity feed. This maintains a complete call history for auditing and follow‑up.

EspoCRM email records become HubSpot email engagements, carrying the subject line, full body (whether plain text or HTML), and the original sent timestamp. Each email is linked to the appropriate HubSpot contact or company, and the engagement timeline displays the sender, recipient, and timestamp, providing a clear chronological view of all email interactions.

EspoCRM Notes are imported as HubSpot Notes and attached to the relevant Contact, Company, Deal, or Ticket record. The rich‑text note body transfers directly, preserving formatting. When a note contains an attached file, FlitStack AI downloads the file from EspoCRM storage, re‑uploads it to HubSpot Files, and links it to the note, ensuring the attachment is accessible in HubSpot.

FlitStack AI extracts file attachments from EspoCRM’s designated storage directory, uploads each file to HubSpot Files, and links the file to the appropriate HubSpot record (Contact, Company, Deal, Ticket, or Note). During extraction, file size is validated against HubSpot’s 25 MB per‑file limit; files exceeding this threshold are flagged for manual handling or compression before the migration proceeds.

EspoCRM Entity Manager custom entities map 1:1 to HubSpot custom objects (available on Enterprise tier). Custom entity relationships (one-to-many, many-to-many) translate to HubSpot custom object associations. If HubSpot Enterprise is not available, custom entity data maps as custom properties on standard objects.

EspoCRM Users map to HubSpot Users by email address match. Unmatched users are flagged before migration so your team can either invite them to HubSpot or assign their records to a fallback owner. EspoCRM Teams translate to HubSpot Teams (Enterprise) or remain as user groupings handled by HubSpot role assignments.

EspoCRM Workflows and BPM module definitions are not migratable. We export the workflow JSON definition and trigger logic from EspoCRM so your HubSpot admin can reference it when rebuilding in HubSpot Workflows. This export is included in the migration package at no additional charge.

EspoCRM Campaigns are transferred to HubSpot as Campaigns, replicating campaign names, status, and start/end dates. However, campaign assets such as email templates, UTM parameter sets, and landing pages must be recreated in HubSpot’s campaign builder. The existing EspoCRM campaign member records—tracking which contacts are enrolled—are migrated as Campaign Member associations linked to the matching HubSpot Contacts, preserving enrollment history.