Migrate from Jubilee to Mailchimp

Subscription status requires compliance mapping before import

Jubilee tracks opt-in preferences in a contact field that may not distinguish between 'never consented' and 'withdrew consent.' Mailchimp enforces strict subscriber status rules — importing contacts with an active status when they have no recorded consent creates a compliance risk under CAN-SPAM and GDPR. FlitStack flags any contact record where consent history is ambiguous and routes those to unsubscribed or pending status by default, with an option to apply double opt-in during import. The client team reviews flagged records before the migration commits.

Matter and case identifiers have no native Mailchimp field

Jubilee stores matters and cases as separate objects linked to contacts. Mailchimp subscribers have no concept of a case reference. Migrating matter numbers requires custom merge fields (MATTER_REF__c) — each contact gets the matter ID stored as text. If a single Jubilee contact has multiple active matters, those matter IDs must be applied as tags, because Mailchimp does not support multi-value custom fields. We surface the many-to-many contact-to-matter structure in the pre-migration plan and let your team decide whether to store the primary matter or all matters on each subscriber record.

Invalid email addresses will bounce at import and damage deliverability

Jubilee contact records frequently contain formatting errors, role-based addresses (info@, admin@), or outdated domains — especially in older practice-management data. Mailchimp counts bounces against deliverability reputation. We run an email-validation pass before import: malformed addresses are flagged in the migration report, role-based addresses are flagged with a recommendation to use a personal contact address, and hard-bounce domains are excluded from the initial import batch. Soft bounces are retried after domain authentication is confirmed.

Jubilee workflows and billing alerts cannot migrate to Mailchimp

Jubilee automations — client intake confirmations, billing reminders, court-deadline alerts, document-request sequences — are practice-management logic built in Jubilee's workflow engine. Mailchimp's Automation Flows use an entirely different trigger-and-action model. There is no direct translation. We export your Jubilee workflow definitions as a structured reference document that your Mailchimp admin can use to rebuild equivalent automations. The rebuild is a separate project and is not included in the FlitStack migration scope.

Document attachments and billing ledgers are out of scope

Client documents, court filings, and billing ledger entries stored in Jubilee have no equivalent in Mailchimp's object model. Mailchimp supports file attachments in campaigns, but those are campaign assets, not client record attachments. We do not export document blobs from Jubilee. The practice-management data (invoices, time entries, court deadlines) stays in Jubilee. If you need those linked to contacts in Mailchimp, the only option is to store file URLs in a custom merge field if the documents are hosted elsewhere — we can include that step if your team provides the hosting.