Migrate from Link app to Mailchimp

Link App contacts map directly to Mailchimp Members. The email address serves as the unique identifier for matching and import. Each contact becomes a subscriber record within the target Mailchimp Audience. Duplicate email addresses are flagged before import to prevent overwrites.

Link App categories (practice area, attorney assignment, case status) become Mailchimp Tags applied to each Member. Multiple tags per contact are supported. Tag names are preserved exactly; Mailchimp's flat tag namespace requires flattening any nested category hierarchies from Link App.

Link App custom fields with short text values (attorney name, matter type, referral source) map to Mailchimp TEXT merge fields. The merge field tag (MERGE0–MERGE15) is assigned based on creation order. Field labels from Link App are stored in a setup reference document.

Mailchimp merge fields are capped at 255 characters. Link App case notes exceeding this limit are truncated to 255 characters and stored in Mailchimp; the full original text is preserved in a CSV reference file linked in a custom field named Case_Notes_Full__c.

Link App's active contacts migrate as Mailchimp 'subscribed'. Archived contacts migrate as 'unsubscribed' unless they have hard bounces on record, which Mailchimp marks as 'cleaned'. Your team decides whether archived clients should receive future campaigns. We recommend documenting this decision in the migration plan to ensure consistent campaign targeting after go-live.

Link App document attachments and secure file links do not have a native Mailchimp equivalent. We create a 'Document_Reference__c' merge field that stores a comma-separated list of document names and their original Link App URLs for manual retrieval after migration.

Link App's threaded secure messages, read receipts, and timestamps have no Mailchimp equivalent. These records are exported as a JSON archive for compliance and reference but do not map to Mailchimp Members or any native object. Client communication history must remain accessible in Link App or an archived export.

Link App case progression workflows and automated client notifications do not transfer to Mailchimp. FlitStack exports your workflow definitions as a rebuild reference document so your team can recreate triggers in Mailchimp Customer Journeys. The data layer migrates; the logic layer requires manual rebuild.

If your firm operates multiple practice areas or offices with separate Link App configurations, each can become a separate Mailchimp Audience. We map the source configuration to target Audiences based on your specification; contacts with matching attributes are assigned to the correct Audience during import.

Link App users and assigned attorneys do not have a direct Mailchimp equivalent. Attorney-to-contact assignments are preserved as a merge field (Attorney_Name__c) on each Member rather than as a Mailchimp user or ownership record. This approach maintains the relationship data within the contact record for segmentation and reporting purposes.

Link App's original contact creation timestamp is preserved as a merge field (Original_Create_Date__c) since Mailchimp sets Member timestamps at import time. This maintains historical context for date-based segmentation and reporting. Preserving the original date also enables retroactive analysis of client acquisition trends and helps in planning re-engagement campaigns.