Migrate from LionDesk to HubSpot

LionDesk contacts map 1:1 to HubSpot contacts. The primary company link resolves to a HubSpot company record — if no matching company exists in HubSpot, we create one from the contact's company name before linking. Owner assignment uses email match to HubSpot users.

LionDesk company records map directly to HubSpot companies with full field fidelity. Address fields, website URL, phone number, and industry pick-list values transfer where present. Parent-company relationships and corporate hierarchies in LionDesk migrate as HubSpot parent company associations, preserving organizational structures and subsidiary relationships across the migration.

LionDesk deals map directly to HubSpot deals with full fidelity. If your LionDesk account uses multiple deal pipelines, each maps to a separate HubSpot pipeline. HubSpot Starter tier supports one pipeline only; Professional and Enterprise tiers enable multiple named pipelines with stage-based probability and forecast categories.

LionDesk task records—including reminders, to-dos, and action items tied to contacts or deals—migrate as HubSpot engagement tasks with full fidelity. Original create dates, due dates, and priority flags are preserved. Completed status carries over as the task's closed state, maintaining task history continuity.

LionDesk notes attached to contacts or deals become HubSpot engagement notes with complete fidelity. The note body text, formatting, and timestamp migrate intact. Author attribution is resolved by matching the creator's email address to a HubSpot user where possible, preserving accountability and ownership history.

Email history logged against LionDesk contacts migrates as HubSpot email engagements with full detail preservation. Subject line, body preview, sent timestamp, and open/click tracking data transfer where available. Full email bodies are imported as accessible via the LionDesk API, maintaining complete communication history and preserving all relevant correspondence.

LionDesk call logs and SMS message threads migrate as HubSpot engagements with type appropriately set to 'Call' or 'Meeting'. Call duration, outcome disposition, and exact timestamps are preserved. Thread content for SMS conversations migrates as embedded note attachments within the engagement record, maintaining conversation context and communication history.

LionDesk drip campaign logic (step sequence, delay rules, trigger conditions) cannot be executed in HubSpot — the automation engines are architecturally different. We export your drip campaign definitions as a JSON reference file documenting each step, delay, and condition for your HubSpot admin to rebuild in HubSpot's workflow builder.

LionDesk custom fields map to HubSpot custom properties. We create HubSpot properties with the corresponding type — Text to single-line text or multiple-line text, Number to number, Date to date, Dollar Amt to currency. Names exceeding HubSpot's 40-character API limit are truncated with a numeric suffix for uniqueness.

LionDesk user assignments on contacts and deals are resolved by matching the user email to an existing HubSpot user. Unmatched users are flagged before migration — your team creates HubSpot user accounts for them, or you assign their records to a designated fallback owner.

LionDesk contact tags map to HubSpot list memberships where the tag represents a static segment, or to a custom multi-checkbox property where the tag represents a characteristic or behavior. We document the complete tag-to-property mapping strategy in the migration plan before executing the migration run, ensuring clarity on how each classification transfers.

File attachments on LionDesk contacts or deals are downloaded and re-uploaded to HubSpot Files, then linked to the corresponding CRM record. File size limits per HubSpot's import tool apply — files over 25MB are linked as external URLs stored in a custom property.