Migrate from Cirqll to Mailchimp

Cirqll Customer records map directly to Mailchimp Members within the primary Audience. We use the Customer email address as the Member identifier (MD5 hash for Mailchimp's deduplication) and map standard fields: first_name, last_name, email, phone, address (street, city, state/province, zip, country). Any Cirqll custom properties on the Customer record map to Mailchimp merge fields (FNAME, LNAME, PHONE, and custom tags) created in the Audience schema before import. All migrated Customers land as subscribed status unless they appear on the suppression list first.

Cirqll Lead records map to Mailchimp Members within the same primary Audience as Customers, or a separate Audience if the customer configures separate lists for prospects versus clients during scoping. Lead qualification status, source attribution, and owner assignment migrate as merge field data or tags within the Member record. The lead creation timestamp migrates as a custom date merge field for segmentation purposes.

Cirqll Activity records (calls, emails, meetings) attach to the Member record via Mailchimp Tags and merge fields rather than a native activity timeline. We create one tag per activity type (e.g., called_on_2024-03-15, met_at_conference) and record the last activity date as a merge field for segmentation. Mailchimp does not store a full chronological activity log per contact; we warn the customer that historical activity depth is reduced and advise on using Mailchimp's campaign-level open and click tracking as the ongoing engagement signal.

Cirqll free-text Notes attached to Contacts or Leads migrate as Mailchimp Member Notes (up to 65,535 characters). The Note creation timestamp and author attribution migrate as text in the Note body since Mailchimp Member Notes do not expose a created-by field. Notes that reference other Contacts or Leads by name are preserved as plain text links; they do not create cross-member relationships.

Cirqll Tasks (with due date, assignee, priority, and completion status) have no Mailchimp equivalent. Mailchimp is a contact and campaign platform, not a task or project management tool. We export all Tasks to a CSV inventory delivered as part of the handoff package, tagged by Contact or Lead association, so the customer's admin can import them to a task management tool (Asana, Trello, or a standalone CRM) post-migration.

Cirqll Calendar Events (with date, time, title, attendee list, and recurrence flags) have no Mailchimp equivalent. We export all Calendar Events to a structured CSV with event title, start/end datetime, attendee email addresses, and recurrence data. The customer uses this inventory to rebuild events in their preferred calendar or scheduling tool.

Cirqll Documents are binary attachments stored separately from CRM records and not accessible via the standard API endpoints. We flag document export as a secondary pass during scoping and deliver a CSV inventory of document filenames, associated Contact or Lead, upload date, and file size. The customer manually re-uploads documents or uses a file hosting tool (Google Drive, Dropbox, SharePoint) post-migration.

Cirqll User accounts (owners assigned to Leads, Tasks, and Activities) do not map to Mailchimp Users because Mailchimp's contact-centric model does not assign record ownership at the individual user level. User names and email addresses associated with Cirqll Notes and Activity records are preserved as text in the Note body or as merge field data on the Member. If the customer requires user-based assignment tracking post-migration, we recommend a separate CRM or project management tool.