Migrate from Aderant Expert Sierra to Mailchimp

Contacts without email addresses cannot become Mailchimp subscribers

Mailchimp's subscriber model requires a valid, deliverable email address for every member. Aderant Expert Sierra contacts without an email on record — such as court contacts, opposing counsel without firm email, or staff records used only for matter routing — must be excluded from the migration. We flag these records during the audit phase and deliver them as a separate reference export. If your firm has a high proportion of contacts missing email, the effective migrated audience size will be lower than the total Expert Sierra contact count, which affects both scope and pricing.

Matter-association tags can exceed Mailchimp's per-subscriber tag density

Mailchimp recommends limiting tags per subscriber to a few hundred for performance reasons, but Aderant Expert Sierra contacts associated with dozens of matters — which is common for senior partners or institutional clients — can generate hundreds of matter tags. We aggregate matter tags by practice area or top-matter only when the per-contact tag count exceeds a threshold you set during planning. This approach preserves segmentation value without hitting Mailchimp's tag density limits or degrading API performance for large audiences.

Client tier and billing rate have no native Mailchimp equivalent

Expert Sierra stores client tier and billing rate as contact or matter properties. Mailchimp has no native fields for these attributes — we create custom merge fields CLIENT_TIER and BILLING_RATE. These merge fields count against Mailchimp's limit of 40 merge fields per audience. If your firm also tracks other custom attributes (billing arrangement type, matter risk level, client since date), we need to prioritize which merge fields to create during planning.

Original contact create date is not preserved as the Mailchimp join date

Mailchimp's subscriber join date (visible in the audience UI) reflects the date the contact was added to Mailchimp — not the date the contact was created in Expert Sierra. We preserve the original create date as a custom merge field ORIGINAL_CREATE_DATE so you can segment by client tenure, but reports showing 'subscriber since' will show the migration date. You need to decide whether to communicate this to your marketing team during training.

Communication preferences and email opt-outs require source-side accuracy

If Expert Sierra's email opt-out flag is not reliably maintained — which is a known issue in practice management systems where billing contacts sometimes receive marketing emails they did not explicitly opt out of — the migrated unsubscribed status in Mailchimp may suppress contacts who should actually receive campaigns. We recommend running a data-quality audit on the opt-out field before migration and flagging any contacts with inconsistent preference settings for manual review before the migration run commits.