Migrate from Oncourse CRM to Mailchimp

Oncourse CRM Contacts migrate to Mailchimp Members within a single consolidated Audience. We map name fields (first_name, last_name), email address (as unique identifier for deduping), phone, and address properties to their Mailchimp Merge Field equivalents. Any Contact-level custom properties migrate as Merge Fields created in the destination Audience before import. Duplicate detection applies at import using email as the dedupe key, with the most recent Oncourse record retained on collision.

Oncourse Leads do not have a direct Mailchimp equivalent because Mailchimp does not distinguish between Leads and Contacts in its data model. All Oncourse Leads merge into the same Audience as Contacts using email as the dedupe key. Lead source and lead status properties from Oncourse migrate as Merge Fields (LEADSOURCE, LEADSTATUS) so the customer's admin can filter and segment based on original lead origin.

Oncourse CRM stores organization name as a Contact property rather than a distinct Account object. We extract this value and create a Mailchimp Tag matching the organization name, applied to every Member whose Contact carries that organization. Tags provide a grouping mechanism equivalent to the organization relationship. Alternatively, if the customer prefers Groups, we create a Group per organization in the Mailchimp Audience.

Oncourse Deals carry name, monetary value, stage, and owner. Mailchimp has no Deal or Opportunity object. We extract Deal records into a written inventory document that the customer's admin can use to create Mailchimp Tags for Deal-related segmentation (for example, Tag with Deal value or Tag with Deal stage name). The inventory includes Deal name, value, stage, owner, and creation date. This is not a data migration; it is a documentation artifact for manual reconstruction.

Oncourse Pipeline Stages are customizable per account and define the sales process. Mailchimp does not support pipeline stages or probability-weighted deal progression. We extract the customer's active stage names and map them to a written Stage Inventory document, with each stage documented for potential Tag-based reconstruction. Tags can be applied to Members who were associated with Deals in specific stages, but this is a manual post-migration step guided by our documentation.

Oncourse CRM Tasks associated with Deals have no Mailchimp equivalent. Mailchimp automations trigger actions but do not maintain a task list linked to contacts. We extract task records (name, status, owner, due date, linked Contact) into a Task Inventory CSV delivered alongside the migration. Customers who rely on task management for sales follow-ups should use Mailchimp's Customer Journeys to automate follow-up emails or integrate a dedicated task tool post-migration.

Oncourse CRM exposes custom properties on Contacts and Leads via DSL export. We map these to Mailchimp Merge Fields created in the destination Audience before data import. Field type mapping follows Mailchimp's supported types: text strings map to text Merge Fields, numeric values map to number Merge Fields, dates map to date Merge Fields, and true/false flags map to address Merge Fields or text fields with validation. Boolean and multi-select custom properties are documented for the admin to configure as appropriate Merge Field types in Mailchimp.

Oncourse CRM does not expose a public file attachment export via its standard import/export tooling. We cannot guarantee attachment migration in automated runs. We recommend a manual backup of the document storage before migration begins. Any attachment references stored as URL fields on Contact or Deal records migrate as text Merge Fields pointing to the original storage location, but the files themselves require a separate file transfer process outside the API scope.