Migrate from Bigin by Zoho CRM to Mailchimp

Bigin Contacts map directly to Mailchimp Audience members. Email address is the dedupe key. Standard fields (First Name, Last Name, Phone, Address fields) map to Mailchimp merge fields FNAME, LNAME, PHONE, and address group fields. We validate email format and flag invalid or missing email addresses before import. Subscribers without a valid email address are held in a reconciliation queue and excluded from the standard migration scope.

Bigin Company records do not have a direct Mailchimp equivalent. We resolve Company-to-Contact linkages and create Mailchimp Tags (one per unique Company name) applied to all Contacts belonging to that Company. If the customer uses Company name for segmentation in campaigns, we alternatively map it to a COMPANY merge field. The customer chooses tag strategy versus merge field during scoping. Company address and industry data do not transfer unless the customer configures additional merge fields in Mailchimp before migration.

Bigin Deals have no Mailchimp equivalent. Mailchimp is an email marketing platform, not a CRM, and does not support pipeline, stage, amount, probability, or close date objects. We exclude Deals from the standard migration scope and deliver a written inventory of all Deals with their stage, amount, owner, and associated Contacts so the customer's admin can export to a spreadsheet or connect to a CRM addon if needed.

Bigin Pipelines are top-level containers for Deals and Stages. Mailchimp has no pipeline concept. We exclude Pipelines from migration scope. If the customer uses Pipeline names or Stages for segmentation in Bigin, we capture these as Tag categories in Mailchimp during scoping, but the Pipeline structure itself is not reproducible in Mailchimp's Audience model.

Bigin Products (catalog items used on Deals) do not map to any Mailchimp object. Mailchimp does not maintain a product catalog. If Products are used for contact segmentation (e.g., 'owns Product X'), we create Tags from Product names and apply them to Contacts associated with Deals containing that Product. The customer confirms this approach during scoping.

Bigin Tasks are standalone to-do items linked to Contacts, Companies, or Deals with due dates, status, and owners. Mailchimp has no task management feature. Tasks are excluded from migration scope. We deliver a task inventory with owner assignments and due dates for the customer's admin to recreate outside Mailchimp or transfer to a project management tool.

Bigin Events are calendar records with start/end times, recurrence data, and attendees linked to CRM records. Mailchimp does not support calendar or event management. Events are excluded from migration scope. Recurring event patterns in Bigin's Bulk Read export are flattened and not preserved as recurrence rules in Mailchimp.

Bigin Call logs store duration, subject, outcome, and recording URL linked to Contacts, Companies, or Deals. Mailchimp has no call logging feature. Call records are excluded from migration scope. If the customer uses call outcome for email segmentation, we create Tags from call outcome values and apply them to the associated Contact record.

Bigin Notes are free-text annotations attached to any record via standard API (not Bulk Read). Mailchimp has no note or annotation feature. Notes are excluded from the standard migration scope. We deliver a written inventory of Notes by Contact with the note body and creation timestamp for the customer's admin to export to a document store or append to a CRM migration in a future engagement.

Bigin custom fields created via the Developer Console with <namespace>__<label> naming map to Mailchimp Merge Fields. We validate the merge field data type (text, number, date, dropdown) and create the corresponding Mailchimp merge field before Contact import. Mailchimp merge fields use uppercase tag names (e.g., INDUSTRY, LEAD_SOURCE). Multi-select custom fields in Bigin become comma-separated text in Mailchimp merge fields unless the customer configures a Tag group for that field during scoping.