Migrate from Insightly CRM to Mailchimp

Insightly Contacts migrate to Mailchimp Members within a primary Audience (list). EMAIL_ADDRESS maps directly, FIRST_NAME and LAST_NAME transfer as standard merge fields, and PHONE transfers as a custom merge field if the audience includes phone number collection. We validate email format before import and flag bounced or invalid addresses for the customer to clean. Contact status (active/inactive) maps to Member status in Mailchimp (subscribed, unsubscribed, cleaned).

Insightly Leads migrate to Mailchimp Members using the same mapping logic as Contacts. Lead source and Lead status preserve as custom merge fields or as Mailchimp tags. The Lead lifecycle (new, contacted, qualified) has no Mailchimp equivalent; we store it as a tag for segmentation purposes rather than a native field.

Insightly Organizations (company-level records) have no Mailchimp equivalent. Mailchimp does not maintain company or account records separate from Members. We do not migrate Organizations as standalone records. If the customer requires company affiliation data, we store it as a custom merge field on the Member (for example, COMPANY_NAME) by extracting the Organization name associated with each Contact via Insightly's link records during the export phase.

Insightly Opportunities (deal records with pipeline stages, probability, and monetary value) have no Mailchimp equivalent. Mailchimp is an email marketing platform and does not track deals, pipeline stages, or deal values. We do not migrate Opportunities. If the customer requires deal-related data in Mailchimp (for example, customer tier or subscription status derived from Opportunity value), we map Opportunity stage or a custom Opportunity field to a Mailchimp tag or merge field during Contact migration.

Insightly Tags (flat string labels applied to Contacts, Organizations, Opportunities, and Projects) map directly to Mailchimp Tags. Tags are preserved as string arrays and imported as Mailchimp tags against the corresponding Member records. Mailchimp tags serve as the primary segmentation mechanism post-migration, so we transfer all tags including those applied to inactive or bounced contacts for full historical preservation.

Insightly custom fields on Contacts and Leads (text, number, date, checkbox, dropdown, multi-select) map to Mailchimp merge fields within the target audience. We retrieve all custom field metadata via Insightly's /CustomFields/Contacts and /CustomFields/Leads endpoints at migration start, then create matching merge fields in Mailchimp via the API before importing any records. Field type mapping follows Mailchimp's supported types: text strings, numbers, dates, and addresses. Insightly multi-select dropdowns map to Mailchimp text merge fields with comma-separated values.

Insightly Tasks (linked to Contacts, Organizations, or Opportunities) have no Mailchimp equivalent. Mailchimp does not maintain task or to-do records. We do not migrate Tasks. If task data contains relevant context (for example, task notes describing customer preferences), we flag those records for manual review and the customer extracts note content separately.

Insightly Notes attached to Contacts and Leads migrate to Mailchimp Member Notes. We extract note body, author, and creation timestamp from the Insightly /Comments API for each Contact and Lead. The note text transfers as a Mailchimp Member Note, preserving the original timestamp and a reference to the original Insightly record ID for audit purposes. Notes attached to Organizations or Opportunities are flagged as unmappable since no parent record exists in Mailchimp.