Migrate from PipelineManager to Mailchimp

PipelineManager People records map directly to Mailchimp Contacts within a primary Audience. Each PipelineManager Person's name, email address, phone number, and custom properties migrate. Email address is the dedupe key. Mailchimp does not enforce a first-name and last-name split on import; we split on the first space if PipelineManager stores a full name field, or preserve as a single name field if the source data is inconsistent.

PipelineManager Company records have no native Mailchimp equivalent. We create a Mailchimp Tag for each unique Company name and apply it to all Contacts in the migrated Audience that are associated with that Company in PipelineManager. Company-level properties (industry, website, address) migrate as merge fields on each Contact or as structured tag notes in a companion document.

PipelineManager custom properties on People records map to Mailchimp Merge Fields (per-contact structured data like phone number or company size) or Tags (cross-contact labels). We assess each custom property during discovery: text fields become Merge Fields if they are per-contact and free-text; select or multi-select fields become Tags. The customer selects the strategy during scoping.

PipelineManager custom properties on Company records have no per-contact storage in Mailchimp. We convert each Company-level custom property to a Tag with format CompanyProperty:Value and apply it to all Contacts associated with that Company. This preserves the segmentation signal at the cost of tag proliferation.

PipelineManager Pipelines organize Deals into named streams (e.g., SMB Sales, Enterprise Sales). Mailchimp has no pipeline or deal-stage concept. We document every Pipeline name and Pipeline ID in the migration inventory so the customer can decide whether to recreate them as Mailchimp Audiences (one per Pipeline) or drop them from active use. This is not a data loss risk; it is a structural difference that must be addressed during scoping.

PipelineManager Deals track sales opportunities with stage, value, owner, and close date. Mailchimp has no Opportunity or deal object. We export Deal records to a CSV delivered alongside the contact migration so the customer's admin can import them into a spreadsheet, a separate CRM, or a Mailchimp-compatible tool if deal tracking is still required. We do not drop Deals silently; we surface the gap and deliver a written record.

PipelineManager activity logs (calls, emails, meetings, notes) attached to People records do not have a native Mailchimp equivalent. Mailchimp tracks opens, clicks, and unsubscribes per campaign but not per-contact call logs or meeting history. We document the activity count per contact in the migration inventory and advise the customer that the timeline will reset in Mailchimp. If the customer requires activity history, we recommend a parallel CRM migration to a platform with activity tracking.

PipelineManager stores unlimited file attachments per account. Mailchimp stores attachments only within individual email campaigns (images and PDFs attached to emails sent to an Audience). We export attachment filenames and storage URLs to a companion CSV. We do not drop the attachment inventory; we deliver it so the customer can manually re-associate files post-migration.