Migrate from QuickDesk to Pipedrive

QuickDesk Contact records map to Pipedrive People. The primary contact fields—name, email, phone—migrate directly. QuickDesk's company text field is held for Organization creation and linked to the People record via Pipedrive's org_id field after the Organization phase completes. Custom properties on QuickDesk contacts migrate as Pipedrive custom fields on the People entity.

QuickDesk Lead records map to Pipedrive Lead. Lead source, creation date, status, and any custom lead form fields migrate as Pipedrive custom fields on the Lead entity. Pipedrive's Lead object uses the same field schema as Deals, so any QuickDesk custom lead form fields are pre-created in Pipedrive as Lead custom fields before import. QuickDesk leads do not auto-convert to Pipedrive People during migration; the customer decides when and how to run the Lead-to-People convert action post-migration.

QuickDesk stores company information as a text field on contact records rather than as a separate entity. We extract every distinct company name value, deduplicate matching names (accounting for case and whitespace variations), and create Pipedrive Organization records. Contacts sharing the same normalized company name are linked to the resulting Organization via org_id. The customer reviews the Organization merge list during scoping and approves or splits Organization candidates before we proceed.

QuickDesk's Customer Pipeline is a core object with configurable stages. We extract the pipeline name, all stage names, stage order, and stage-specific rules. Pipedrive supports multiple pipelines, each with its own stages. We map the QuickDesk pipeline to a Pipedrive pipeline with identically named stages (or renamed to match Pipedrive conventions if the customer requests alignment). Stage progression rules from QuickDesk are documented as Pipedrive automation triggers for the customer to rebuild.

QuickDesk stage names such as prospecting, qualification, proposal, negotiation, and close map to Pipedrive pipeline stages. We preserve stage probability percentages where they exist in QuickDesk and set them in Pipedrive. Custom stage names are carried over and the customer can rename them in Pipedrive post-migration. Stage color coding migrates if QuickDesk exposes this data via API.

QuickDesk custom fields on Leads and Contacts migrate to Pipedrive custom fields on the corresponding entity (People or Lead). Field types are mapped: text to text, number to number, date to date, dropdown to single-select picklist, multi-value fields to multi-select picklist. We pre-create all custom fields in Pipedrive before any data import begins so that the import mapping step can reference them directly.

QuickDesk tracks sales activities including calls logged and tasks set. These map to Pipedrive Activities. Call logs with duration and outcome migrate as Activity records of type call. Tasks with due dates and assignee information migrate as Activity records of type task. Automated activity triggers (those tied to QuickDesk's engagement automation) do not migrate because the automation logic is not exposed via API; the customer rebuilds these as Pipedrive workflow triggers post-migration.

QuickDesk's Calendar and Task features integrate with sales goals and activity tracking. We export task records with due dates, assignees, status, and priority. Recurring task patterns are not preserved because they are not exposed via API; the customer recreates recurring tasks as Pipedrive automation sequences if needed. Calendar-based scheduling does not migrate; Pipedrive's Google Calendar and Outlook integrations handle new calendar events post-migration.

Pipedrive does not support custom objects—only custom fields on its four core entities (People, Organizations, Deals, Activities). If QuickDesk has custom record types beyond standard Contacts, Leads, and Pipeline data, we document their field schemas and advise the customer on how to represent them as custom fields on Pipedrive's core entities or as tagged label sets. Complex relational structures require a different destination platform.

QuickDesk's forecasting feature calculates pipeline health based on stage values and historical close rates but stores derived analytics only. We cannot export forecast snapshots. We recommend capturing any custom forecast exports as PDFs before the cutover date. Pipedrive's built-in revenue forecasting is rebuilt post-migration using the migrated pipeline data, stage probabilities, and deal values.