Migrate from QuickDesk to Freshsales

QuickDesk Contacts map directly to Freshsales Contacts. We extract all standard fields (name, email, phone, address) and any custom contact properties via the QuickDesk API. The company text field on the QuickDesk Contact is held as a lookup reference during this phase—it is not written to a contact field in Freshsales. Instead, it is resolved to the corresponding Account record created in the Accounts phase before Contacts are imported.

QuickDesk Leads map directly to Freshsales Leads with all custom lead form fields preserved. The lead source, creation timestamp, status, and any personalized form fields migrate as custom fields on the Freshsales Lead object. Freshsales requires that corresponding Contact or Account custom fields exist before field mapping can be configured during lead conversion; we create these fields in Freshsales during the schema design phase so that the mapping dropdown in Admin Settings has valid targets.

QuickDesk has no formal Account object—company information lives as a text field on Contact records. We extract every distinct company name value, deduplicate by normalized string match (trim, lowercase), and create Freshsales Account records. Contacts sharing the same company name are linked to the corresponding Account via the Account Lookup. We flag any company names with slight variations (e.g., 'Acme Corp' vs 'Acme Corporation') for the customer's admin to review before final Account merging in Freshsales.

QuickDesk Deals map to Freshsales Deals with the deal amount, name, expected close date, and pipeline stage preserved. We map the QuickDesk pipeline stage name to the corresponding Freshsales Deal stage value. Deal owner maps by email match to the Freshsales User record. Any custom properties on the QuickDesk Deal (e.g., deal type, competitor field) migrate as Freshsales Deal custom fields.

QuickDesk pipeline stages (e.g., Prospecting, Qualification, Proposal, Negotiation, Closed Won, Closed Lost) are extracted from the QuickDesk pipeline configuration. We recreate these as Freshsales Deal stages in the Admin Settings pipeline editor before Deal migration begins. Custom stage names in QuickDesk are preserved as-is and flagged for renaming to match Freshsales naming conventions if desired.

QuickDesk custom fields on Leads and Contacts, including fields created through personalized lead forms, are extracted with their field definitions and all values. We create the corresponding custom fields in Freshsales using field types that match (text, number, date, picklist, checkbox). The critical step is configuring Freshsales' field mapping under Admin Settings > Leads module before lead conversion happens—unmapped lead fields lose their data during conversion per Freshsales' conversion workflow. We document the mapping for every custom field so the customer's admin can configure it during sandbox testing.

QuickDesk sales activities—call logs with duration and outcome, tasks with due dates and assignees, and goal tracking records—map to Freshsales Activity records. Call logs migrate as Activities with type = call and the duration preserved. Task records migrate with Status, Priority, and ActivityDate preserved. Goal tracking records in QuickDesk are not standard Freshsales objects; we flag these for the customer to document as Freshsales targets or custom fields if the data is critical.

QuickDesk Calendar events and task records map to Freshsales Activities. Calendar events with start and end times migrate with the date preserved. Task records with due dates, descriptions, and assignees migrate as Freshsales Activities. Recurring tasks and calendar-based scheduling rules are not supported for migration; we document the recurrence patterns in QuickDesk so the customer's admin can configure Freshsales workflows for recurring task generation post-migration.

QuickDesk owners referenced on Contact, Lead, and Deal records are matched by email to Freshsales User accounts. Owners without a matching Freshsales User go into a reconciliation queue for the customer's admin to provision before the migration run. This is a required gating step because Freshsales requires OwnerId to be set on Deals and Activities.

QuickDesk automation rules and engagement triggers are not exposed via API and cannot be extracted programmatically. We conduct a manual audit of the QuickDesk account during scoping to identify all active automation rules, sequence names, and trigger conditions, and we deliver a written rebuild checklist with recommended Freshsales workflow equivalents. The customer's admin rebuilds these in Freshsales' workflow builder post-migration. This is documented as a non-migration deliverable, not skipped work.

QuickDesk's forecasting feature calculates pipeline health from stage values and historical close rates on read, not as stored data records. Forecast snapshots and historical forecast data cannot be exported. We recommend exporting any custom QuickDesk forecast reports as PDF before the cutover date. Freshsales provides its own forecasting model using migrated Deal data and stage values; the customer's admin rebuilds the forecast configuration based on Freshsales' standard forecasting setup.

QuickDesk personalized lead forms create custom fields per form submission, and these fields may not exist in Freshsales before migration. We extract all lead form field definitions from QuickDesk, create corresponding custom fields on the Freshsales Lead, Contact, and Account objects, and configure the Freshsales lead field mapping under Admin Settings so that custom field data survives the lead conversion process. This is a configuration-only mapping step that must be completed before any Lead conversion happens in Freshsales.