Migrate from SmartDesk to Mailchimp

SmartDesk Contacts migrate to Mailchimp Audience members as the primary record. First name, last name, email address, phone, and lifecycle stage transfer to Mailchimp standard merge fields. Any SmartDesk custom contact fields migrate as Mailchimp custom merge fields (Fx fields on Standard plans, unlimited on Premium and Enterprise). We handle the unsubscribe status mapping: contacts with SmartDesk unsubscribed or bounced flags are imported to Mailchimp as suppressed contacts rather than active subscribers to protect deliverability.

SmartDesk Accounts do not have a direct Mailchimp equivalent because Mailchimp has no Account or Company object. We merge Account data into the Contact record as tags or groups: the company name becomes a tag (for example, tag=Acme Corp), industry becomes a group within the audience, and employee count is stored as a custom merge field if the Mailchimp plan supports custom fields. This is a deliberate flattening of the data model.

SmartDesk Leads migrate to Mailchimp Audience members with a lead_source tag carrying the original SmartDesk lead source value. Lifecycle stage or lead status from SmartDesk migrates as a tag or custom field. Because Mailchimp has no separate Lead and Contact model, all prospects and leads land in the same audience and are distinguished by tags rather than record type.

SmartDesk Campaigns with campaign name, type, status, start date, and end date map to Mailchimp Campaigns. Campaign type in SmartDesk maps to the corresponding Mailchimp campaign type (regular, automation, or A/B test). Open and click tracking data stored in SmartDesk's email delivery system is not migrated because it lives in the sending layer rather than in SmartDesk's database; historical open and click rates are not available for import into Mailchimp.

SmartDesk Email Templates migrate to Mailchimp Templates as HTML content with merge field placeholders preserved exactly as written. Dynamic content blocks or conditional logic embedded in SmartDesk templates may require manual review post-migration because Mailchimp's template structure uses its own content block model. We flag any template with conditional logic for customer review before upload.

SmartDesk Users map to Mailchimp account users by email address. Only the email marketing user (the person who will manage Mailchimp campaigns) is relevant to the Mailchimp destination; sales reps and help desk users from SmartDesk have no Mailchimp counterpart. We flag any SmartDesk Owner without a matching Mailchimp account user for the customer to provision before migration.

SmartDesk Deals have no Mailchimp equivalent. Deal name, value, stage, expected close date, and owner cannot be stored in Mailchimp's contact-centric data model. We do not migrate Deals as records. Instead, we deliver a written inventory of every active SmartDesk Deal with its value, stage, contact association, and owner so the customer's admin can decide whether to export deal data to a spreadsheet, a dedicated CRM add-on, or rebuild in a downstream CRM platform.

SmartDesk Pipelines and Stages define the sales process and do not exist in Mailchimp. We document every SmartDesk pipeline with its stages, stage probabilities, and the number of Deals in each stage as part of the written inventory delivered to the customer's admin. This inventory serves as the blueprint for any CRM rebuild.

SmartDesk Help Desk Tickets have no Mailchimp equivalent. Ticket subject, status, priority, assignee, and conversation threads cannot be stored in Mailchimp. We deliver a written inventory of all open and recently closed tickets with their linked contact, status, and priority so the customer's admin can plan a helpdesk migration to a dedicated platform if needed.