Migrate from BoldTrail BackOffice to Mailchimp

BoldTrail contact records map directly to Mailchimp subscribers within an Audience. The contact's email address becomes the primary subscriber identifier; all other properties transform into corresponding merge fields. Inactive or archived BoldTrail contacts can be optionally suppressed during migration rather than imported as unsubscribed records into Mailchimp.

BoldTrail contacts flagged as agents — including brokerage staff, realtors, team leads, and administrative personnel — map to Mailchimp subscribers tagged with 'Agent' or a custom brokerage-defined label. Tags preserve the agent classification identity without requiring a separate custom field in Mailchimp, allowing immediate segmentation of agent contacts.

BoldTrail contacts identified as buyers, sellers, tenants, or other non-agent roles become Mailchimp subscribers tagged with 'Client' or a more granular role-specific tag. The tag structure enables segmenting clients separately from agents for targeted campaign outreach, drip sequences, and property-specific communication automations in Mailchimp.

BoldTrail company records associated with contacts merge into contact-level merge fields on the subscriber record. Company name, website URL, industry classification, and address information append to the contact record as merge fields rather than creating a separate company object, since Mailchimp has no native company entity or relationship model.

BoldTrail transaction records associated with a contact aggregate into merge fields on the subscriber record. Transaction type, closing amount, close date, transaction status, and referral source store as custom merge fields for audience segmentation, but they do not create separate transaction objects in Mailchimp's data model.

BoldTrail agent license numbers have no native Mailchimp equivalent field type. A custom merge field named LICENSENUM creates on the target Audience, and each agent's license number value migrates per subscriber record. The Mailchimp merge field type is set to TEXT to accommodate alphanumeric license formats across different state licensing boards.

BoldTrail commission plan associations and plan names map to a custom merge field (COMMPLAN) for reference and reporting purposes in Mailchimp. However, the underlying commission plan logic, split calculation rules, tier structures, and disbursement triggers do not migrate — the plan name is stored as informational metadata only in Mailchimp.

BoldTrail's original createdate timestamp is preserved as a custom merge field (ORIGCRTDT) in Mailchimp because Mailchimp's native subscriber timestamp reflects the import date, not the original BoldTrail record creation date. This preservation maintains historical continuity for reporting, attribution analysis, and contact lifecycle tracking across both platforms.

The BoldTrail internal contact ID stores as a custom merge field (BTRAILID) for traceability, delta-run deduplication, and reconciliation against the source system during ongoing sync operations. Both Mailchimp subscriber IDs and the original BoldTrail contact IDs persist in the record for audit trail purposes, rollback operations, and cross-referencing between platforms.

BoldTrail contact tags, role labels, and custom classifications apply directly as Mailchimp Tags on the corresponding subscriber record. Tags transfer as-is from BoldTrail; however, the tag taxonomy structure in Mailchimp may require manual consolidation or renaming if BoldTrail uses a significantly different labeling schema or hierarchy.

BoldTrail transaction pipelines, commission automation workflows, and multi-step business process flows have no direct Mailchimp equivalent in Customer Journeys. FlitStack exports complete workflow definitions, step sequences, condition logic, and action triggers as a structured JSON reference file for your team to manually rebuild in Mailchimp's Customer Journeys automation builder.

BoldTrail commission calculation rules, split schedules, tiered commission structures, and disbursement triggers are inherently real estate-specific and do not map to any Mailchimp feature or merge field logic. These commission parameters must be documented separately and manually rebuilt within your commission management system if automated commission communication workflows are needed.