Migrate from Lawcus to Mailchimp

Lawcus contacts map directly to Mailchimp audience members. Each contact's email address becomes the subscriber key. First name, last name, phone, and address fields translate to Mailchimp default merge fields (FNAME, LNAME, PHONE, ADDRESS). Contacts without a phone or address still migrate, leaving those merge fields blank. All tags attached to a contact are also transferred as Mailchimp subscriber tags, enabling immediate segmentation.

Mailchimp has no Company object — Lawcus company name, industry, and website are stored as custom merge fields (COMPANY_NAME, COMPANY_INDUSTRY, COMPANY_WEBSITE) on each audience member linked to that company. If a contact has no associated company, the merge fields remain empty. The company hierarchy (parent/child) is flattened into a single text field for each contact.

Lawcus matters represent legal cases with billing, documents, and court dates. Mailchimp cannot represent legal case data. We preserve the matter name and matter ID as a Mailchimp tag (e.g., 'Matter: Smith-v-Jones-1234') and surface matter reference data in a supplemental CSV for manual annotation.

Lawcus leads with a valid email address migrate as Mailchimp audience members tagged with 'Source: Lead'. Unconverted leads from Lawcus are flagged so you can suppress them from active Mailchimp campaigns if needed. Leads without an email address are exported to a separate CSV for manual review, as Mailchimp requires a valid email for subscriber status.

Lawcus custom fields on contacts (e.g., practice_area, referral_source, bar_number) become Mailchimp merge fields. Field types map: text to text, picklist to radio/select merge field, date to date merge field. Merge field names are uppercase and alphanumeric. Fields exceeding 255 characters are flagged for truncation or split into multiple merge fields to preserve data integrity.

Lawcus contact tags migrate 1:1 to Mailchimp tags. Tags preserve categorization logic from Lawcus — for example, 'Corporate', 'Family Law', 'Estate Planning' become Mailchimp tags used for audience segmentation. If duplicate tags exist across contacts, they remain distinct per subscriber, allowing fine-grained filtering in Mailchimp campaigns.

Lawcus lead source values (referral, website, directory) map to a Mailchimp merge field (LEAD_SOURCE) with defined options. These values also populate as tags so segments can filter by lead origin without requiring a custom merge field. If new lead sources appear in Lawcus after migration, they can be added to the merge field options manually in Mailchimp.

Lawcus activity records (calls logged, emails sent, meetings scheduled) have no Mailchimp equivalent. Mailchimp tracks opens, clicks, and unsubscribes — not pre-existing client interaction history. We export a JSON activity log for reference but it does not populate Mailchimp records.

Lawcus workflows with stages and triggers cannot migrate. We export the workflow definition (stages, conditions, actions) as a JSON specification that maps to Mailchimp Customer Journeys triggers, so your team can rebuild the logic in Mailchimp's automation builder. This JSON includes step names, conditional branches, and expected time delays, providing a clear blueprint for recreating each workflow in Mailchimp Customer Journeys.

Lawcus user assignments (which attorney or staff owns a contact or matter) do not translate to Mailchimp, which has no per-record ownership model. We preserve the original Lawcus user name as a merge field (ORIGINAL_OWNER) for reference. This allows you to filter contacts by original owner for internal reporting.

Lawcus documents attached to contacts or matters cannot migrate to Mailchimp. Documents remain in Lawcus or your document management system. We flag records with attachments in the migration report for manual follow-up. If you need document access from Mailchimp, consider linking to a shared drive via a custom field URL.

Lawcus invoices and billing records are financial documents with no Mailchimp equivalent. These remain in Lawcus for accounting purposes. If you need billing history visible to clients, that requires a client portal integration separate from the Mailchimp migration. Your accounting team can continue using Lawcus for invoicing without interruption.