Migrate from Dispatch Pro to Mailchimp

Dispatch Pro customer contacts map 1:1 to Mailchimp Members. The primary email address is the unique identifier in Mailchimp. If a Dispatch Pro contact has no email address, it is flagged as un-importable — Mailchimp requires an email address for every Member record. Multiple Dispatch Pro contacts with the same email address are deduplicated to a single Mailchimp Member.

Dispatch Pro companies do not have a native Mailchimp equivalent — Mailchimp has no Account or Company object. The company name and domain are mapped to COMPANY and COMPANY_DOMAIN merge fields. If a Dispatch Pro contact is associated with multiple companies (N:N), the primary company is mapped as the primary merge field value and secondary companies are appended as tags on the Mailchimp Member.

Dispatch Pro stores customer addresses as structured location records — street, city, state, ZIP, country. Mailchimp supports a structured ADDRESS merge field type that renders correctly in email templates. The mapping preserves the full address string and optionally splits it into individual merge vars (ADDR1, CITY, STATE, ZIP) if the Mailchimp audience has those fields configured.

Every custom property on a Dispatch Pro contact — service-type flags, certification levels, payment-terms labels, referral sources, technician-assignment notes — requires a corresponding merge field in the Mailchimp audience. FlitStack creates these as custom merge fields before the migration run. Text fields are capped at 255 characters in Mailchimp; longer Dispatch Pro text values are truncated and flagged in the pre-migration report.

Dispatch Pro job types (HVAC, plumbing, electrical, roofing, etc.) do not map to any native Mailchimp field. FlitStack creates one Tag per unique job type encountered in the contact's job history and optionally maps the top three job types to Mailchimp Interest Groups if the audience has those groups configured. This allows Mailchimp campaigns to segment by the service categories each customer has historically used.

Individual job records — job number, scheduled date, technician assigned, job status, invoice amount, line items — have no Mailchimp equivalent. Mailchimp Members cannot store structured job-history records. FlitStack exports the complete job history for each contact as a structured JSON file alongside the Mailchimp import. Customers who need job history visible in their CRM use this export to rebuild in a PSA or field-service tool.

Dispatch Pro technicians are employee records, not customer contacts. They do not typically receive marketing emails and should not be imported as Mailchimp Members unless explicitly required. FlitStack flags technician contacts during the pre-migration audit. If technicians are also customers (receiving service at their own address), they are imported as Members with a TECHNICIAN_SOURCE tag to allow segmentation.

Invoice records, payment amounts, and billing history stored in Dispatch Pro have no Mailchimp counterpart. FlitStack preserves invoice summaries (total spend, last invoice date, outstanding balance) as custom merge fields on the Member record if the data is available via the contact object. Full invoice line items are included in the JSON job-history export.

Dispatch Pro stores call logs, notes, and file attachments per customer record. Mailchimp has no native notes or file attachment capability for Members. FlitStack surfaces call counts and note summaries as tags on the Mailchimp Member (e.g., TAG: CalLog_3, TAG: Note_Summary). Attachments are not migrated — they are flagged in the pre-migration audit for manual retrieval from Dispatch Pro before the cutover window.

Dispatch Pro may store marketing consent flags as a custom property on the contact record. Mailchimp requires explicit opt-in for GDPR compliance and uses member status (subscribed, unsubscribed, pending, cleaned) as the gating field. FlitStack maps consent=true to subscribed, consent=false or missing to unsubscribed, and pending double opt-in situations to the pending status with a re-consent campaign recommendation.

Dispatch Pro's internal record ID and original create date are not native Mailchimp fields. FlitStack stores the Dispatch Pro ID as a SOURCE_RECORD_ID merge field and the original create date as a SOURCE_CREATE_DATE merge field — both for traceability and to support delta-run deduplication if the migration is run in multiple phases.

Dispatch Pro stores estimates and quotes linked to contacts and locations. Mailchimp has no deal, opportunity, or quote object. These records are exported as JSON alongside the contact export and are not importable into Mailchimp. Teams that need quote history should migrate to a CRM destination (Salesforce, HubSpot) rather than Mailchimp.