Migrate from Fulcrum Snap to Mailchimp

Fulcrum Snap contact records map directly to Mailchimp members. Each contact exports with name, email, phone, job title, and address. After deduplication by email address, each unique email becomes one member in your Mailchimp audience with all merge field values populated from the source contact properties.

Fulcrum Snap client records hold company name, industry, and billing profile. Mailchimp has no client object — we surface the company name as a merge tag on the member record and use the client billing status as a Mailchimp tag so segments can filter by payment standing without querying a separate system.

Fulcrum Snap assigns contact roles per matter (Attorney, Paralegal, Billing Contact, Client). These roles map to Mailchimp tags applied to each member — a contact who is an Attorney on Matter A and Paralegal on Matter B receives both tags. Tag-based segmentation lets you send matter updates to attorneys and billing communications to the billing contact.

Fulcrum Snap custom fields like client_id, matter_number, and bar_number hold legal-specific identifiers that have no native Mailchimp equivalent. We create a matching merge tag for each custom field, preserving the original Fulcrum Snap value so your Mailchimp audience retains the source system identifier for reconciliation.

Matter records in Fulcrum Snap hold time entries, invoices, and billing data that cannot map to Mailchimp's campaign-centric data model. We extract matter type and matter status as tags and merge tags respectively, providing a reference label for segmentation without attempting to store billing or time data in an email marketing platform.

Fulcrum Snap stores structured addresses (street, city, state, ZIP, country) on contact records. Mailchimp's built-in address merge fields accept structured address data, enabling segment filters by city or state without custom field configuration. We map each address component to its corresponding Mailchimp field.

Fulcrum Snap records email marketing opt-in preferences that may differ from Mailchimp's subscribed/unsubscribed states. We apply a value mapping: opted-in contacts import as Subscribed, opted-out contacts import as Unsubscribed, and contacts with no explicit preference import as Pending so you can re-confirm before sending.

Fulcrum Snap attachments (contracts, invoices, court filings) attached to contact or matter records have no Mailchimp equivalent and are excluded from migration. If attachments are relevant for email campaigns, we recommend linking to a document management system or SharePoint rather than attaching large files through Mailchimp.

Fulcrum Snap apps define custom properties per form (e.g., EPL filings, IP docketing, client intake). Each custom property in Fulcrum Snap becomes a dedicated merge tag in Mailchimp, preserving the full property set on the member record even though the form logic that populated those properties no longer applies.

Fulcrum Snap tracks which user created or owns a contact record. Mailchimp has no native owner field. We capture the Fulcrum Snap owner name as a merge tag on the member record so you can identify which team member originally created each contact without needing a CRM-level owner assignment.