Migrate from Crank CRM to Mailchimp

Crank CRM Contacts map to Mailchimp audience members. We extract email address, first name, last name, phone number, and any custom fields active on the contact record, then insert them as Mailchimp subscriber records via the Marketing API. Status (subscribed, unsubscribed, pending) maps to Mailchimp member status. If double opt-in is enabled in the Mailchimp destination account, pending contacts receive a confirmation email. Duplicate email detection uses Mailchimp's hash-based deduplication against the existing audience.

Crank CRM Organizations map to Mailchimp Customer Profiles on Standard and Premium plans, storing company name, industry, website, and address. On lower Mailchimp plans that lack Customer Profiles, we store organization data as merge fields (COMPANY, INDUSTRY, WEBSITE) on the Contact record. Organization mapping requires that the Contact has a resolved email address before the organization is stored. We link organization names back to their contacts via a shared tag for segment-building.

Crank CRM Demo Sessions are the primary data entity in the source platform. Each session's metadata (session date, duration, viewer count, recording URL, sharing method) is decomposed: session date and duration become date and text merge fields on the related Contact record. Viewer count and sharing method become numeric and text merge fields. Recording URLs are stored as URL-type merge fields. We tag the contact with the demo campaign or product name for segmentation in Mailchimp. Sessions without a linked Contact are held in a staging table for admin review.

Crank CRM Owner records are resolved by email match against the Mailchimp destination account's admin users. If a matching Mailchimp user exists, the owner name is stored as a merge field or tag for attribution. If no match exists, the owner name is stored as a text merge field on each related contact record. Owner-to-contact linkage is preserved via tag naming convention (Owner: [Name]) rather than a formal lookup relationship, as Mailchimp has no Owner object equivalent.

Crank CRM custom fields on Contacts or Organizations (active only if CRM modules are enabled) map to Mailchimp merge fields by matching field type. Text, number, date, phone, and URL custom fields map directly to corresponding Mailchimp merge field types. Multi-select or checkbox fields map to Mailchimp tags or a comma-separated text merge field. We pre-create the merge field schema in the Mailchimp audience before importing any contacts, as merge fields must exist before they can receive data. Mailchimp allows up to 40 merge fields per audience.

Crank CRM Pipelines and Deal records have no structural equivalent in Mailchimp. If CRM modules are active, we store the most recent Deal stage and deal name as text merge fields on the Contact record, and tag the contact with the pipeline name and stage for segmentation. Deal monetary values, probabilities, and close dates are stored as numeric and date merge fields. This mapping preserves the data as properties but does not recreate a pipeline view in Mailchimp; the customer's admin maps these to Mailchimp Automations or a companion CRM for ongoing pipeline management.

Crank CRM Usage Logs capture screen share, recording, and email campaign activity. We translate each log entry into a Mailchimp tag on the associated Contact (tag format: Usage_[Type]_[Timestamp]) to preserve interaction history. High-volume usage logs (thousands of entries per contact) are summarized rather than individually tagged to avoid exceeding Mailchimp's per-contact tag limits. We aggregate by activity type and attach a summary note field instead.

Crank CRM demo recording URLs and session attachments are stored as URL-type merge fields on the Contact record. We do not download and re-upload recordings to Mailchimp (Mailchimp does not have a file attachment object for contact records). Broken links (recordings deleted or expired on CrankWheel's infrastructure) are flagged in the migration report with the session record ID so the customer's admin can follow up. Attachments that are documents (PDFs, slides) linked in session records are documented with their URL and associated contact for manual re-upload if needed.