Migrate from Unanet CRM by Cosential to Mailchimp

Unanet contact records map directly to Mailchimp subscribers within a designated Audience. The primary email address field becomes the subscriber key used by Mailchimp for identification and deduplication — duplicate email addresses are flagged and surfaced for resolution before the bulk import operation begins. First name, last name, and physical address fields map to Mailchimp's standard subscriber fields without transformation required.

Unanet company name data migrates to Mailchimp's built-in COMPANY merge field on the subscriber record. If multiple companies are associated with a single contact record in Unanet, the primary company becomes the merge field value while additional company associations are preserved as tags formatted as 'Secondary: Company X' for reference and segmentation purposes.

Unanet pursuits track project-based opportunities with stage, probability, and value — Mailchimp has no deal or pipeline concept. These records are exported to CSV for reference and rebuilt manually in Mailchimp's automation sequences if applicable. No automatic translation is possible.

Unanet contact custom fields map to Mailchimp merge fields within the target Audience. Mailchimp allows up to 40 merge fields per audience — fields exceeding this limit or requiring multi-value storage are handled as tags or dropped with explicit disclosure before migration runs.

Unanet contact labels such as 'Decision Maker', 'VIP Client', 'AEC Industry', or other categorization flags migrate as Mailchimp subscriber tags applied to the corresponding subscriber record. Tags are preserved exactly as named in Unanet with uppercase normalization applied for Mailchimp compatibility and searchability. Duplicate tags that would result from the migration are merged during the import process to maintain a clean tag taxonomy.

Unanet contact notes and company notes migrate as Mailchimp notes attached to the subscriber record. The original timestamp and note author are appended to the note body for full traceability back to the source record. Long notes exceeding Mailchimp's 2,000-character limit per note are truncated at that boundary with a reference link included pointing to the full original text location.

Unanet activity logs including calls logged, emails sent, and meetings scheduled have no direct Mailchimp equivalent for this type of historical engagement tracking. Mailchimp tracks campaign engagement metrics including opens, clicks, and unsubscribes on its own timeline starting from first campaign activity. Activity history is exported as a reference CSV file rather than migrated as operational data within the Mailchimp platform.

Unanet proposal automation binds contact and pursuit data to branded templates for submission — Mailchimp has no proposal generation or template-based document automation. Proposal templates are out of scope for migration and must be recreated in a dedicated proposal tool.

Unanet users and owners assigned to contacts and pursuits have no Mailchimp equivalent — Mailchimp subscribers are not assigned to team members. Owner information is exported as a reference merge field but does not function as an assignment mechanism in Mailchimp.

Unanet file attachments (proposals, resumes, project profiles) linked to contacts cannot migrate to Mailchimp — Mailchimp does not store file attachments on subscriber records. Attachments are exported with reference paths and must be re-hosted separately or linked via merge fields pointing to a document management URL.