Migrate from eBrief Ready to Mailchimp

Every Party record in eBrief Ready (barrister, expert witness, client, opposing counsel) becomes a Mailchimp Subscriber in the target audience. Email address is the primary key — contacts without a recorded email address cannot be imported and are flagged for manual review. Each subscriber retains their full eBrief Ready contact field set via Mailchimp merge fields.

eBrief Ready matter identifiers (e.g., MTR-2024-0042) become Mailchimp Tags applied per subscriber. One subscriber can have multiple matter tags when they are a party on multiple matters, mirroring eBrief Ready's N:N party-to-matter model. Tags are used for segmentation so a firm can email all parties on a specific matter or all parties on matters of a given type.

eBrief Ready's party role values (Counsel, Expert Witness, Client, Instructing Solicitor, etc.) have no native Mailchimp equivalent. FlitStack creates a Mailchimp merge field (PARTYROLE) to store the role value per subscriber. Role-based segments in Mailchimp (e.g., all Expert Witnesses across all matters) are then built from this field.

eBrief Ready matter types (litigation, arbitration, mediation, advisory) map to a tag prefix (e.g., Type:Litigation) so matter-type segments are possible in Mailchimp alongside matter-number tags. This allows a firm to broadcast to all litigation-related parties regardless of which specific matter they are attached to.

Organisations stored as party entities in eBrief Ready map to the Mailchimp COMPANY merge field and the optional COMPANY field in the subscriber profile. When a party is an individual, the organisation field captures the firm or chambers they belong to — useful for segmentation by referring firm.

eBrief Ready allows custom properties on party records (e.g., BAR Number, SSC Number, Preferred Chambers). Each custom property becomes a Mailchimp merge field of the matching type (text, number, or date). Boolean and pick-list properties become text merge fields. Merge field setup is delivered as a schema plan before the migration runs.

eBrief Ready records which user created or last modified a party record. Mailchimp has no native owner/tracker field for subscriber records. If firm-specific routing is required (e.g., each partner manages their own client list), FlitStack can model this as an OwnerTag applied per subscriber, but Mailchimp's native access controls are role-based, not owner-based.

eBrief Ready documents (briefs, court books, correspondence, evidence files) and their metadata (OCR text, annotation highlights, page references) have no equivalent in Mailchimp's email-marketing data model. These assets must remain in eBrief Ready or a document management system. FlitStack can provide a manifest of document URLs for reference linking in Mailchimp emails.

eBrief Ready's AI-generated chronology timelines, analysis summaries, and document classification outputs are platform-native constructs with no Mailchimp equivalent. If a firm wants to share chronology summaries via email, FlitStack can export them as PDFs and map them to Mailchimp campaign attachments or external links.

Parties flagged as unsubscribed or do-not-contact in eBrief Ready are exported as a non-subscribed Mailchimp contact list and imported as a suppression list before the main contact migration runs. This prevents accidental outreach to parties who have opted out at the firm level, protecting sender reputation from day one.

The date a matter was opened in eBrief Ready is stored as a custom datetime merge field on each subscriber who is a party on that matter. This preserves matter-age context for reporting and allows segmentation of long-running matter parties for re-engagement campaigns.

eBrief Ready's Pro feature for bulk-editing party records across a matter maps to Mailchimp's tag-management operations. FlitStack applies matter-number tags in batch during migration so Mailchimp reflects the same party groupings that exist in eBrief Ready. The bulk-edit logic translates into batch-tag assignments, preserving role-specific group names where they exist. After migration, a grouping report confirms that each subscriber belongs to the correct matter-level and type-level tag sets.