Migrate from Oncord to Mailchimp

Oncord Contacts migrate 1:1 to Mailchimp audience members. The contact's email address is the dedupe key. Standard fields (first name, last name, phone, address) map to Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS). Any contact without a valid email address is held in a skip queue because Mailchimp requires an email address for audience membership. Oncord's unlimited contacts model means there is no contact ceiling during migration, but the customer should anticipate Mailchimp's per-contact pricing at scale.

Oncord Groups (static segmentation lists) map to Mailchimp Tags. Each Group name becomes a Tag applied to all members of that Group. If the destination Mailchimp account already has Tags from a prior tool, we merge rather than duplicate. On Lite plans, Oncord filters are restricted to Groups only, which means customers on Lite may have heavier reliance on Groups for segmentation than customers on higher tiers.

Oncord custom field definitions and values export via the CustomFields API component. We map text fields to Mailchimp text merge fields, number fields to number merge fields, date fields to date merge fields, and dropdown or multi-select fields to radio or checkbox merge fields respectively. Merge field tag names follow Mailchimp's MAX10CHAR uppercase convention. We flag any Oncord custom field that exceeds Mailchimp's merge field type constraints (e.g., very long text values that cannot fit in a TEXT merge field) during scoping.

Oncord Products (available only with active Commerce add-on at $40/month) migrate as Mailchimp Product entries if the destination Mailchimp account has e-commerce functionality enabled. We export product name, description, price, SKU, inventory count, and product images. Products in Mailchimp are used for product-centric automations (abandoned cart, product recommendations) and are distinct from audience data. If the customer does not have e-commerce features enabled in Mailchimp, Products migrate as a reference table in the documentation rather than live records.

Oncord discount rules, coupon codes, eligibility conditions, and usage limits (available with Commerce add-on) do not have a direct Mailchimp equivalent. Mailchimp does not manage promotional codes or discount rules natively. We document all active discounts and coupons in the handoff inventory so the customer's team can recreate promotional campaigns in Mailchimp's automation builder or external e-commerce platform post-migration.

Oncord Events with RSVP functionality (part of the Marketing add-on at $40/month) include event name, date, location, capacity, and attendee list linked to Contacts. We export the attendee list as a Mailchimp Tag applied to the corresponding audience members, with the event date preserved as a custom merge field. The event itself does not become a Mailchimp object; instead, we recommend recreating event-based campaigns in Mailchimp Customer Journeys using the attendee tag as the entry condition.

Oncord marketing automation workflows (triggers, conditions, actions, delays) do not migrate as code. The automation models between Oncord and Mailchimp are structurally different: Oncord uses a property-triggered workflow builder with CRM actions, while Mailchimp uses Customer Journeys with entry triggers, time delays, and action blocks. We deliver a written inventory of every active Oncord workflow with its trigger, conditions, actions, and recommended Mailchimp Customer Journey equivalent for the customer's team to rebuild post-migration.

Oncord web forms with their field-to-contact-property mappings export as form definition documentation. Mailchimp's form builder creates signup forms, landing pages, and embedded forms independently. We document the Oncord form structure, required fields, and any custom field bindings so the customer's team can recreate equivalent forms in Mailchimp's builder. Form submissions (historical data) are already captured as Contact records and migrate with the Contact export.

Oncord admin users (unlimited on base plan) export as user records with name, email, and role. Mailchimp does not have a per-user contact ownership model; instead, Mailchimp uses account-level user management with audience-level permissions. We map Oncord admin roles to Mailchimp account roles (Admin, Author, Manager, Viewer) based on the customer's description of each user's access level. Users without an email address are excluded from the migration.