Migrate from BackDocket to Mailchimp

Mailchimp has no native case or company object — case data requires Merge Field setup before migration

Mailchimp's data model is contact-centric: an audience is a flat list of subscribers with merge fields attached. Backdocket's Case records have no direct Mailchimp destination — there is no Case, Matter, or Attorney object in Mailchimp. Every piece of case metadata (practice area, court name, assigned attorney, case status) must be pre-created as a Merge Field in your Mailchimp audience before the migration loads data. If your firm uses more than a handful of Backdocket custom fields, this pre-creation step can extend your migration prep window by a day or two. FlitStack delivers a Merge Field creation checklist based on your Backdocket field inventory so nothing is missed before the import runs.

Backdocket suppression data (unsubscribed contacts) must be handled separately to protect deliverability

Mailchimp's deliverability depends on maintaining a clean suppression list — contacts who unsubscribed in Backdocket must be imported as suppressed contacts in Mailchimp before the active audience loads, or the migration risks triggering bounces that damage your sender reputation. Backdocket does not expose a per-contact unsubscribe flag in its standard export — unsubscribes may need to be sourced from Backdocket's activity log or the connected Mailchimp integration's sync history. FlitStack identifies unsubscribed contacts from available Backdocket data, formats them as a Mailchimp suppression list import, and runs that import before the active contact migration so Mailchimp respects opt-out status from go-live.

Backdocket contact roles map to Mailchimp Tags, which are not equivalent — segmentation logic must be rebuilt

Backdocket supports structured contact roles: Attorney, Client, Opposing Counsel, Witness, Vendor, and more, with the ability to associate a contact with a Case under a specific role. Mailchimp has no role concept at the contact level — roles are represented as Tags. This means 'Attorney John Smith on Case 1234' and 'Client Jane Doe on Case 1234' both get a Tag, but the tagging model loses the Case-to-role linkage Backdocket preserves. If your firm relies on Backdocket role data to drive segmented sends (e.g., 'send only to Opposing Counsel on active cases'), that segmentation logic must be rebuilt in Mailchimp using Merge Fields (PRACTICE_AREA, CASE_STATUS) rather than Tags alone.

Mailchimp's per-contact pricing means migrated Backdocket contacts may change your Mailchimp billing tier

Mailchimp charges by the total number of contacts in an audience, not by active campaigns sent. Backdocket contact lists can grow large as a firm accumulates leads, former clients, and referral contacts. Migrating a large Backdocket contact list into Mailchimp can push a firm from a lower Mailchimp pricing tier (e.g., Essentials) into a higher one (Standard or Premium), where monthly costs increase significantly. We surface the total contact count from Backdocket before migration and provide an estimate of the resulting Mailchimp plan tier so your finance team can anticipate the billing impact before migration commits.

Backdocket workflows, task sequences, and document attachments do not migrate and require manual rebuild

Backdocket's workflow engine automates legal process steps — task assignments, deadline reminders, approval chains, and document generation triggers. Mailchimp's automation builder handles email sequences (welcome emails, birthday automations, re-engagement campaigns) — a fundamentally different automation model with no structural equivalence to Backdocket's task-based workflows. Documents stored in Backdocket (court filings, executed contracts, client intake forms) have no Mailchimp equivalent and are not migrated. FlitStack exports Backdocket workflow definitions and document metadata as reference files, but the rebuild work — designing Mailchimp email automations and establishing a document storage solution — falls to your team.