Migrate from SuperOffice CRM to Mailchimp

SuperOffice Contact records map directly to Mailchimp Subscribers. The contact's email address becomes the Subscriber email (Mailchimp's unique identifier), first name maps to FNAME, last name maps to LNAME, and phone number maps to PHONE if present. We run a duplicate-email scan against the SuperOffice associate table before export and remediate any conflicts per SuperOffice Admin requirements. Active status in SuperOffice maps to subscribed; contacts with an explicit unsubscribe or mailing-opt-out preference map to unsubscribed in Mailchimp.

SuperOffice Company records do not have a direct Mailchimp equivalent because Mailchimp organizes by Subscriber, not Account. We resolve the Company-Contact link via the associate table, then populate the COMPANY merge field on each Subscriber with the linked Company name. If the customer requires Company-level segmentation in Mailchimp, we create tags derived from Company name (e.g., tag: Acme Corp) and apply them during import so that audience filtering can work by company.

SuperOffice Selections are named dynamic lists of Contacts, Companies, or Sales. Each Selection maps to a separate Mailchimp Audience. We evaluate each Selection's membership at migration time and import those contacts as subscribed members of the corresponding audience. Selections referencing Companies or Sales rather than Contacts directly are resolved through the associate table to identify the underlying Contact records before audience assignment. Customers with more than five Selections should plan for multiple Mailchimp Audiences or consider using a single audience with tags for segmentation to avoid per-audience pricing.

SuperOffice user-defined fields (udefs) on the Contact object map to Mailchimp merge fields. We create a merge field in Mailchimp for each SuperOffice udef, matching the field type: text udefs become text merge fields, date udefs become date merge fields, and dropdown udefs become dropdown merge fields with the same option values. The Prog ID from SuperOffice is preserved in a handoff note for the customer's reference when mapping templates. Development Tools license is required to customize udef placement in SuperOffice, which affects how quickly the customer can audit their own field inventory during scoping.

SuperOffice Tags are applied across Contact, Company, Sale, and Project objects. Tags on Contact records migrate as Mailchimp tags. Multi-value tags (contacts with multiple tags) become multiple Mailchimp tag assignments on the same Subscriber. We export tags as a normalized list and apply them in batch during import. Tags on non-Contact records (Company, Sale, Project) are not migrated because those objects do not have a Mailchimp destination.

SuperOffice tracks mailing consent at the Contact level. We map SuperOffice mailing preference settings to Mailchimp subscription status: contacts with an active mailing subscription become subscribed, contacts with an explicit unsubscribe become unsubscribed, and contacts with no mailing history or no consent recorded become pending (for GDPR compliance requiring double opt-in in certain jurisdictions). We preserve the original consent timestamp as a merge field consent_date__c for audit purposes.

SuperOffice Sales (Deals) have no Mailchimp equivalent and are not migrated as data records. However, if a customer uses SuperOffice Sales as a proxy for customer lifecycle stage (e.g., Closed-Won mapped to Customer), we can surface this as a tag on the migrated Contact (e.g., tag: Customer, tag: Prospect) using the Sale's stage value linked via the associate table. This is an optional mapping decided during scoping. The customer receives a written inventory of all Sales records in the handoff documentation.

SuperOffice Projects do not map to any Mailchimp object. If the customer links Contacts to Projects via the associate table and wants to flag high-value accounts, we can apply a Mailchimp tag derived from the Project name (e.g., tag: Enterprise Account) during contact import. Otherwise, Project records are inventoried in handoff documentation and not migrated as data.