Migrate from Thunderbolt Pipeline to Mailchimp

Thunderbolt Pipeline contacts migrate as Mailchimp subscribers within a target audience. Every contact record must have a valid email address to create a Mailchimp subscriber profile. Contacts lacking an email address cannot be imported and will be flagged as non-importable records before the migration run executes, allowing your team to address data gaps or exclude them from the migration batch.

Thunderbolt Pipeline companies transform into a custom merge field labeled COMPANY on each Mailchimp contact record. Since Mailchimp lacks a native Company object, parent-company hierarchies and multi-company affiliations collapse into a single text field per contact. This flattening preserves the primary company name but loses nested corporate structure details present in Thunderbolt Pipeline.

Bid records have no native Mailchimp equivalent, so FlitStack AI encodes bid status, bid type classification, and award outcome as contact tags on the associated contact records. Tags follow a structured format such as 'bid_2024', 'bid_awarded', and 'bid_type_subcontractor', enabling audience segmentation by bid history within Mailchimp's tagging system.

Thunderbolt Pipeline bid statuses—Pending, Submitted, Awarded, Lost, and Declined—map to tag prefixes with a standardized format. Each contact linked to a bid receives the corresponding status tag. As bid statuses change over time, contacts accumulate multiple status tags if multiple bids are associated with their record.

Workforce and resource allocation records in Thunderbolt Pipeline encode crew roles and trade specialties as tags on the linked contact. Tags such as 'role_electrician', 'role_plumber', and 'role_foreman' enable Mailchimp audience segmentation by trade classification, preserving workforce context from the source CRM.

Phone numbers transfer directly to Mailchimp's standard PHONE merge field without transformation. Both mobile and office phone numbers from Thunderbolt Pipeline are stored in the same field since Mailchimp does not differentiate between phone number types on contact records.

Thunderbolt Pipeline contact address components—street, city, state, zip, and country—map to Mailchimp's address merge fields labeled ADDR1, ADDR2, CITY, STATE, ZIP, and COUNTRY. Multi-line street addresses split on newline characters into ADDR1 for the primary line and ADDR2 for secondary address details.

Thunderbolt Pipeline project records linked to a contact encode as project tags using a standardized prefix format such as 'project_metro_walls' or 'project_active'. Project status indicators including active, completed, and on_hold append a secondary tag component to enable granular segmentation by project lifecycle stage.

Compliance document status and certification flags such as 'compliance_current', 'compliance_expired', and 'compliance_cert_osha' migrate as read-only tags on the contact record. These tags support re-certification reminder campaigns within Mailchimp by identifying contacts with expiring or expired credentials.

Thunderbolt Pipeline custom contact properties that lack a standard Mailchimp field equivalent are created as merge fields within the target audience. The merge field data type is inferred from the source property type: text properties become text merge fields, date properties become date merge fields, and numeric values become number merge fields for consistent data representation.

Contacts marked as unsubscribed or bounced in Thunderbolt Pipeline export as a Mailchimp suppression list and import separately from active subscribers. This isolation prevents accidental re-emailing of opted-out contacts while preserving the complete opt-out record in your new platform for compliance documentation and audit purposes.

Thunderbolt Pipeline bid notification workflows, task assignment automations, and workforce reminder rules are platform-native logic constructs with no direct Mailchimp equivalent. These workflow definitions must be reviewed and rebuilt manually using Mailchimp's automation builder or external workflow tools like Zapier or Make to replicate the original logic.

Thunderbolt Pipeline's bid analytics, margin reports, and workforce utilization dashboards lack a Mailchimp counterpart. While the underlying contact data migrates successfully, the reporting layer including bid-specific metrics and construction analytics must be reconstructed using Mailchimp's campaign analytics or an external business intelligence tool for ongoing visibility.