Migrate from Olqan to Mailchimp

Olqan Contacts map directly to Mailchimp Members using email address as the dedupe key. We map Olqan firstname and lastname to Mailchimp FNAME and LNAME merge fields, email to EMAIL, phone to PHONE, and lifecycle stage to a Mailchimp custom field olqan_lifecycle_stage__c (created during migration). Any Olqan contact with no email address is flagged for manual review because Mailchimp Members require a valid email.

Olqan Company records do not map to a standalone Mailchimp object because Mailchimp has no Companies or Accounts concept. Instead, we create a Tag per unique Company name and apply it to all Olqan Contacts linked to that company. We also create a custom field company_name__c on Member to preserve the exact company string. Industry and company size from Olqan map to custom fields industry__c and company_size__c if the destination Mailchimp plan supports custom fields.

Olqan Deals have no direct Mailchimp equivalent. We capture the most recent Deal's stage name and value and store them as custom fields on the associated Member record: deal_stage__c and deal_value__c. If the customer used Olqan's pipeline feature heavily, we recommend rebuilding deal-stage segmentation as Mailchimp Tags and Groups post-migration rather than expecting deal values to appear as structured CRM data.

Olqan custom fields on Contacts migrate to Mailchimp custom fields. We detect the Olqan field type (text, number, date, dropdown) and map to the closest Mailchimp field type. Mailchimp merge fields are capped at 255 characters; any Olqan text field exceeding this is truncated with a suffix note, and the full value is stored in a Mailchimp Notes section if available. This is a critical pair-specific gotcha we flag before migration.

Olqan Owners (the CRM user assigned to a Contact or Deal) cannot map to a Mailchimp-native ownership model because Mailchimp does not assign Members to specific users. We create a Tag per Owner name (e.g., tag: assigned-to-jane-doe) and apply it to all Members owned by that user. The customer's Mailchimp admin uses these Tags for internal routing or accountability if needed.

Olqan Tickets track customer support conversations and have no equivalent in Mailchimp. Support ticket data (agent assignments, conversation threads, status, priority) does not migrate. If the customer needs to preserve ticket history, we recommend exporting Olqan ticket records as a CSV for manual reference and setting up a dedicated support tool (e.g., Zendesk, Freshdesk) post-migration.

Olqan Project records contain task hierarchies, time logs, milestones, and assignees. Mailchimp has no project management or task-tracking module. Project data does not migrate. We flag this gap during scoping if the customer's team relies on Olqan's project features and recommend a dedicated project management tool post-migration.

Olqan Employee records store job titles, departments, start dates, manager hierarchies, and payroll data. Mailchimp is not an HR platform and has no employee records. Employee data does not migrate. The customer's HR data remains in Olqan or requires a separate HR platform if they fully decommission Olqan.

Olqan Invoice records contain line items, totals, payment status, and payment terms. Mailchimp has no invoicing or finance module. Invoice data does not migrate. Historical paid invoices retain their original amounts and dates in Olqan's export if the customer needs them for accounting purposes.

Olqan supports Tags on Contact records. We migrate all Olqan Tags as Mailchimp Tags on the corresponding Member record using the same tag name. Mailchimp Tags are additive labels that do not have hierarchy; if Olqan tags have a nested structure, we flatten them into dot-separated tag names (e.g., region.north.enterprise becomes the single tag region.north.enterprise) to preserve the taxonomy without breaking Mailchimp's flat tag model.