Migrate from LocaliQ to Mailchimp

LocaliQ Contacts in Dash map directly to Mailchimp subscribers within a single Audience. Email address serves as the primary dedupe key. We preserve standard fields (first name, last name, phone, address) and all Dash custom properties as Mailchimp merge fields or tags depending on field cardinality. Single-value properties become merge fields (FNAME, LNAME, PHONE, ADDRESS); multi-value or classification properties become tags for segment-based targeting.

Dash Leads migrate as subscribers in the same Mailchimp Audience, using email as the dedupe key. The Dash lead score, lifecycle stage, and lead status are preserved as merge fields or tags depending on cardinality. We recommend tagging by lead status (New, Contacted, Qualified, Converted) rather than creating separate audiences per stage, as Mailchimp's multi-list model (being deprecated) favors a single audience with tags and segments for lifecycle separation.

LocaliQ Companies do not map to a native Mailchimp object because Mailchimp has no company/account concept. We extract the company name and any company-level custom properties and map them as subscriber attributes on the linked Contact or Lead record. Company names become a merge field or tag (company_name) so that segmentation by account type, industry, or size is possible in Mailchimp. If the customer maintains multiple contacts per company, tagging by company name groups them for bulk actions.

Dash custom fields map to Mailchimp merge fields. Mailchimp Premium plans support up to 80 fields per Audience; Standard and Essentials tiers have lower limits that we confirm during scoping. We inventory every Dash custom field, classify by data type (text, number, date, boolean, dropdown), and create equivalent Mailchimp field types. Properties that exceed Mailchimp's field limit are handled as tags instead. Dash-specific types like AI lead score (numeric) map to number-type merge fields; AI agent attribution (categorical) maps to tag-based classification.

Dash pipeline stages tracking lead progression (New, Working, Nurturing, Qualified, Closed Won, Closed Lost) do not have a native Mailchimp equivalent. We map each stage to a Mailchimp tag applied to the subscriber record, enabling segment-based filtering by lifecycle stage. Alternatively, we create a dash_pipeline_stage merge field of type dropdown to preserve the original value in a structured format for reporting. The customer chooses tag versus field strategy during scoping based on segmentation needs.

LocaliQ campaign records (across search, social, and display channels) contain budget allocations, status, and targeting parameters. Mailchimp has no campaign metadata object for external advertising data. We extract campaign names and associate them with the contacts who are members of each campaign, tagging each subscriber with the campaign source tag (e.g., campaign_google_search_q1, campaign_facebook_local) so that attribution-based segments can be rebuilt in Mailchimp for email re-engagement of advertising-generated leads.

Dash engagement history (email interactions, call records, meeting logs, task completions) does not have a native Mailchimp activity timeline equivalent. We flag engagement recency using a last_engagement_date merge field and create engagement frequency tags (e.g., highly_engaged, lapsed, new_contact) based on the activity timestamp analysis. This enables Mailchimp segmentation by recency and frequency for re-engagement campaigns. Detailed engagement notes migrate as tags with truncated text if needed for audit purposes.

Dash AI agent configurations (greeting scripts, routing rules, SMS templates, chat flows) are LocaliQ-specific and have no Mailchimp equivalent. Mailchimp does not support voice, SMS, or chat agent functionality natively. We document the existing agent configurations in a written inventory with screenshots and configuration values so the customer can evaluate Mailchimp-compatible alternatives (e.g., ManyChat for chat, SMSBump for SMS) if needed. This is a configuration handoff, not a data migration.

LocaliQ automation sequences and trigger conditions do not migrate to Mailchimp customer journeys because they are structurally different automation models. We deliver a written inventory of every active LocaliQ automation with its trigger event, condition branches, delay steps, and CRM actions. The customer rebuilds equivalent customer journeys in Mailchimp using Mailchimp's visual automation builder. This document is included in the migration deliverables as a rebuild specification.

LocaliQ's directory citation data across 100+ platforms (Google Business Profile, Yelp, Bing, Apple Maps, and others) and review history are tied to the LocaliQ listings infrastructure and cannot transfer to Mailchimp. We export the citation URLs and verification status as a standalone CSV so the customer can manage listings directly in the directories or through a dedicated listings tool post-migration. Review content and response history export as a separate document.