Migrate from Insightly Marketing to Mailchimp

Insightly Contacts map to Mailchimp Audience members. We use email address as the dedupe key during import and merge Insightly contact properties (name fields, phone, address, custom fields) into Mailchimp's contact profile. Insightly's lifecycle stage and lead status migrate as merge field values rather than native Mailchimp fields. We flag any contacts with duplicate email addresses for manual resolution before final import.

Insightly Organizations map to Mailchimp Companies if the destination Mailchimp account is on Plus or Premium tier (which includes the Companies feature). On Standard or Essentials tier, Organization name and domain can be stored as merge fields on the Contact record. We check the destination tier during scoping and adapt the mapping accordingly. Organization-to-Contact relationships are preserved by linking each Contact to its parent Organization record in Mailchimp where the tier supports it.

Insightly Leads that do not yet have a corresponding Contact record migrate as Mailchimp Audience members in the subscriber or prospect segment. We preserve Lead_Status from Insightly as a merge field value for segmentation in Mailchimp. Any lead scoring values from Insightly custom fields migrate as merge fields that can be used in Mailchimp's audience filtering.

Insightly Tags applied to Contacts, Organizations, and Leads migrate to Mailchimp Tags. Each unique tag name creates a corresponding Mailchimp tag. We preserve the tag count per contact for segmentation but note that Mailchimp tags are flat (no tag hierarchy) whereas Insightly tags can be scoped per object. If the customer uses Insightly tag categories for organizational purposes, we document those categories as part of the migration deliverable for manual reconstruction in Mailchimp as segment groups or labels.

Insightly custom fields on Contacts (beyond the standard set of first name, last name, email, phone, address) migrate to Mailchimp merge fields. We map Insightly field types to Mailchimp merge field types: text fields become text merge fields, date fields become date merge fields, numeric fields become number merge fields, and picklist fields become dropdown merge fields. We flag any custom fields with validation rules that may restrict values importable into Mailchimp's merge field format.

Insightly custom field groups are named expandable sections that group related custom fields. Mailchimp does not have an equivalent grouping concept for merge fields. We flatten the field group structure and apply a naming convention (GroupName_FieldName) to preserve the original grouping information within the merge field label. This keeps the information accessible without requiring structural recreation.

Insightly email templates export in a non-standardized format that cannot be directly imported into Mailchimp. We extract the HTML content, inline styles, and image references from each template and provide the customer with a written template inventory documenting the layout structure, content blocks, and design elements. The customer rebuilds templates in Mailchimp's campaign builder or imports the cleaned HTML if Mailchimp's template import supports it for that specific format. We preserve template content and imagery where possible but advise budgeting for template reconstruction time.

Insightly campaign history (sends, opens, clicks, bounces) represents historical email engagement data. Mailchimp does not import Insightly's campaign performance metrics. We document the Insightly campaign names, send dates, and audience sizes as part of the migration deliverable so the customer has a record of historical campaign activity. Ongoing campaign metrics will populate in Mailchimp after cutover.

Insightly Opportunities have no equivalent in Mailchimp's audience model. Mailchimp is an email marketing platform and does not track pipeline stages, deal values, or probability. We document the Opportunity fields in use during scoping and flag the fields that will not migrate. If the customer needs Opportunity data, it must be retained in Insightly CRM (a separate license), moved to a dedicated CRM, or recorded in a spreadsheet.

Insightly Projects (with milestones, task lists, and assignees) are outside Mailchimp's scope. Mailchimp does not have a project management or task management capability. We document the Project records in use during scoping. If project tracking is needed, the customer should retain Insightly CRM for project management or select a separate project management tool.