Migrate from Q Dispatch to Mailchimp

Q Dispatch job and work-order data cannot be stored as records in Mailchimp

Mailchimp has no work-order or job object. Q Dispatch work orders, job statuses, technician assignments, parts used, and scheduling information are outside Mailchimp's contact model. FlitStack preserves job history by tagging Q Dispatch customers with job-type labels (e.g., HVAC-Repair, Plumbing-Emergency) so the marketing team can segment by service category — but the detailed job record itself (technician, parts, notes) does not transfer. Your team should plan for this limitation: if job history detail is needed for marketing (e.g., send a campaign to customers whose last job was more than 12 months ago), you need to decide how to surface that from Q Dispatch post-migration.

Email opt-in and consent status requires pre-migration verification

Q Dispatch is a dispatch and field service tool — it was not designed to manage email marketing consent. If your Q Dispatch customer records include an email address but no explicit marketing opt-in flag, Mailchimp will import those contacts as subscribed by default. Sending campaigns to unsubscribed contacts creates CAN-SPAM and GDPR compliance risk. We flag contacts without a consent record and import them with a status that requires your team to either suppress them or obtain re-consent before sending. This step is the customer's responsibility, but FlitStack surfaces the list of at-risk contacts before migration commits.

Mailchimp merge fields have a 30-character name limit and require pre-creation

Mailchimp's merge field API enforces a 30-character maximum on merge field tags (the internal identifier used in templates and segments). Q Dispatch custom field names often exceed this. FlitStack truncates and sanitizes field names during mapping, but if two Q Dispatch custom fields would produce the same 30-character Mailchimp tag after truncation, they create a collision. We flag collisions before migration and require your team to rename Mailchimp fields or accept the mapping as-is. Mailchimp also requires custom fields to exist before import — we create them via the Mailchimp API before data loads, but the field type (text, number, date, dropdown) must be correct or data will be rejected.

Q Dispatch contact-to-address relationships are flat; Mailchimp address fields are structured

Q Dispatch may store customer addresses as a text field or a structured address object. Mailchimp uses five structured address merge fields (ADDR1, CITY, STATE, ZIP, COUNTRY). If Q Dispatch stores address as a single text blob, FlitStack attempts to parse it using common US address patterns — success rate depends on address formatting consistency. Addresses that fail parsing are imported with the raw value in ADDR1 and a flag for manual correction. Multi-line addresses or addresses outside standard US formats are the highest-risk cases for parsing failures.

Mailchimp pricing is audience-size based; large Q Dispatch customer lists may push plan tiers

Q Dispatch customer lists grow with your service business. If your Q Dispatch account contains 15,000 customer contacts and you migrate them to Mailchimp, you need a Mailchimp plan that covers 15,000 contacts. Mailchimp's Essentials plan starts at approximately $13/month for 500 contacts and scales in tiers — the pricing jump from 10,000 to 15,000 contacts can be significant on Standard and Premium plans. FlitStack includes the contact count in the migration scope document so your team can verify the target Mailchimp plan before migration commits.