Migrate from QuickDesk to Mailchimp

QuickDesk Contacts map to Mailchimp Members in a single Audience. Standard fields (first name, last name, email, phone) migrate directly to Mailchimp merge fields FNAME, LNAME, EMAIL, and PHONE. Any custom contact properties extract via the QuickDesk API and map to custom Mailchimp merge fields, which accept up to 255 characters per field. Contacts with no email address cannot migrate as Members; we flag these records separately for the customer's admin to review.

QuickDesk Leads map to Mailchimp Members in the same Audience as Contacts. We apply a Tag (e.g., 'QuickDesk-Lead-Source: [sourcename]') to distinguish leads from contacts in the migrated audience. Lead status and creation date are preserved as merge fields or Tags so the customer can rebuild segments in Mailchimp based on lead origin and age.

QuickDesk stores company as a text property on Contact and Lead records, not as a separate object. We extract every distinct company string, normalize by email domain for deduplication (e.g., [email protected] and [email protected] both yield company tag 'Acme'), and apply the company name as a Tag on each Member record. Where contacts share the same email domain but have different company text values, we preserve both tags and flag the ambiguity for the customer to resolve.

QuickDesk pipeline stages (prospecting, qualification, proposal, negotiation, close) have no native Mailchimp equivalent. We document each stage name and the count of records per stage, then apply stage-name Tags to the corresponding Member records so the customer can build Segments in Mailchimp that replicate their pipeline view. Stage progression logic does not migrate; it is rebuilt manually in Mailchimp Customer Journey Builder.

QuickDesk custom fields on Leads and Contacts migrate to Mailchimp custom merge fields. We extract the field definition (name, type, required flag) from the API and create matching Mailchimp merge fields before importing Member data. Date fields map to Mailchimp Date type; numeric fields to Number type; text fields to Text type. Mailchimp enforces a 255-character limit on text merge fields, so any QuickDesk custom field exceeding this limit is truncated with a warning flag in the migration report.

QuickDesk sales activity records (call logs, tasks, goals) have no structural equivalent in Mailchimp. We extract activity type, date, and outcome where available via the API and apply them as Tags on the Member record (e.g., 'Activity: Call 2024-03-15 Outcome: Interested'). The full activity timeline does not replicate in Mailchimp's interface because Mailchimp is not an activity-tracking CRM.

QuickDesk Customer Experience Automation sequences are proprietary and not exposed via API. We cannot extract automation logic, triggers, or action sequences. We document every automation rule name and trigger condition found in the account during scoping and deliver a rebuild checklist for Mailchimp Customer Journey Builder. The customer recreates each flow manually post-migration.

QuickDesk forecasting calculates pipeline health from stage values and historical close rates. These analytics are derived on read, not stored as records. No forecast data migrates. We recommend exporting any QuickDesk pipeline reports as PDFs before the cutover date. Mailchimp provides campaign-level analytics (opens, clicks, unsubscribes, conversions) but no deal-based forecasting.