Migrate from QuickDesk to HubSpot

QuickDesk contacts migrate directly to HubSpot contacts. The contact's company_id resolves to a HubSpot company record via domain match or explicit company_name field before the contact is created, so Contact.vault_hs_company_id is populated correctly. If no matching HubSpot company exists, the contact is created without an association and flagged in the migration report for manual review.

QuickDesk companies migrate directly to HubSpot companies. HubSpot company properties (domain, industry, phone, address) are mapped from QuickDesk company fields. Parent-child company hierarchies use HubSpot's parent_company_id field. If a parent company in QuickDesk does not have a corresponding record in HubSpot, FlitStack creates a placeholder company and flags it for your team to either link to an existing HubSpot company or approve as a new record.

QuickDesk deals map to HubSpot deals with one significant transformation: QuickDesk's single-pipeline stages map to HubSpot's default pipeline stage values. If QuickDesk uses more than one pipeline, each pipeline becomes a separate named HubSpot pipeline. The mapping preserves stage order and closed-won/closed-lost status for each stage, and any custom QuickDesk stage properties are stored as HubSpot custom deal properties.

QuickDesk has no named-pipeline concept — all deals share one stage set. If your QuickDesk account uses multiple stage sets (e.g., SMB vs. Enterprise), each stage set migrates as a separate HubSpot named pipeline. Pipeline setup is delivered as a pre-migration plan.

Stage names map value-by-value from QuickDesk to HubSpot dealstage. Closed Won and Closed Lost values are preserved exactly. Any QuickDesk stage without a HubSpot equivalent is created as a custom stage before migration runs. Stage probability percentages are mapped from QuickDesk's stage settings, and the pipeline blueprint document lists each stage's order and probability for your HubSpot admin to confirm before the migration begins.

QuickDesk call logs migrate as HubSpot engagements with type=calls. Original timestamps, duration, call direction (inbound/outbound), and owner are preserved. Notes attached to a call log become HubSpot engagement metadata. Call disposition codes, if used in QuickDesk, are stored as a custom engagement property in HubSpot so your team can report on call outcomes without losing historical data.

QuickDesk notes migrate as HubSpot engagement notes, linked to the parent contact, company, or deal. Original create timestamps and note owner are preserved. Rich-text formatting is retained where the note body contains HTML. Attachments linked to QuickDesk notes are downloaded and re-uploaded to HubSpot file storage, then associated with the engagement note so all supporting documentation moves with the note.

QuickDesk custom objects map 1:1 to HubSpot custom objects (Enterprise-tier required). The HubSpot custom object schema is created first using QuickDesk's field names and types as the blueprint. N:N associations between custom objects in QuickDesk require a HubSpot junction object.

QuickDesk owner_id resolves by email match against HubSpot users. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts first or assigns records to a designated fallback owner. No record lands without a valid HubSpot owner.

QuickDesk file attachments linked to contacts, companies, or deals are downloaded and re-uploaded to HubSpot's file storage, then linked back to the parent CRM record. HubSpot's file size limit of 250 MB per file applies; larger files are linked as URL references.

QuickDesk sequences and automated outreach sequences have no HubSpot equivalent that accepts direct migration. FlitStack exports sequence definitions (step order, timing, template content) as a JSON document so your HubSpot admin can rebuild them using HubSpot sequences or a third-party sales engagement tool.

QuickDesk static lists migrate as HubSpot static lists — contacts are added by email match. Dynamic lists with filter rules cannot be replicated because HubSpot list filters operate on live property values; contacts enter the new HubSpot list and the dynamic logic is rebuilt as a HubSpot list or workflow enrollment criteria.