Migrate from OnePageCRM to Mailchimp

OnePageCRM contact records map to Mailchimp contacts within a target Audience. Email address is the dedupe key. We export all standard fields (first name, last name, phones, addresses, social URLs) and map them to Mailchimp's default contact properties. The contact's status in OnePageCRM (e.g., active, archived) determines whether the record enters the active audience or is held for review. Custom contact fields from OnePageCRM map to Mailchimp merge fields using exact tag matching—see the gotchas section for field name requirements.

OnePageCRM Organizations (companies) do not have a direct Mailchimp equivalent. Mailchimp has no company or account record. We handle this by mapping Organization name and address to merge fields on each linked Contact record. For contacts linked to the same company, the company data appears on each contact as identical merge field values. We document the Organization-to-contact relationship in a separate lookup table so the customer can restore company grouping if they later move to a CRM that supports account records.

OnePageCRM Deals cannot migrate to Mailchimp. Deals track sales pipeline, amount, stage, close date, and product line items—none of which Mailchimp models. We extract deal metadata (deal name, associated contact, stage, amount) into a CSV export delivered alongside the audience import. The customer's sales team reviews this export and decides whether to export deals to a separate CRM or accept them as archived records.

OnePageCRM tags assigned to contacts migrate to Mailchimp tags on the corresponding audience contact. Tags are a flat namespace in both platforms. We carry over all contact-level tags from the export. If a contact has multiple tags in OnePageCRM, each tag appears as a separate Tag record in Mailchimp. Deal-level tags do not migrate because Deals themselves do not migrate.

OnePageCRM admin-created custom fields on contacts require pre-creation in Mailchimp as merge fields before import. Merge field tags must exactly match the OnePageCRM custom field label or API name (we verify this during scoping). Supported merge field types in Mailchimp are text, number, date, phone, address, and website. Drop-down or multi-select custom fields in OnePageCRM map to Mailchimp radio or checkbox merge fields if the destination Mailchimp account supports those field types at the current plan tier.

OnePageCRM Lead Source classifies how a contact entered the CRM (website inquiry, referral, etc.). We map this to a Mailchimp merge field called LEAD_SOURCE or apply it as a tag depending on the customer's preference. If Mailchimp already has a LEAD_SOURCE merge field configured, we use it. If not, we recommend creating it during pre-migration setup and flag it in the custom field checklist.

OnePageCRM contact status (Prospect, Customer, Archived, etc.) has no direct Mailchimp equivalent. Mailchimp uses subscriber status (subscribed, unsubscribed, bounced, cleaned). We map active OnePageCRM contacts to Mailchimp subscribed status. Archived or inactive contacts are mapped to unsubscribed or held for review depending on the customer's suppression strategy. The full status taxonomy mapping is defined during scoping and documented in the migration runbook.

OnePageCRM Predefined Items represent products or services used in deal creation. Mailchimp has no product catalog object. We export Predefined Items as a separate CSV with name, price, quantity, and grouping. If the customer needs to track product interests in Mailchimp, the items can be mapped to Mailchimp product rows within aAutomation e-commerce event tracking, but this requires Mailchimp's e-commerce integration and is scoped separately from the standard contact migration.