Migrate from Propeller CRM to Mailchimp

Propeller Contact records map directly to Mailchimp subscribers in the destination audience. We preserve first name, last name, email address, phone number, and company name as standard Mailchimp merge fields (FNAME, LNAME, EMAIL, PHONE, COMPANY). Any Propeller custom contact properties migrate as additional merge fields or subscriber tags. Opt-in status is inferred as subscribed for all exported contacts unless the Propeller record explicitly noted an unsubscribed or bounced status, which we carry over as the Mailchimp Subscribed status field.

Mailchimp has no dedicated Company or Account object. Propeller Company records are merged into the Contact migration by company name, with each subscriber receiving a COMPANY merge field carrying the original company name. If a Propeller Company record was linked to multiple Contacts, those contacts receive a matching tag (e.g., 'Company: Acme Corp') so the customer can build Mailchimp segments by company affiliation post-migration. We flag any duplicate company name variations for customer confirmation before encoding.

Mailchimp has no deal or opportunity object. Propeller Deals are preserved as text-encoded tags on the linked subscriber record (e.g., 'Deal: $4,500 Enterprise Q1') and in a MERGE_NOTES or CUSTOM_NOTES merge field carrying deal name, amount, and stage as plain text. The customer should understand that these are reference annotations, not live pipeline records — Mailchimp cannot track deal progress, stage transitions, or owner assignments natively.

Propeller pipeline stage names (e.g., 'Proposal Sent', 'Awaiting Finance', 'Verbal Yes') have no Mailchimp equivalent. We encode the final stage value as a tag on the associated subscriber (e.g., 'Stage: Proposal Sent') and in the deal reference note. Stage ordering logic from Propeller is not preserved because Mailchimp has no sequence concept for subscriber attributes. Stages requiring manual placement confirmation during scoping are flagged in the mapping document before migration.

Propeller Email Campaigns are not directly importable into Mailchimp because Mailchimp campaigns are tied to send operations on its platform. We extract campaign names, associated contact lists (by email address match), send dates, and open/click statistics from the Propeller archive and document them as a written campaign inventory. If the Propeller contact lists are intact and still valid, we recreate them as Mailchimp audiences or static segments so the customer can reference historical send history alongside the new Mailchimp campaign data.

Propeller email templates with merge field names and HTML body content migrate to Mailchimp template format. We extract template subject lines, body HTML, and merge field placeholders from the archive and create Mailchimp Templates via the Mailchimp API. Plain-text variants are preserved if present in the Propeller export. The customer should review templates in Mailchimp's template editor before sending because rendering differences between Propeller's email renderer and Mailchimp's may affect layout.

Propeller user accounts tied contacts and deals to individual sales reps by email address. Mailchimp subscribers have no owner field. We capture the original owner email as a tag on each subscriber (e.g., 'Owner: [email protected]') and in the deal reference note for contacts with associated deals. If the original Propeller owner email is no longer active, this tag still preserves the attribution context for the customer's admin.

Propeller's Gmail extension tracked per-contact activity logs (email opens, link clicks, replies, meeting scheduling) as live event data inside the platform. These were not included in the shutdown data export package. We cannot reconstruct the activity timeline from the Propeller archive and do not falsely promise this data as part of the migration. Mailchimp will begin fresh campaign tracking from the date of migration onward.