Migrate from Lofty to Mailchimp

Lofty leads map directly to Mailchimp subscribers using email address as the unique key. First name, last name, email, phone, and address fields map to Mailchimp's built-in merge fields (FNAME, LNAME, EMAIL, PHONE, ADDRESS). The Lofty lead ID is stored as a custom merge field (LEAD_ID__c) for traceability and delta-run de-duplication.

Lofty contacts and leads both route to Mailchimp subscribers since Mailchimp has no separate contact/lead split. The contact's primary company name is mapped to a MERGECOMPANY merge field. Lofty contact custom fields migrate as Mailchimp merge fields using type-compatible translation.

Lofty companies do not have a direct Mailchimp equivalent. Company name, domain/website, industry, employee count, and annual revenue are mapped as Mailchimp merge fields on each subscriber (e.g., COMPANY_NAME, COMPANY_INDUSTRY, EMPLOYEE_COUNT). For multi-company contacts, the primary company becomes the merge field value; secondary companies are stored as a comma-separated custom merge field.

Lofty deal pipeline stages (e.g., New Lead, Showing Scheduled, Under Contract, Closed) translate to Mailchimp tags applied to the subscriber record. We create a tag group per Lofty pipeline so stage tags are namespaced (e.g., 'Pipeline-Main: Showing Scheduled'). Tags preserve original stage-entry timestamps in a supplemental reference export for reporting continuity.

Lofty deals contain deal name, amount, stage, close date, and owner — these cannot map to a native Mailchimp object because Mailchimp has no opportunity or deal record. Deal data is exported to a CSV reference file so teams can decide whether to recreate deal summaries as Mailchimp merge fields or handle them externally.

Lofty tags used for lead labeling, source tracking, tag-based segmentation, and workflow triggers migrate directly to Mailchimp tags on the matching subscriber record. When a Lofty contact has multiple active tags, each tag becomes a separate Mailchimp tag. Multi-value tags originating from Lofty multi-select custom fields are exploded into individual Mailchimp tags per selected value, preserving the complete choice set on each subscriber.

Lofty segments are defined by filter rules (field + operator + value combinations). We translate Lofty segment rules into Mailchimp segment conditions where the underlying fields have been mapped as merge fields. Static segments (saved contact lists) migrate as Mailchimp static segments. Dynamic segments are noted for rebuild using Mailchimp's segment builder.

Lofty text-type custom fields on leads and contacts map directly to Mailchimp TEXT merge fields, preserving the field values as-is. Field names from Lofty are preserved where possible but shortened to comply with Mailchimp's 30-character merge field name limit when needed. Unicode characters and special characters in both field names and values are sanitized according to Mailchimp's field validation rules to prevent API rejection during the merge field creation phase.

Lofty number, percentage, and currency custom fields map to Mailchimp NUMBER merge fields. Currency symbol is stripped and the numeric value is stored; teams that need currency context can enable a separate TEXT merge field. Percentage fields store the decimal value (e.g., 0.15 for 15%) unless a separate field is created for formatted display.

Lofty date-type custom fields map to Mailchimp DATE merge fields. The date format is normalized to Mailchimp's accepted format (YYYY-MM-DD) during transformation. If Lofty stores datetime with time components, the time portion is preserved in a companion TEXT merge field.

Lofty single-select pick-list fields map to Mailchimp merge field options (radio-button or dropdown style). Each distinct Lofty pick-list value is created as a Mailchimp option. If a Lofty pick-list value does not yet exist in Mailchimp, it is created dynamically before the migration run.

Lofty multi-select fields contain multiple chosen values per record. We explode each selected value into a Mailchimp tag within a tag group named after the original field (e.g., 'Property_Type: Single Family'). This preserves the full choice set per contact unlike a text merge field which could only store a concatenated string.

Lofty activity history (calls, emails, meetings, notes with timestamps and owner attribution) has no Mailchimp equivalent. Campaign-level engagement (opens, clicks, unsubscribes) is tracked natively in Mailchimp but native Lofty activity records do not transfer. Activity data is exported to a structured JSON reference file so teams can preserve it for compliance or rebuild needs.

Lofty attachments on leads and contacts (e.g., property documents, contracts, images) do not migrate to Mailchimp because Mailchimp has no attachment storage on subscriber records. Files are exported individually and the subscriber is notified via a reference manifest listing file names, original record, and a download link.

Lofty lead source data (website form, referral, Zillow, Realtor.com, etc.) maps to a SOURCE merge field on the Mailchimp subscriber. If multiple sources are tracked per contact, they are stored as Mailchimp tags in a 'Lead_Source' tag group. This preserves attribution data for segmentation and campaign targeting in Mailchimp.