Migrate from Onsite CRM to Mailchimp

Onsite CRM Contact records map 1:1 to Mailchimp Audience members. The primary email address serves as the subscriber hash for Mailchimp's API import. First name, last name, phone, and address fields map to Mailchimp's standard contact fields. Status respects unsubscribe and cleaned records: we export the suppression list from Onsite CRM if available and import it as a non-subscribed audience in Mailchimp to prevent accidental re-engagement.

Onsite CRM Company records do not map to a native Mailchimp object. We create a COMPANY merge tag in Mailchimp and populate it by joining each Contact's associated Company name. If Onsite CRM exposes a company-address export, we map it to Mailchimp's ADDRESS merge tag group on the contact. The company-contact relationship is preserved as a data attribute rather than a separate record type.

Onsite CRM custom fields on Contact map to Mailchimp merge tags. Mailchimp requires merge tag names in ALL CAPS with a maximum of 10 characters and alphanumeric characters plus underscores only. We transform the Onsite CRM field labels to valid Mailchimp MERGETAG syntax during the import transform phase. Picklist-style custom fields in Onsite CRM become Mailchimp radio or dropdown merge field types. Multi-select fields become checkboxes.

Onsite CRM tags applied to Contacts migrate as Mailchimp Tags. Tags in Mailchimp are lightweight labels used for segmentation and targeting. We export the contact-tag associations and import them via the Mailchimp Tags API after the contacts are loaded. Tag taxonomy is preserved as-is with no normalization unless the customer requests cleanup during scoping.

Onsite CRM Deal records have no equivalent in Mailchimp. Mailchimp does not support a deal, opportunity, or pipeline object. We export the Deals list (deal name, value, stage, close date, associated contact) as a CSV and deliver it alongside the migration for the customer's admin to handle manually or use in a separate spreadsheet-based tracking workflow. The deal-contact association is noted in the export.

Onsite CRM pipeline stage definitions do not map to any Mailchimp object. Pipeline stages are a sales-specific concept that Mailchimp's marketing-centric model does not support. We include pipeline stage definitions in the delivered deals CSV so the customer can document their original sales process outside Mailchimp if needed.

Onsite CRM email engagement history (sent, opened, clicked) has no native Mailchimp equivalent because Mailchimp tracks campaign-level engagement, not individual email log entries from a source CRM. We export email engagement records as a CSV for the customer's admin to reference. The contacts themselves migrate with their opt-in status preserved; future email campaigns in Mailchimp will generate fresh engagement data.

Onsite CRM call logs and SMS threads are phone-channel activities with no Mailchimp equivalent. Mailchimp tracks email engagement only. We do not migrate calling or SMS history. These records are flagged in the unmapped-records inventory delivered post-extraction.

Onsite CRM task and reminder records do not map to any Mailchimp object. Mailchimp's automation is campaign-triggered, not task-management-based. We deliver an export of open and completed tasks as a CSV for the customer's admin to handle in a separate task management tool post-migration.

Onsite CRM user records (sales reps and admins) map to owner and assignee fields in CRM systems but have no equivalent in Mailchimp's per-seat licensing model. Mailchimp accounts are assigned by email invitation; user records from Onsite CRM are not a transferable artifact. We include a user-list export as reference data only.