Migrate from QuickDesk to Twenty CRM

QuickDesk Contact records map to Twenty's People object. All standard fields (name, email, phone, address) transfer directly. The QuickDesk company text field is preserved separately for later Company reconstruction. Any custom contact properties are mapped to Twenty custom fields that must be created in Settings -> Data Model before the CSV import phase begins, per Twenty's requirement that fields must exist before import.

QuickDesk Lead records map to Twenty's People object using the same target as Contact records. Lead source, creation date, and status fields transfer to Twenty People custom fields. Where the customer's QuickDesk account uses both Contacts and Leads as distinct lifecycle stages, we preserve the distinction using a custom people_type__c field that records whether the original was a Contact or Lead in QuickDesk.

QuickDesk stores company names as a text field on contact records, not as a separate Company or Account object. We extract all distinct company values from contact records, normalize them (trim whitespace, remove identical duplicates), and create Company records in Twenty. Contacts sharing the same company name are linked to the corresponding Twenty Company via the People-Company relationship. The customer reviews and resolves any contacts with identical company strings that may represent the same organization.

QuickDesk's Customer Pipeline maps to Twenty's Opportunity object. Each QuickDesk Pipeline stage becomes a Twenty Opportunity stage value. The pipeline's stage progression rules (prospecting, qualification, proposal, negotiation, close) are preserved as stage labels. Pipeline-level deal values transfer to the Opportunity amount field. Where QuickDesk has multiple pipelines, we create Twenty Opportunity records tagged by pipeline name using a custom field.

QuickDesk pipeline stages map to Twenty Opportunity stage values. Custom stage names in QuickDesk are preserved as custom Opportunity stage options in Twenty rather than renamed, ensuring no data loss. The customer can rename stages in Twenty post-migration if desired. Stage order and probability settings are recorded from QuickDesk and applied as stage configuration notes in Twenty.

QuickDesk custom fields on Leads and Contacts—including personalized lead form fields—map to Twenty custom fields on the People object. All custom field definitions (name, type, options for picklists) must be pre-created in Twenty Settings -> Data Model before import. We extract the full custom field schema from QuickDesk during scoping and generate a field creation checklist for Twenty. Field order in Twenty is configurable post-migration.

QuickDesk activity records—logged calls with duration and outcome, tasks with due dates and assignees—map to Twenty Tasks. Call logs preserve duration and disposition in custom Task fields. Goals and activity tracking records map to Notes attached to the relevant People record. Automated activity triggers from QuickDesk's Customer Experience Automation do not migrate; the trigger logic is documented separately for manual rebuild.

QuickDesk Calendar records map to Twenty Notes with a calendar_event__c custom field flag. Recurring calendar events and scheduled appointments require manual review because QuickDesk's calendar integration and recurrence patterns may not map directly to Twenty's event model. The customer should export any active calendar events as a backup before the migration window opens.

QuickDesk owners map to Twenty Members by email match. We extract all owner IDs referenced on Contacts, Leads, and Pipeline records and resolve them to Twenty workspace Members. Per Twenty's documentation, users must be invited and accept invitations before data import, so that assignee and owner references are satisfied at migration time. Any owner without a matching Twenty Member goes to a reconciliation queue for manual provisioning.

QuickDesk personalized lead form fields map to Twenty custom fields on the People object. The form field name and data type are preserved. We extract the full lead form schema during scoping, generate a custom field creation checklist for Twenty, and include field-level mapping in the import CSV. Fields must exist in Twenty before the import phase runs.