Migrate from BoldTrail to Mailchimp

BoldTrail Contact maps 1:1 to Mailchimp Subscriber. Email address is the primary key on both platforms and maps directly. First name, last name, phone, and address fields map to Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS). BoldTrail contact status (active/inactive) determines Mailchimp subscriber status on import.

Mailchimp has no native company object. BoldTrail Company data merges onto the primary contact record: company name stores in the COMPANY merge field, industry stores as an industry tag, and company phone stores in a custom merge field. Only the primary company per BoldTrail contact migrates to avoid duplicate contact records.

BoldTrail Deal records do not have a direct Mailchimp equivalent. The deal maps as a series of tags on the associated contact record: deal_stage tag (e.g., 'Lead—Inquire­d', 'Showing—Scheduled', 'Offer—Submitted', 'Closed—Sold'), property_address tag for the listing, and sale_price stored in a custom merge field on the contact. Multiple deals per contact become multiple tags.

BoldTrail Listing data (property address, MLS number, listing status, listing price) migrates as tags on the buyer or seller contact. Listing status ('Active', 'Pending', 'Sold') becomes a tag so Mailchimp segments can filter contacts by current property status. Listing address stored as a tag for geographic segmentation in Mailchimp campaigns.

BoldTrail Smart Campaigns and automated sequences cannot migrate to Mailchimp Customer Journeys — the trigger models, event types, and action sequences are architecturally different. FlitStack exports the BoldTrail campaign names, sequence step names, and tag memberships as a rebuild reference document your team uses to reconstruct flows in Mailchimp's Customer Journey builder.

BoldTrail custom properties on contacts without a direct Mailchimp merge field equivalent (e.g., buyer_timeline, preferred_area, agent_referral_source) require a Mailchimp merge field to be created before migration. FlitStack creates the merge field in Mailchimp during the pre-migration setup phase, matching the BoldTrail field type (text, number, date, or pick-list) to the nearest Mailchimp merge field type.

BoldTrail lead status values (New, Contacted, Qualified, etc.) map to Mailchimp tags with the prefix 'LeadStatus:' so segments can filter by original BoldTrail lead status. The mapping preserves the exact BoldTrail pick-list values as tag labels — no data is lost, and Mailchimp segments can reconstruct the equivalent of BoldTrail's lead pipeline view.

BoldTrail Owner (agent) data stores as a tag on each contact: 'Agent:{firstname_lastname}' or 'Owner:{owner_id}'. This preserves the assignment relationship without requiring Mailchimp user management (which Mailchimp does not expose at the contact level). Agent-based segments can be built in Mailchimp by filtering on the owner tag.

BoldTrail activity history (logged calls, emails, meetings, notes attached to a contact) does not have a native Mailchimp equivalent. FlitStack preserves the last 10 most-recent activity entries as a tag set on the contact (e.g., 'LastActivity:Call—2025-11-15') and the full activity log as a custom note attachment exported alongside the contact record. This is reference data, not usable for Mailchimp automations.

BoldTrail unsubscribes and hard bounces export as a suppression list and import directly into Mailchimp's suppression management. This ensures Mailchimp does not re-solicit contacts who have already opted out in BoldTrail, protecting deliverability and sender reputation from day one of the new Mailchimp account.

BoldTrail tags applied to contacts (e.g., 'hot_lead', 'investor', 'fsbo_referral') map 1:1 to Mailchimp tags. If the same tag exists in BoldTrail and Mailchimp the merge is direct; new tags are created on the fly during migration. Tag count is preserved exactly so existing Mailchimp segment definitions can be rebuilt from the same tag vocabulary.