Migrate from Case Status to Mailchimp

Case Status contacts become Mailchimp subscribers in the target audience. Email address is the subscriber key — FlitStack deduplicates by email and maps each contact's name, phone, and address fields to Mailchimp's standard subscriber profile fields. Original Case Status create dates are preserved in a custom datetime merge field.

Case Status text custom properties map to Mailchimp merge fields of type 'text'. Mailchimp enforces a 255-character limit on text merge fields — FlitStack truncates values exceeding this threshold and flags them in the pre-migration diff report so your team can decide whether to split into multiple fields.

Case Status numeric custom properties such as matter value, client ID, or settlement amount are mapped to Mailchimp number‑type merge fields, which impose no character limit. FlitStack creates each merge field with the original Case Status label as its name, ensuring clarity in Mailchimp’s audience builder. Because number fields support range‑based segmentation, you can filter subscribers by value thresholds (e.g., matters over $100 K) in campaign filters.

Date‑typed custom properties in Case Status — such as date opened, next hearing date, or case closure date — are mapped to Mailchimp date merge fields. FlitStack converts all dates to ISO 8601 format so Mailchimp can correctly interpret the values for date‑based automation triggers and segmentation filters. The conversion also validates that dates fall within a plausible range, flagging any malformed entries before import.

Phone number custom properties in Case Status are mapped to Mailchimp phone‑type merge fields. FlitStack strips all non‑numeric characters, re‑formats the numbers to E.164 (e.g., +1‑555‑123‑4567) where feasible, and stores the normalized value. This standardization enables Mailchimp’s SMS add‑on to reliably send text messages, supports phone‑based segmentation, and flags any malformed numbers for your team to correct before import.

Case Status matter records — case number, case stage, opposing counsel, court, filing date, hearing date, case type — have no native equivalent in Mailchimp. FlitStack exports these as a structured CSV keyed by the client email address, so your team can reference the full matter context in Mailchimp by joining on email or rebuilding as a custom CRM integration.

Case Status engagement events (client emails, calls logged, notes) are translated into Mailchimp tags on the subscriber record. For example, a Case Status contact with a logged call becomes a subscriber tagged 'Logged-Call'. Tags enable segmentation in Mailchimp — your team can build segments for 'Clients with open matters' or 'Clients with recent calls' using these derived tags.

Case Status NPS scores and client feedback ratings are migrated to a number‑type merge field (e.g., NPS_SCORE) on each Mailchimp subscriber. FlitStack also preserves the feedback submission date in a companion date merge field, enabling time‑based segmentation. With the numeric score stored, you can create Mailchimp segments for promoters (9‑10), passives (7‑8), and detractors (0‑6), and trigger tailored follow‑up campaigns or referral requests based on the score.

Case Status contacts retain an assigned attorney or owner, which FlitStack translates into Mailchimp tags on each subscriber record (e.g., ‘Attorney: Smith’). Tagging per attorney enables your firm to segment audiences by legal representative, send attorney‑specific newsletters, or trigger drip sequences that deliver content aligned with the assigned attorney’s practice area. Tags also support internal reporting on attorney‑level engagement and help route inbound leads to the correct team member.

Case Status records client portal logins and other engagement events such as opened status updates or document downloads. FlitStack translates each distinct event into a descriptive Mailchimp tag (e.g., ‘Portal‑Login’, ‘Opened‑Status‑Update’). To avoid tag proliferation, FlitStack aggregates repeated events into a single tag per type, preserving a clear engagement history. You can then segment subscribers into active versus inactive cohorts, trigger re‑engagement campaigns for dormant clients, or personalize email content based on past interactions.

Case Status referral source fields (e.g., 'Google Ads', 'Referral', 'Organic Search') migrate to a text merge field. Mailchimp's segmentation by this field lets your firm run source-based nurture campaigns — for example, targeting referral-sourced clients with a different onboarding email than paid-ad leads.

Case Status contacts with an active email subscription flag map to Mailchimp 'subscribed' status. Contacts marked asDo NotContact or with invalid email addresses in Case Status are imported as 'unsubscribed' or 'cleaned' in Mailchimp to protect deliverability metrics from the start.

Firms with multiple offices or practice groups in Case Status can represent this in Mailchimp as a custom merge field ('FIRM_OFFICE') or as an audience-specific tag. FlitStack recommends the merge field approach for single-audience setups and tag-based per-office segmentation for multi-location firms running separate campaigns.

Case Status documents and attachments associated with contacts or matters have no native Mailchimp equivalent. FlitStack exports a document reference CSV (file name, URL, associated contact email) for manual linking. If your firm uses a document management system, this CSV can be used to rebuild links or embed document references in Mailchimp emails.