Migrate from Fello to Mailchimp

Fello contacts map 1:1 to Mailchimp audience members. Each contact's email address is the unique key for deduplication during import. First name, last name, email, phone, and address fields map to Mailchimp's built-in subscriber fields. Contacts without an email address are flagged and excluded — Mailchimp requires an email address for audience membership.

Fello's AI lead score (0–100 scale) has no Mailchimp native equivalent. We create a numeric merge field (Fello_Lead_Score) in Mailchimp and import each contact's score as a number value. This field can then drive Mailchimp segment conditions for targeting high-propensity leads in campaigns.

Fello custom fields scoped to real estate (property type, neighborhood, listing stage, estimated home value) require corresponding Mailchimp merge fields. Text fields map to Mailchimp text merge fields. Pick-list values from Fello map to Mailchimp dropdown merge fields with the same option set. Merge field names are truncated to Mailchimp's 30-character limit.

Fello tags migrate as Mailchimp tags with full name preservation. During the CSV import, each contact's tag list is parsed and applied as individual Mailchimp tags. Duplicate tag names are handled automatically — Mailchimp deduplicates tag names at the audience level. The full tag vocabulary is preserved so segmentation logic carries over.

Fello captures TCPA consent timestamps and consent type (call, text, email) as separate fields. These migrate to Mailchimp as a text merge field (TCPA_Consent) storing the consent type and a date merge field (Consent_Date) for the timestamp. Mailchimp does not enforce consent flags — this data is preserved for compliance records.

Fello contacts often associate with a brokerage or company name. Mailchimp has no native company field, so we map this to a text merge field (Brokerage_Name). If the contact's company is used for segmentation, it can be stored as a separate merge field and used to build Mailchimp segments by company name.

Fello's owner ID (agent who owns the contact record) is a foreign key with no Mailchimp equivalent. We preserve it as a text merge field (Fello_Owner_ID) so teams can reference which agent a contact belonged to in Fello. Mailchimp's built-in 'Owner' concept does not map to Fello's agent-owner model.

Fello enriches contacts with estimated home value data from its AI model. This numeric value migrates to a Mailchimp number merge field (Est_Home_Value). Mailchimp supports numeric merge fields for segmentation but not for calculations — the value is stored for targeting use cases like 'contacts in homes valued over $500K.'

Fello Smart Workflows trigger outreach based on lead score changes, listing signals, or agent actions. Mailchimp Customer Journeys have no migration path — these must be designed and built from scratch in Mailchimp's journey builder. We provide a workflow export document detailing each Fello automation's trigger, conditions, and actions for manual rebuild reference.

Fello segments based on lead score thresholds, listing stage, or custom field values translate to Mailchimp segments built from equivalent merge field conditions. Because Mailchimp segments are defined by merge field rules rather than saved lists, we document each Fello segment's criteria so it can be replicated as a Mailchimp segment filter condition.