Migrate from Inception to Mailchimp

Inception contacts migrate directly as Mailchimp audience members. Email address is the unique identifier; first name, last name, phone, and address fields map to Mailchimp's standard merge fields (FNAME, LNAME, PHONE, ADDRESS). Duplicate email addresses are flagged for merge or suppress decisions before import.

Inception companies have no direct Mailchimp equivalent. Companies are mapped as tags applied to contacts (e.g., tag 'Pfizer-Midwest-Region') or as a custom text field (Company_Name__c) on the audience member record. Multi-company associations per contact collapse to the primary company tag.

Inception deal records contain prescription volume, pipeline stage, and close date. These map to Mailchimp custom merge fields (Deal_Stage__c, Rx_Volume__c, Close_Date__c) and stage-based tags (e.g., 'Pipeline-Prospective', 'Pipeline-Prescribed'). Mailchimp has no native deal workflow capabilities; this data becomes reference metadata for historical tracking.

Inception call logs with timestamp, duration, rep name, and outcome migrate as Mailchimp activity notes on the contact record. Original call date preserved. Note format: '[Rep Name] Call - Duration: X min - Outcome: [value]'. Call disposition codes stored in supplemental CSV export.

Inception email activity records showing sent/received status and subject line become Mailchimp activity notes. Subject line truncated to 255 characters to fit Mailchimp note field. Original send timestamp preserved as reference on the contact record.

Inception meeting records with meeting title, date, duration, and attendee list migrate as Mailchimp activity notes. Attendee names appended to note body. Meeting location or virtual link stored in a custom text field if present in Inception data.

Inception custom contact properties (e.g., Therapeutic_Area__c, HCP_License__c, Prescribing_Tier__c) require Mailchimp merge field creation before migration. FlitStack creates matching text, number, or dropdown merge fields via the Mailchimp API and maps values directly during import. Dropdown values require manual value-by-value configuration in Mailchimp's field settings.

Inception owner/rep assignments on contacts have no direct Mailchimp equivalent. Mailchimp contacts are not owned by individual users. Rep-contact assignments are documented in a separate CSV export for reference and reconciliation. If rep-based contact routing is required in Mailchimp, owner tags can be applied manually after migration.

Inception sales workflow rules (e.g., auto-follow-up after no response, territory-based routing) cannot migrate to Mailchimp. Mailchimp's Customer Journeys operate using email-triggered automations that function fundamentally differently from CRM workflow logic. FlitStack exports workflow definitions as JSON documentation for your team's manual rebuild in Customer Journeys.

Inception report configurations measuring rep performance, prescription targets, and physician engagement cannot transfer to Mailchimp. Report definitions are exported as reference CSVs for documentation. Mailchimp's built-in analytics cover campaign performance and audience growth metrics, not sales force productivity KPIs.