Migrate from Fame Service to Mailchimp

Fame Service contacts migrate as Mailchimp audience members. Each contact's email address becomes the unique identifier. Status (subscribed, unsubscribed, cleaned) is preserved from Fame Service. Duplicate emails across Fame Service lists are flagged before bulk import. We also validate email formats to ensure they comply with Mailchimp's syntax requirements before import.

Fame Service first name maps to Mailchimp's built-in FNAME merge field. If Fame Service stores full names in a single field, we split on space and populate both FNAME and LNAME. Empty first names pass through as blank. We also handle hyphenated or compound names by treating hyphens as separators when splitting.

Fame Service last name maps to Mailchimp's built-in LNAME merge field. If no last name exists in Fame Service, LNAME is left blank. Mailchimp accepts contacts without last names. For multi-part surnames such as those with spaces, hyphens, or prefixes, we preserve the full string as the LNAME value to maintain accuracy.

Email is the primary key in Mailchimp and must be unique per audience. We run de-duplication against existing audience members before importing. Bounced or cleaned emails from Fame Service are imported with status preserved to avoid re-sending to invalid addresses.

Fame Service phone numbers migrate to Mailchimp's PHONE merge field. We validate and format phone numbers to E.164 standard before import to ensure SMS-capable numbers are correctly stored. If a phone number lacks a country code, we attempt to infer it based on the contact's address data; otherwise, we flag it for manual review before migration.

Mailchimp has no native Company object. Fame Service company names are stored as a custom field (Company_Name__c) on each contact. We recommend creating this as a text merge field in your Mailchimp audience before migration runs. If Fame Service stores additional company attributes such as industry or website, those are mapped to separate custom fields (e.g., COMPANY_INDUSTRY, COMPANY_WEBSITE) for completeness.

Mailchimp does not support deal or pipeline stages. Deal amounts and stage names from Fame Service are migrated as read-only custom fields on contacts — they preserve historical context but cannot drive Mailchimp automations. Each deal's close date is also stored as a separate date field (ORIG_CLOSE_DATE__c) to retain timeline information for reporting purposes.

Fame Service tags map directly to Mailchimp tags. Tags are applied to contacts during import using Mailchimp's tag management endpoint. Tags with the same name across Fame Service lists are consolidated — no duplicate tags created per contact. If a tag exceeds Mailchimp's 50-character limit, we truncate it and append an index to preserve uniqueness.

If Fame Service has multiple lists, we recommend merging into one Mailchimp audience using tags to distinguish original list membership. Multiple Mailchimp audiences are independent — contacts counted separately — so merging is more cost-efficient at scale. Before merging, we reconcile subscription statuses across lists to ensure the most restrictive status (e.g., unsubscribed) takes precedence in the combined audience.

Fame Service custom fields map to Mailchimp merge fields. We pre-create merge fields in Mailchimp (via API) before importing contacts. Mailchimp limits merge field names to 10 characters and uppercase — we handle the name transformation automatically. If a Fame Service field name exceeds 10 characters, we truncate it and add a short suffix to avoid collisions with existing fields.

Mailchimp does not preserve original record creation dates. We store the Fame Service create timestamp as a custom date field (SOURCE_CREATED_DATE__c) on each contact for reporting continuity. The custom field is formatted as ISO 8601 (YYYY-MM-DD) to align with Mailchimp's date expectations, and it is indexed for use in segmentation filters.

Fame Service unsubscribe and bounce records migrate with status preserved. Mailchimp suppresses these contacts from future sends automatically. We import them as non-marketing contacts to retain historical data without counting toward paid contact limits. The original bounce reason, where available, is stored in a custom text field (BOUNCE_REASON__c) for audit and re-engagement decision-making.

Automations do not transfer between platforms due to incompatible trigger-action architectures. We export Fame Service automation definitions as a structured JSON reference that your team can use to rebuild Customer Journeys in Mailchimp. The export includes trigger types, conditions, delays, and action sequences.