Migrate from Actionstep to Mailchimp

Actionstep clients map directly to Mailchimp subscribers. The email address serves as the primary key for this mapping — it is used for de-duplication against existing Mailchimp contacts and is lowercased to generate the Mailchimp subscriber hash (an MD5 hash of the lowercase email). Clients without an email address on record in Actionstep are flagged for manual review before import to avoid creating incomplete subscriber records in Mailchimp. The FlitStack pre-migration audit identifies all contacts missing email addresses and presents them in a separate review queue.

Actionstep stores a client organization name alongside the individual client record. This maps to the COMPANY merge field on the Mailchimp subscriber record. If both individual and company contacts exist for the same party, the individual client record takes priority and company is stored as a merge field.

Actionstep participants are contacts linked to a matter with a role (e.g., Opposing Counsel, Expert Witness, Witness). Each participant role becomes a Mailchimp tag applied to the contact's subscriber record. A contact who is both a client and a participant receives both roles as separate tags.

Matter records do not map to a Mailchimp object. Instead, each matter's name or type becomes a tag applied to all participants and clients linked to that matter. If you need multi-matter segmentation, a Mailchimp segment is created per matter type rather than per individual matter.

Actionstep custom fields defined in the as:client_custom object model are mapped to Mailchimp merge fields. Mailchimp supports up to 40 merge fields per audience. Custom fields with type 'dropdown' or 'radio' map to Mailchimp dropdown merge fields. Date fields, number fields, and phone fields each map to their corresponding Mailchimp merge field types.

If Actionstep tracks contact communication preferences in a custom field, those values are mapped to Mailchimp's member status. Contacts with 'do not contact' flags in Actionstep are imported as unsubscribed (not deleted) so Mailchimp's suppression list is respected and the original flag is preserved as a merge field for reference.

Phone numbers stored on Actionstep clients and participants migrate directly to Mailchimp's PHONE merge field. FlitStack preserves international phone number formatting exactly as it appears in Actionstep — no reformatting or standardization logic is applied during migration. This ensures that phone numbers used for SMS marketing in Mailchimp retain their original format, and contacts can be reached internationally without formatting-related delivery issues. Phone numbers migrate alongside other contact fields in the same batch operation.

Actionstep client and participant addresses (street, city, state/province, postal code, country) map to Mailchimp's compound ADDRESS merge field. The ADDRESS merge field is structured as addr1, addr2, city, state, zip, country — FlitStack splits Actionstep address strings into these sub-fields using standard parsing rules.

Documents attached to Actionstep matters or client records have no equivalent in Mailchimp's schema. Mailchimp stores campaign assets (images, PDFs) in its Content Studio, but these are not contact-linked documents. Documents are excluded from the migration scope and are flagged in the pre-migration audit report.

Financial records in Actionstep — time entries, trust transactions, billing invoices, and trust account balances — have no Mailchimp equivalent. These records are excluded from the migration. A reference export of these records can be provided as a standalone CSV for archival purposes.

Actionstep Builder workflows and matter-step automation rules have no functional equivalent in Mailchimp. These must be reconstructed in Mailchimp's Customer Journey automations. FlitStack can export your Actionstep workflow definitions as a structured document to serve as a rebuild reference for your Mailchimp admin.

Actionstep user accounts and staff records do not map to Mailchimp subscribers — Mailchimp contacts are external parties (clients, participants) not internal team members. If your Actionstep staff are also on your mailing list, they appear as separate subscriber records identified by their personal email addresses.