Migrate from PipeRun CRM de Vendas to Mailchimp

Export coordination and customer participation

We schedule a joint export session with the customer's PipeRun admin to generate CSV exports for all required objects: Contacts (Contatos), Companies (Empresas/Organizações), Deals (Negócios), Activities (Atividades), and Proposals (Propostas). Each object requires a separate export. We provide the customer with a pre-migration checklist specifying which columns to include, which filters to apply (active records only vs. all records), and the export format. The customer uploads the exported files to a secure staging environment we provide. This step requires one to two business days of the customer's active participation.

Data audit and merge tag design

We audit every exported CSV file for record counts, null field frequency, duplicate email addresses, and custom field coverage. We identify all PipeRun custom fields on Contacts and map each to a Mailchimp merge tag, transforming names to meet Mailchimp's uppercase-alphanumeric convention. We design the audience structure: whether multiple PipeRun Funnels map to separate Mailchimp Audiences or to Audience Tags within a single Audience. We produce a data audit report and a merge tag mapping table for the customer to review and approve before any Mailchimp write operations begin.

Mailchimp audience and merge tag configuration

We configure the target Mailchimp Audience: creating all required merge tags (FNAME, LNAME, PHONE, COMPANY, and any custom merge fields identified in the audit), setting field types (text, date, number, dropdown), and configuring address fields if the PipeRun export includes physical address data. If multiple Audiences are required for Funnel isolation, we create them with naming that reflects the corresponding PipeRun Funnel. We verify that the Mailchimp API is accessible with the provided API key before proceeding to import.

Subscriber import with deduplication

We import Contacts from the PipeRun CSV into the configured Mailchimp Audience. Before import, we prepend the PipeRun record ID to the contact name field to eliminate PipeRun's title-based dedup risk. Email address is used as the Mailchimp dedupe key. Company associations are written as both a COMPANY merge tag on each contact and as an Audience Tag on the subscriber record. After import, we reconcile the subscriber count against the exported Contact count and investigate any discrepancies before marking the phase complete.

Deal context and tag pass

We extract deal values and current funnel stages from the PipeRun Deals CSV and append them as merge tags (DEAL_VALUE, DEAL_STAGE, DEAL_FUNNEL) on the corresponding subscriber records using Mailchimp's batch API. We apply PipeRun Company tags to all associated Contact subscribers in the same pass. We generate a per-subscriber activity map that ties each Mailchimp subscriber to the PipeRun company and deal records they were linked to, for the customer's reference during post-migration reconciliation.

Validation, handoff, and automation inventory

We run a final reconciliation comparing the Mailchimp subscriber count and field completeness against the source CSV totals. We deliver the automation inventory document listing every PipeRun ação automática with its trigger, condition, and action summary, mapped to a recommended Mailchimp Customer Journey equivalent. We conduct a live walkthrough with the customer's team to validate the audience, confirm tag coverage, and demonstrate how to rebuild the first automation in Mailchimp Customer Journeys. We do not provide ongoing post-migration support or workflow rebuild as standard scope.