Migrate from Bridgify to Mailchimp

Booking history cannot natively trigger Mailchimp Customer Journeys

Bridgify booking records contain structured status and timestamp data, but Mailchimp automations run on tags, date fields, and subscriber activity within Mailchimp — not on external booking events. After migration, FlitStack AI tags each subscriber based on their Bridgify booking profile (experience type, status, recency), which enables Customer Journey entry conditions in Mailchimp, but ongoing booking-triggered sends require a Zapier or webhook integration between Bridgify and Mailchimp to fire in real time. The historical booking data is preserved for segmentation but not for live automation triggers without additional integration work.

Hard bounces and invalid emails must be suppressed before import or they damage deliverability

Mailchimp applies deliverability penalties when imported audiences contain high bounce rates. If Bridgify contacts include bounced or malformed email addresses, those must be validated and removed before the Mailchimp import runs. FlitStack AI runs an email format audit against every Bridgify contact during the pre-migration validation step — syntactically invalid addresses are flagged and excluded, and a cleaned import file is used for the Mailchimp upload. Hard-bounce history from Bridgify is preserved as a custom field for compliance reference but does not map to a live Mailchimp suppression rule.

Duplicate email addresses across Bridgify partner datasets collapse to one Mailchimp subscriber

If Bridgify serves multiple partner programs or loyalty tiers and a single customer appears in more than one dataset — for example, a bank customer who is also a loyalty program member — they may have multiple Bridgify records with the same email address but different booking history. Mailchimp uses email address as its unique subscriber key, so FlitStack AI deduplicates by email during import, merging tag histories from both Bridgify records into a single Mailchimp subscriber. The bridgify_customer_id custom field stores both source IDs for audit traceability. This merging may cause partner-tier tags to coexist on one subscriber record.

Unsubscribe and consent flags require explicit mapping to avoid GDPR and CAN-SPAM exposure

Bridgify consent tracking uses a non-standard flag model — some contacts may have implied opt-in from booking activity rather than explicit email marketing consent. Mailchimp enforces explicit opt-in for most plan tiers and requires that unsubscribes are honored immediately. FlitStack AI maps every Bridgify consent variant to the correct Mailchimp subscriber status: explicit opt-in becomes Subscribed, implied consent or booking-only records become Pending (triggering a double opt-in confirmation email), and any Bridgify record with an unsubscribe action is pre-suppressed in Mailchimp before the migration completes. Regional compliance metadata is preserved in custom fields for audit purposes.

Mailchimp's audience-level pricing means merged records count once — but only if email deduplication is clean

Mailchimp bills by total subscriber count within each audience, including unsubscribed contacts still in the audience. If deduplication logic misses contacts with identical email addresses using different letter casing or extra whitespace, Mailchimp will treat them as separate billable subscribers. FlitStack AI normalizes all email addresses to lowercase with trimmed whitespace before generating the Mailchimp import file, which reduces the risk of duplicate billing. However, contacts that genuinely share an email address (such as corporate shared inbox accounts used by multiple Bridgify customers) will still collapse to one Mailchimp subscriber — your team should review these before migration commits.