Migrate from Simpleview CRM to Mailchimp

Simpleview Member Account records (analogous to Companies in horizontal CRMs) contain primary contact data, address, and organization-level custom fields. We extract the primary Contact record linked to each Member Account, map the account name to the Company field on the Mailchimp contact, and preserve the source Simpleview AcctID as an external_id for deduplication. Any Member Account records without an associated contact are held in a reconciliation queue for manual review.

Simpleview Contact records linked to Member Accounts migrate to Mailchimp Contacts within the target Audience. We map first name, last name, email address, phone, and postal address to the corresponding Mailchimp merge fields. The original Simpleview contact ID is stored in a custom external_id field for future sync reference.

Fields under Simpleview's Custom_Account category have no standardized schema across clients. We extract the full client-specific field definition during audit, map each custom field to either a Mailchimp merge tag (for single-value fields) or an Audience Group with group options (for picklist-type fields). Text-area and multi-line custom fields are stored as merge tags with full text content preserved. Required-field constraints are set on merge tags as specified by the customer during scoping.

Amenity_MS values on Simpleview Listings use a client-defined vocabulary. We extract the full source amenity vocabulary, deduplicate it, and map each value to a Mailchimp Tag on the associated contact record. Unmapped amenities are flagged for manual review before final import. Any Listing-level amenities that cannot be attributed to a specific contact are summarized in a written document for the customer admin.

Simpleview Listings represent partner/member directory entries tied to Member Accounts via AcctID. We do not create directory-style records in Mailchimp since Mailchimp has no listing or directory object. Instead, we extract the ListingID and link it to the corresponding Member Account contact record via a merge tag (listing_id). The customer admin can use this reference to build a supplementary directory in a separate tool if needed.

Simpleview Opportunity pipeline stages (meetings, sports, travel trade, group business) have no structural equivalent in Mailchimp. We extract a written inventory of all open and historical opportunities with their stage, value, close date, and associated Member Account. The customer admin re-enters pipeline data manually or evaluates a dedicated CRM if ongoing pipeline tracking is required.

Simpleview Events are first-class objects with registrations linked to Member Accounts. Mailchimp has no event management or registration object. We extract a written inventory of all events with attendee lists, registration status, and event metadata. The customer admin evaluates event platforms (Eventbrite, Cvent, or others) for ongoing event management needs.

Simpleview Coupons link to Listings and Member Accounts with date ranges (RedeemStart, RedeemEnd, PostStart, PostEnd) and offer text that may include HTML. Mailchimp has no coupon or offer management object. We extract coupon metadata as a written inventory for the customer admin to recreate in a coupon management tool or discount tracking spreadsheet.