Migrate from Bidtracer to Mailchimp

Bid and project records have no Mailchimp equivalent and require reference export

Bidtracer stores bid amounts, bid dates, bid statuses, line-item estimating data, and project records as first-class objects. Mailchimp's model supports only subscriber contacts with merge fields. Bid records and project data cannot map to Mailchimp contacts — bid amounts and statuses appear nowhere in the subscriber profile. We export bid and project records as structured CSV files attached to the migration audit log. Your team uses the export to maintain bid context in a spreadsheet or re-import into a CRM if needed later. If bid data is critical for email segmentation (e.g., 'send to all contacts with an active bid'), the CSV export provides the lookup key (contact email) to re-enable that logic.

Mailchimp's 30-merge-field limit per audience constrains Bidtracer custom field migration

Bidtracer supports extensive custom fields per contact object, including construction-specific properties like license numbers, safety training completion, trade certifications, and equipment type. Mailchimp allows a maximum of 30 merge fields per audience. For Bidtracer setups with more than 30 custom contact fields, we prioritize the fields actively used for segmentation and contact qualification, then export the remainder to the reference CSV. We verify the merge field count during the planning phase and surface the constraint before migration. Fields that do not make the cut are preserved in the audit log as a Bidtracer field dump.

Contacts without email addresses are excluded, creating a partial migration gap

Bidtracer contacts that lack a valid email address cannot become Mailchimp subscribers. In construction CRMs, subcontractor contacts, equipment vendor records, and historical leads often have phone numbers or company names without email. These records are excluded from the Mailchimp migration and flagged in the audit log. We provide a separate export of email-less contacts with company name and phone for manual outreach list building or import into a different platform. If your Bidtracer usage depends heavily on contacts without email, the migration coverage will be lower than expected.

Bidtracer activity history (calls, meetings, notes) does not transfer to Mailchimp engagement records

Bidtracer logs activities including calls made, meetings scheduled, and notes attached to contacts. Mailchimp tracks engagement metrics (opens, clicks, unsubscribes) for campaign sends but has no concept of pre-migration activity history. Call logs, meeting records, and note content from Bidtracer cannot appear in a contact's Mailchimp activity feed. If your team uses activity history to personalize outreach (e.g., 'last met on [date]'), that context is lost in the Mailchimp migration. We export activity logs as a CSV reference file; your team rebuilds relationship context manually in Mailchimp based on campaign engagement data going forward.

Bidtracer attachments and bid documents require external hosting after migration

Bidtracer stores bid documents, proposal PDFs, submittals, and plan files attached to bid and project records. Mailchimp's attachment support is limited to images embedded in campaign content — document attachments are not stored on the subscriber record. We download all Bidtracer attachments organized by bid ID and deliver them as a zip archive. To include document references in Mailchimp campaigns, your team uploads files to an external host (Google Drive, Dropbox, SharePoint) and links to them in campaign content. There is no automatic preservation of document access within Mailchimp.