Migrate from LeadDesk to HubSpot Service Hub

LeadDesk Contacts migrate 1:1 to HubSpot Contacts via REST API or CSV export depending on the customer's current tier (Advanced unlocks API; Instant and Essential require CSV). Phone numbers, names, custom fields, and email addresses transfer directly. We resolve the contact's associated Campaign and Project as ticket associations or custom properties on the Contact record. Any LeadDesk Contacts without email addresses are flagged for manual review because HubSpot requires an email for full CRM functionality.

LeadDesk Campaigns and Projects serve as parent containers for outbound initiatives and cannot map to a single HubSpot object. We split them across two HubSpot constructs: each unique LeadDesk Campaign or Project becomes a HubSpot Ticket Pipeline, and the individual call records and leads associated with that Campaign or Project become Ticket records assigned to that Pipeline. Campaign status and Sponsor assignment are preserved as custom ticket properties. If the customer has more than 20 unique Campaigns or Projects, we scope the top 20 by record volume and document the remainder for manual pipeline creation post-migration.

LeadDesk Leads with a status of converted or closed-won map to HubSpot Contacts. Unqualified or in-progress Leads map to HubSpot Leads. We determine the split using LeadDesk's lead status and outcome fields, preserving the original LeadDesk lead score as a custom field on the HubSpot record. Outcome codes are preserved as a custom property for reporting continuity.

LeadDesk call records include duration, disposition (Result and Outcome), agent assignment, and campaign linkage. We extract call history as structured records and map them to HubSpot Task with TaskSubtype = Call. Call duration migrates to CallDurationInSeconds, disposition codes migrate to a custom task field ld_disposition__c, and the original timestamp preserves the activity timeline order. Parent Contact resolution uses LeadDesk's contact association by email match against HubSpot Contacts. Bulk API with chunking is required for migrations exceeding 100,000 call records.

LeadDesk Results and Outcomes are call disposition codes — the specific end-state of a call attempt. We extract the full disposition taxonomy and normalize it to HubSpot Ticket Status values within the mapped Pipeline. LeadDesk disposition codes that have no clear HubSpot equivalent are preserved as a custom multi-select picklist property on the Ticket object. We flag any disposition that appears on more than 10 percent of call records for priority mapping during scoping.

LeadDesk chatbot analytics export as a time-bounded ZIP containing four CSV files (conversations, outcomes, timing, and agent). We decompress, parse, and map conversation timestamps, intents, and outcomes to HubSpot's Conversations inbox. We confirm the export date range with the customer during discovery and validate the four CSV files before proceeding. Chatbot conversations outside the selected date range are not recoverable after migration; this is a permanent data loss risk if not caught during scoping.

LeadDesk agent activities track login time, talk time, wrap-up, and utilization. We export activity logs as structured time-series records and map them to HubSpot Tasks with custom fields (talk_time__c, wrap_time__c, utilization_pct__c). Agent performance reporting is not native in HubSpot Service Hub — we recommend HubSpot's built-in reporting or a custom report type for agent metrics post-migration.

LeadDesk Offices represent multi-site deployment nodes. We migrate Office records with their associated timezone as a custom property on the relevant HubSpot Users or as a Team designation. VoIP routing configuration has no direct HubSpot equivalent and is documented for IT rebuild.

LeadDesk Teams group Agents under Teamleaders and Managers. We preserve team membership and reporting hierarchy, mapping them to HubSpot Teams. Teamleader and Manager roles map to HubSpot Team Admin roles where applicable. Role preservation is documented in a separate permissions matrix for the customer's admin to configure post-migration.

LeadDesk allows custom fields on contacts and leads. We map these field-by-field, creating corresponding HubSpot Contact Properties with matching field types. Complex nested objects or unsupported data types (e.g., LeadDesk-specific JSON blobs) are flagged for manual review before migration. The customer chooses whether to drop unsupported fields or reformat them as string properties.

LeadDesk dialer modes (preview, power, predictive, AI) and round settings are stored per campaign. HubSpot Service Hub has no native dialer, IVR, or outbound calling feature. We document the full dialer configuration for each LeadDesk Campaign as a written record, and the customer must select a separate calling solution (HubSpot calling add-on, a third-party dialer integration, or a dedicated CCaaS platform) post-migration. This is a structural gap, not a migration failure.

LeadApps are add-on applications within LeadDesk. We export their configuration as JSON where the platform exposes it, but we do not migrate their runtime state. LeadApps must be reconfigured in the destination platform or replaced with HubSpot App Marketplace equivalents. We flag each active LeadApp by name and function in the handoff documentation.