Migrate from Dibcase Legal Case Management to Mailchimp

SSA case-status fields have no native Mailchimp equivalent and require merge field setup

Dibcase stores SSA case statuses (Initial Claim, ALJ Hearing Scheduled, Fully Favorable, etc.) that have no direct mapping to any Mailchimp native field. Mailchimp allows up to 80 custom merge fields per audience, but the field type options are limited to text, number, date, phone, address, URL, and birthday. SSA status pick-list values must be stored as text merge fields (DIB_SSA_STATUS__c, DIB_CASE_TYPE__c) and your Mailchimp admin needs to decide whether to surface these in segment filters or keep them as reference-only fields in contact profiles. FlitStack creates these fields during migration setup but cannot build Mailchimp automations that act on SSA status — that requires manual rebuild in Mailchimp's Customer Journeys.

Dibcase's N:N contact-to-client model collapses to one Mailchimp contact per email address

Dibcase allows multiple representatives to be associated with the same client case, and contacts can belong to multiple cases simultaneously. Mailchimp stores one contact record per unique email address. When FlitStack encounters duplicate email addresses across Dibcase records, it merges them using a most-recent-wins rule: the most recently updated record's data populates the Mailchimp contact, and secondary associations are preserved in DIB_CASE_ID as a semicolon-delimited list. This means a single attorney with two clients may appear as one Mailchimp contact rather than two — your team should decide whether to deduplicate before migration or accept merged contact profiles.

Mailchimp's free plan caps at 500 contacts — Dibcase tier growth may require plan upgrade

Dibcase pricing limits billable clients per plan tier (51-100, 101-300, 301-500). Mailchimp's free plan also caps at 500 contacts. For firms near the 300-500 client range in Dibcase, the Mailchimp migration will require at minimum an Essentials ($11/mo) or Standard ($20/mo) plan to accommodate the full contact list plus merge field overhead. If your Dibcase list includes inactive and archived records migrated as unsubscribed, those still count toward Mailchimp's contact limit on free and Essentials plans. FlitStack flags all contacts that will exceed the free-plan cap before migration commits so your team can select the appropriate Mailchimp plan.

Document references and SSA ERE tool settings cannot migrate and must be rebuilt

Dibcase's Dropbox-connected file index, SSA ERE tool session settings, and document exhibit references have no Mailchimp equivalent. Mailchimp's content studio supports file uploads for email attachments but does not maintain a document index per contact or case. The DIB_DOC_REFS and DIB_DROPBOX_PATH merge fields FlitStack creates store path references as text only — they are not live links and do not sync. If your intake or nurture workflow relies on sending Dibcase-stored documents via email, that automation must be rebuilt in Mailchimp Customer Journeys, typically by uploading the relevant templates to Mailchimp's content studio and connecting them to the appropriate customer journey trigger.

SMS consent flag requires explicit Mailchimp SMS compliance re-verification

Dibcase tracks SMS consent for client communications, and this flag migrates as DIB_SMS_CONSENT on each contact. However, Mailchimp's SMS marketing is governed by TCPA (for U.S. numbers) and CASL (for Canadian numbers), which require explicit, documented consent that is distinct from Dibcase's internal consent flag. Contacts marked as SMS-consented in Dibcase are not automatically eligible for Mailchimp SMS campaigns. Your team must either run a re-verification campaign in Mailchimp or maintain a separate SMS-eligible segment that is manually curated before activating Mailchimp SMS. FlitStack preserves the Dibcase flag for reference only; it does not constitute TCPA-compliant consent for Mailchimp SMS.