Migrate from RunSensible to Mailchimp

RunSensible contact records map 1:1 to Mailchimp subscribers within a target Audience. The contact's primary email address becomes the subscriber's email address. RunSensible archived contacts map to Mailchimp unsubscribed status if suppressed, or to a separate import batch for review.

RunSensible contacts linked to specific Matter records are tagged in Mailchimp with the Matter name or case number as a Tag. This preserves the relationship between a subscriber and their associated legal matter without requiring a custom junction object in Mailchimp.

RunSensible company records do not map to a discrete Mailchimp object. Instead, each contact's primary company name is stored in a custom merge field (COMPANY) on the subscriber record. Additional company affiliations are applied as Tags (e.g., 'Secondary Client: Acme Corp') to preserve N:N relationships.

Mailchimp has no native Matter or case object. Matter names, case numbers, and matter status are preserved as Tags on each subscriber who is a party to that matter. Matter status (Open, Pending, Closed) can also be stored as a custom merge field (MATTER_STATUS) for filtering in Mailchimp segments.

RunSensible billing contacts who may not be primary matter contacts are merged into the same Mailchimp Audience. A 'Billing Contact' Tag is applied to distinguish these records from matter-party contacts without creating a separate Audience, since Mailchimp charges per contact regardless of Audience membership.

RunSensible custom contact properties (e.g., referral source, preferred contact method, bar number) map to Mailchimp custom merge fields. Mailchimp Standard and Premium plans allow multiple custom merge fields; Free and Essentials plans have lower limits. We flag any custom fields exceeding plan limits before migration.

RunSensible company custom properties such as industry classification, firm size, or annual revenue do not map to any Mailchimp object. Instead, these company-level custom fields are propagated as merge fields on each related contact's subscriber record in Mailchimp. If a contact is associated with multiple RunSensible companies, the primary company's custom field values take precedence for migration, and secondary company custom fields are flagged for manual review.

RunSensible contact address fields including street address, city, state, postal code, and country map to Mailchimp's structured ADDRESS merge field component. This mapping enables Mailchimp's postal mail integration features and supports address-based audience segmentation if your Mailchimp plan includes those capabilities. The full address is stored in a single ADDRESS merge field with structured subcomponents.

RunSensible contact phone numbers migrate to Mailchimp's PHONE merge field. This enables SMS marketing features in Mailchimp Standard and Premium plans. SMS consent flags from RunSensible cannot be automatically preserved — your team should configure Mailchimp's SMS opt-in within each subscriber's profile after migration.

RunSensible email logs and communication history attached to contacts have no Mailchimp equivalent. Mailchimp generates its own engagement tracking including opens, clicks, and bounces from campaigns sent after migration. Historical communication logs and email threads do not transfer to Mailchimp. FlitStack flags this data gap in the pre-migration disclosure report so your team is aware that all prior client communication history will remain accessible only in RunSensible.

RunSensible document storage including court forms, client files, and signed agreements does not map to Mailchimp. Mailchimp supports file attachments in campaigns but does not function as a document management system. Documents must remain in RunSensible or be migrated to a separate document storage platform such as Google Drive, Dropbox, or a dedicated legal document management system.

RunSensible's IOLTA trust accounting and billing records are practice management data with no Mailchimp counterpart. Billing history, outstanding invoices, and trust account balances do not migrate. If you need to communicate billing status to clients via email, this must be managed as a manual or Zapier-integrated process post-migration.

RunSensible staff user accounts including attorneys, paralegals, and billing administrators do not map to Mailchimp subscriber records. These are internal system accounts for platform access, not client contact records. Staff members who also receive firm communications as clients should be imported separately as contacts, distinct from their staff login accounts. This ensures staff credentials and client communication preferences remain properly segregated in Mailchimp.

RunSensible workflow triggers and email automation sequences have no structural equivalent in Mailchimp. Client onboarding sequences, matter-status email alerts, and billing notification automations must be redesigned as Mailchimp Customer Journeys. FlitStack exports RunSensible workflow definitions as a reference document for your Mailchimp admin.