Migrate from Summit Service Systems to Mailchimp

Summit Contact records map directly to Mailchimp Subscribers via email address as the unique identifier. First name, last name, email, phone, and address fields become standard Mailchimp merge fields. Owner assignment in Summit has no direct equivalent in Mailchimp's subscriber model.

Email address is the primary key for Mailchimp subscribers. FlitStack uses email as the match field for deduplication during import, flagging duplicate emails against existing Mailchimp subscribers by audience. If a duplicate email is detected, the most recent activity timestamp from Summit determines which record takes precedence, preserving the freshest profile in the target audience.

Mailchimp has no native Company or Account object. Summit Company name and industry map to custom merge fields (COMPANY_NAME, INDUSTRY) on the subscriber record. This is a flat denormalization — company hierarchies and parent-child relationships are not preserved in Mailchimp's model.

Phone number migrates as a custom TEXT merge field in Mailchimp. Standard Mailchimp accounts do not include a native PHONE field — FlitStack creates this as a subscriber custom field before import. This ensures that any phone numbers captured in Summit are searchable and segmentable in Mailchimp, even if the field must be manually added via Audience settings.

Summit custom properties on Contact records (text, number, date, pick-list) each require a corresponding Mailchimp merge field. Merge field type must match Summit's data type. Pick-list values from Summit become TEXT merge fields in Mailchimp — value remapping is not available in Mailchimp merge fields.

Mailchimp has no deal or opportunity object. Summit Deal names and stages can be represented as Mailchimp tags (e.g., Deal Stage: Proposal Sent) or as segment criteria, but the full deal record with amount, close date, and contact associations does not map to any native Mailchimp construct. We recommend tagging subscribers by deal stage as a reference signal.

Summit tags applied to contacts migrate as Mailchimp tags. Tags are additive labels in both platforms. FlitStack maps tag names directly, preserving the full tag string. Tags with Summit-specific naming conventions are imported as-is. Any tag that contains special characters or spaces is URL‑encoded during import to maintain consistency with Mailchimp's tag format.

Mailchimp does not natively store original opt‑in timestamp as a subscriber field. FlitStack creates a MC_OPTIN_DATE merge field and populates it from Summit's contact creation date or explicit opt‑in timestamp for deliverability and compliance continuity. This value is stored as a TEXT merge field, allowing segmentation based on when the subscriber originally opted in.

Summit contacts with an unsubscribed status export as suppressed contacts and are imported to Mailchimp's per‑audience suppression list. This prevents accidental re‑engagement emails after migration. The suppression file includes the EMAIL and STATUS fields required by Mailchimp, and it is loaded before the active subscriber import to ensure that all opted‑out contacts are excluded from any campaign activity immediately after cutover.

Summit may store email engagement logs linked to contacts. Mailchimp tracks campaign open and click data natively per subscriber, but historical engagement from Summit does not migrate into Mailchimp's activity timeline. That data remains in Summit exports for reporting continuity.