Migrate from BoomTown to Mailchimp

BoomTown contacts migrate as Mailchimp audience members, with each contact’s email address serving as the primary key for the subscriber record. All standard fields such as name, phone, and address are mapped to Mailchimp’s built‑in merge fields, while BoomTown owner email is stored as a custom merge field for campaign attribution. Any duplicate email addresses detected during migration are flagged for review before final audience creation, ensuring a clean subscriber list.

BoomTown custom properties on contacts map to Mailchimp merge fields such as FNAME, LNAME, PHONE, and any custom fields you have defined (for example, source, lead score, or lifecycle stage). Each property’s data type is validated and transformed to Mailchimp’s supported types — dates become date fields, numbers stay numeric, and text remains text. Pick‑list values are converted to Mailchimp tag criteria, preserving the categorical information for segmentation.

BoomTown company records have no direct Mailchimp equivalent, so the primary company name for each contact is migrated as a COMPANY_NAME merge field on the contact record. Secondary company associations or parent‑child relationships are stored as tags on the contact, allowing you to filter by company affiliation. Any company‑only records that have no associated contacts are exported as a separate reference file for downstream handling.

BoomTown deals, transaction amounts, close dates, and pipeline stages have no Mailchimp object, so this data is exported as a structured CSV reference file. The export includes the deal name, amount, close date, pipeline stage, and the associated contact email as a join key, allowing your team to rebuild a sidecar pipeline tracker in a spreadsheet or integrate the data into a third‑party pipeline tool after migration.

BoomTown labels and tags applied to contacts are migrated as Mailchimp tags on each corresponding audience member, preserving the original categorization logic. These tags drive segmentation filters and automation triggers in Mailchimp Customer Journeys, enabling you to recreate lead‑routing logic based on the tags you already use. If a contact has multiple tags, all are transferred; duplicate tags are merged automatically to avoid redundant entries.

BoomTown lead stages (new lead, contacted, shown, under contract, closed) become Mailchimp tags or segment filter values, each applied as a tag on the contact. This lets you build Mailchimp segments targeting contacts at specific pipeline positions, such as all contacts in the ‘under contract’ stage for a closing reminder. The final stage at migration is applied; stage history is not retained, but an audit log records the mapping.

BoomTown drip campaigns and automated email sequences have no direct Mailchimp equivalent and must be rebuilt in Mailchimp’s Customer Journey builder. FlitStack exports your BoomTown campaign definitions—including trigger conditions, step timing, email content references, and audience criteria—as a structured reference document. Your Mailchimp admin can use this document to recreate each workflow step by step, preserving the original logic while adapting it to Mailchimp’s trigger model.

BoomTown activity history—including logged calls, emails, tasks, and meeting notes—does not map to Mailchimp because Mailchimp records only campaign engagement (opens, clicks, unsubscribes). To preserve this information, FlitStack exports the activity logs as a reference CSV that includes the contact email, activity type, date, duration, and notes. This file supports compliance reviews and audit trails, and it can be imported into a separate task‑management system if needed.

BoomTown lead scores are migrated as a LEAD_SCORE custom merge field, preserving the original value from BoomTown. If you prefer tag‑based segmentation, FlitStack can convert the scores into categorical tags (Hot Lead, Warm Lead, Cold Lead) based on thresholds you define. Because Mailchimp lacks native scoring, your team decides how to use the LEAD_SCORE value in segments, such as targeting contacts with scores above a set threshold for priority nurture sequences.

BoomTown owner assignments are resolved to the user’s email address and stored as an OWNER_EMAIL custom merge field on each contact record. Mailchimp does not have a native user‑assignment model, but the OWNER_EMAIL field can be used to segment contacts by assigned owner, to trigger owner‑specific automations, or to sync with a separate CRM that handles user management. This allows your team to maintain owner‑based workflows even after the migration.