Migrate from BlinQ to Mailchimp

Blinq contact records map directly to Mailchimp subscribers by email address as the primary key. The Blinq contact's name, email, phone, and company fields map to the standard Mailchimp EMAIL, FNAME, LNAME, PHONE, and COMPANY merge fields. If a Blinq contact lacks an email address it is flagged and excluded — Mailchimp requires a valid email for subscriber records.

Blinq card custom fields (created per card profile in the Blinq dashboard) require corresponding Merge Fields in the target Mailchimp Audience. We create Merge Fields during migration using the same field label and the closest matching Mailchimp type (TEXT, NUMBER, DATE, PHONE, ADDRESS). Long-text Blinq fields may be truncated or stored as multiple shorter merge fields depending on Mailchimp's 255-character limit per merge field.

Blinq tags and qualifiers applied to a contact transfer as Mailchimp tags on the corresponding subscriber. Mailchimp tags are account-level, not Audience-scoped, so a Blinq qualifier like 'event_attendee' becomes a Mailchimp tag shared across all Audiences. If the same tag name exists in Mailchimp with a different casing, we match case-insensitively and preserve the source Blinq tag label.

Blinq meeting notes and AI-generated conversation summaries are stored per connection record. Mailchimp's subscriber Notes field holds up to 255 characters. For notes exceeding that limit, we create a custom long-text Merge Field (e.g., Connection_Notes__c) and store the full note content there. Timestamps on meetings are preserved as a separate date Merge Field.

Blinq stores event name, event date, and scan timestamp for badge scans. Mailchimp has no native event-log object. We surface this as a custom text Merge Field per event (e.g., Last_Event__c = 'CRM Summit 2025') and optionally store the full scan history as a JSON-encoded custom merge field for reference — your team decides whether to display this on the subscriber profile.

Blinq users with multiple cards (e.g., separate cards for different roles or companies) create multiple contact records in Blinq. When the same email appears on multiple Blinq cards, we merge into a single Mailchimp subscriber and store the card-specific context in role-labelled Merge Fields (e.g., Primary_Card_Role__c, Secondary_Card_Company__c) rather than creating duplicate subscribers.

Blinq's Zapier integration creates a sync log showing when a contact was pushed to a CRM. Mailchimp has no native sync-log object. The sync history is preserved as a reference field (Sync_Log__c) in text format for audit purposes, but the operational meaning of 'synced to CRM' does not apply in Mailchimp's pull-based model.

Blinq stores card owner details (name, email, profile) separately from contact records. In Mailchimp, the account owner and subscriber records are separate objects. We do not migrate Blinq user accounts to Mailchimp subscriber records — the Mailchimp account is provisioned separately and managed by your team independently of the subscriber audience.

Mailchimp does not expose a native created-date field on subscribers accessible as merge data. We create a custom TIMESTAMP-type Merge Field (Blinq_Created_Date__c) on the Audience and populate it with the original Blinq contact creation date so reporting can reflect the full contact history from the source system.

Blinq tracks how a contact was added (QR scan, NFC tap, email share, link click). Mailchimp has no native channel attribution field. We map this to a custom text Merge Field (Source_Channel__c) so your Mailchimp segments can filter by acquisition method — useful for event teams who want to isolate contacts captured via NFC badge scans.

If a contact has unsubscribed in Blinq (or your upstream CRM), we export their email as a suppression list and import it to Mailchimp's Suppression List before the main audience import runs. This prevents accidentally re-subscribing contacts who have opted out — a requirement for CAN-SPAM and GDPR compliance. Mailchimp treats suppressed contacts differently from unsubscribed; both statuses are preserved from source.