Migrate from Ascora to Mailchimp

Ascora Customer records map to Mailchimp subscribers when an email address is present. Customers without an email address are flagged for review — the contact cannot exist in Mailchimp without one. We preserve the original Customer create date as a custom merge field.

FlitStack AI maps Ascora Contact objects—individuals linked to a Customer—to Mailchimp subscribers when an email address is present. When a Customer holds multiple Contacts, each Contact with a distinct email is created as its own Mailchimp subscriber, preserving first name, last name, and custom field values. If two Contacts share the same email, FlitStack AI collapses them into a single subscriber record, merging name details and retaining all associated tags.

Ascora custom fields on Customer records map to Mailchimp merge fields. Mailchimp supports up to 40 merge fields per audience with type constraints — text, number, date, address, phone, or birthday. We validate Ascora field types against these constraints and surface any incompatible mappings before migration.

Ascora Customer site addresses (street, city, state, postal code, country) map to Mailchimp's structured ADDRESS merge field type. Multi-site customers require a decision rule — we migrate the primary site address and store additional sites as a text merge field for reference.

FlitStack AI extracts phone numbers from Ascora Customer or Contact records and writes them to the Mailchimp PHONE merge field without transformation. The value is stored as a string, using international format (e.g., +1‑555‑123‑4567) when available, ensuring compatibility with Mailchimp's phone‑number handling. If a record contains multiple phone numbers, the primary or first listed number is used; any additional numbers are optionally saved as a text merge field for reference.

FlitStack AI exports Ascora Job records (work orders, service tickets) as a structured CSV archive because there is no corresponding Mailchimp object. The export includes job ID, linked customer reference, current status, scheduled and completed dates, and technician assignment details. This archive preserves the full job history for record‑keeping and can be used to rebuild job‑related email triggers in Mailchimp if needed.

FlitStack AI exports both Ascora Quote and Estimate records as a separate CSV because there is no equivalent Mailchimp object. The export captures quote ID, linked customer reference, line‑item details, total amount, and current status. This archive is provided alongside the Mailchimp subscriber migration, giving your team a complete record of sales proposals for future reference or for rebuilding quote‑related email sequences in Mailchimp.

FlitStack AI exports Ascora Invoice records to a CSV file containing invoice ID, linked customer reference, total amount, invoice status (open, paid, overdue), and payment date. Because Mailchimp lacks any invoice or financial transaction object, the export preserves the full billing history for accounting continuity. This CSV archive is delivered alongside the Mailchimp subscriber migration, enabling your finance team to reconcile past payments or to reconstruct invoice‑related email notifications in Mailchimp if desired.

Tags applied to Ascora Customer or Contact records migrate to Mailchimp Tags on the corresponding subscriber. Tags are created automatically in Mailchimp if they do not exist. This preserves any segment logic your team built in Ascora for tagging repeat customers or service types.

Ascora owner and technician user records have no Mailchimp equivalent. User data is exported in the archive but does not become a Mailchimp object. Owner names are optionally preserved as a text merge field on the subscriber record for reference.

FlitStack AI reads Ascora's industry or trade‑type properties (such as HVAC, Plumbing, Electrical) and maps each distinct value to a Mailchimp Tag on the subscriber record. These tags can be used directly for audience segmentation or to construct Mailchimp Segment filters that target specific trades. This approach supports targeted email campaigns, such as seasonal maintenance reminders or service promotions, leveraging the trade classification already captured in Ascora.

FlitStack AI copies the Notes text from Ascora Customer records into the Notes field of the corresponding Mailchimp subscriber profile. The text is transferred as plain, unformatted content, preserving the full note even if it exceeds typical field lengths. Mailchimp displays these notes to any account user with audience access, but they do not support rich formatting, bullet points, or threaded replies, so they serve as a simple reference log.