Migrate from Tubular CRM to Mailchimp

Tubular Contacts map directly to Mailchimp Audience Members. We transfer first name, last name, email address, phone number, company association, owner assignment, and custom fields to Mailchimp Merge Fields. Email address is the dedupe key during import. Tubular's company association is stored as a Merge Field (COMPANY) because Mailchimp has no separate Companies/Accounts object. Tags from Tubular Contacts are applied as Mailchimp Tags at import time.

Tubular Deals have no direct Mailchimp equivalent, so we split the mapping across two Mailchimp features. The deal name and current stage become a Mailchimp Tag (e.g., deal_name__stage). Deal value, currency, payment terms, owner, and probability percentage become Merge Fields (DEAL_VALUE, DEAL_CURRENCY, DEAL_STAGE, DEAL_OWNER, DEAL_PROBABILITY). Because Tubular Pro exports Deals as flat CSV rows, multi-product Deals lose line-item granularity unless the customer exports Line Items separately and we merge them as a delimited Merge Field value.

Each Tubular Pipeline Stage becomes a Mailchimp Group within the primary Audience. We create Groups matching the stage names (e.g., Prospecting, Qualification, Proposal, Negotiation, Closed Won, Closed Lost) and subscribe imported Contacts and Leads to the Group corresponding to their current deal stage. Group-based segmentation enables targeted campaigns to contacts at specific pipeline stages without requiring Merge Field filtering.

Tubular Leads map to Mailchimp Audience Members with a Tag (LEAD_SOURCE: Tubular) applied to distinguish them from converted Contacts. Lead source, status, owner, and custom Lead Builder fields transfer as Merge Fields. The Lead-to-Contact conversion workflow is not automated in Mailchimp; the customer's team manages lead status changes manually or through Customer Journey automation.

Tubular Tags on both Contacts and Deals transfer as flat label arrays to Mailchimp Tags. Tag names are preserved exactly as stored in Tubular. If the same tag appears on a Contact and a Deal, it is applied once to the Audience Member record. Mailchimp's 10 requests/second API rate limit is observed during bulk tag application to avoid throttling.

Tubular Tasks cannot be represented as native task objects in Mailchimp because Mailchimp has no Tasks or Activities object. We convert open tasks to a Tag (PENDING_TASK: [task title]) and completed tasks are dropped. Task due dates and owners are stored as Merge Fields (TASK_DUE, TASK_OWNER) on the contact record. This approach preserves task awareness but not the full task management capability of Tubular.

Email logs, call logs, and notes from Tubular Activity Logs attach to the related Contact or Deal. In Mailchimp, activity history converts to a Tag (LAST_ACTIVITY: [type]) and note content is stored in a Merge Field (ACTIVITY_NOTE) as a truncated text value. Full chronological activity timelines are not reconstructable in Mailchimp because the platform does not support timestamped activity records.

Tubular Owner names and IDs map to a Mailchimp Merge Field (DEAL_OWNER) applied to the related Contact record. Owner email lookup is used to match Tubular Users to Mailchimp contacts where the owner differs from the contact. Mailchimp does not have a Users or Teams object, so role-based access control within Mailchimp is configured separately by the customer's admin.

Tubular Leads map to Mailchimp Audience Members with a Tag (OBJECT_TYPE: Lead) applied at import to preserve the source object type. Lead source, status, owner, and custom Lead Builder fields transfer as Merge Fields. The Lead-to-Contact conversion workflow is not automated in Mailchimp; the customer's team manages lead status changes manually or through Customer Journey automation.

Tubular Tags on both Contacts and Deals transfer as flat label arrays to Mailchimp Tags. Tag names are preserved exactly as stored in Tubular. If the same tag appears on a Contact and a Deal, it is applied once to the Audience Member record. Mailchimp's 10 requests/second API rate limit is observed during bulk tag application to avoid throttling.