Migrate from Fans-CRM to Mailchimp

Fans-CRM fan and subscriber records are the primary migration object. We extract name, email address, subscription status, subscription start date, and any custom engagement properties from the Fans-CRM export file. These map to Mailchimp Contacts inside an Audience, with Fans-CRM engagement scores mapped as a numeric custom field. Subscription status from Fans-CRM (active, lapsed, churned) maps to a Mailchimp tag rather than a standard field, since Mailchimp does not have a native subscription-status property beyond the built-in subscribe/unsubscribe/cleaned state. Email address is the dedupe key for import.

Fans-CRM tracks tier names, tier pricing, and fan counts per tier for each creator profile. We map tier assignments as a Mailchimp merge field (e.g., TIER_NAME) on each contact record, with the tier label as a string value. We also create a Mailchimp Tag matching each tier name so that audiences can be segmented by tier using Mailchimp's tag-based filtering. If multiple tiers exist per fan (e.g., monthly and one-time PPV tiers), we create additional merge fields or comma-separated tag assignments. Tier pricing is preserved as a separate numeric merge field if the migration scope includes it.

Fans-CRM stores fan-level engagement scores, chatter metrics, and interaction frequency as numerical values on the fan record. These do not map to any standard Mailchimp field. We create custom numeric fields in Mailchimp (ENGAGEMENT_SCORE, CHATTER_COUNT, LAST_ACTIVE_DATE) and import the historical values. Mailchimp does not use engagement scores for automation triggers natively, but the fields are available for segmentation in Mailchimp's Segments builder using rule conditions on numeric custom fields.

Pay-per-view transaction records include PPV amount, fan identifier, content reference, and timestamp. Mailchimp's Contact model does not support transactional revenue records natively. We aggregate the most recent or cumulative PPV value per fan as a numeric custom field (TOTAL_PPV or LAST_PPV_AMOUNT) if the data is available in the export. Full PPV transaction history is documented as a separate structured CSV delivered alongside the migration, which the customer's admin can connect to a revenue tracking system separately. We flag this as a data inventory item, not a live CRM migration object.

Fans-CRM content posts contain media references, PPV pricing, and performance metadata. Mailchimp has no content post or media library object; content lives as attachments within campaigns. We do not migrate content posts. We deliver a written inventory of post IDs, titles, PPV prices, and post dates in a structured CSV so the customer's admin can reference them for campaign content planning inside Mailchimp. Media files remain in Fans-CRM's storage and are not transferred as part of the migration.

Fans-CRM uses Smart Folders and tag-based content organization. We extract the underlying tag data from the export file and import each tag as a Mailchimp Tag on the relevant contact record. Tags migrate as flat labels; folder hierarchy from Fans-CRM is not preserved because Mailchimp has no equivalent nested folder structure. Tags are used for audience segmentation in Mailchimp. The customer chooses a tag naming convention during scoping if multiple fan profiles share a single Mailchimp audience.

Fans-CRM chat assistant templates, bulk message scripts, and automated reply rules are platform-specific automation logic with no direct Mailchimp equivalent. Customer Journeys in Mailchimp use a different trigger-and-action model. We document the template structures, message flows, and variable placeholders during discovery and deliver them as a written reference so the customer's admin can rebuild them in Mailchimp's automation builder. Template content does not migrate programmatically.

Fans-CRM agency users with role-based permissions represent team member records. Mailchimp does not have a full user management object comparable to a CRM; Mailchimp accounts have account-level Users and Workspace-level Members for multi-user access, but these are not contact records. We map agency team members as Mailchimp account Users if the customer requires user-level access tracking, or we document the role assignments separately. The anti-detect browser session data associated with team member accounts does not transfer and is not migrated.