Migrate from Husky Intelligence to Mailchimp

Every customer and lead record with a valid email address becomes a Mailchimp subscriber. Email is the required unique identifier — records without an email address are flagged before import and excluded by default. First name, last name, phone, and address fields map to Mailchimp's standard merge fields FNAME, LNAME, PHONE, and ADDRESS. Custom properties from the Husky property list become Mailchimp merge fields named in UPPERCASE_WITH_UNDERSCORES format, limited to Mailchimp's ~40 merge-field-per-audience ceiling.

Mailchimp has no native owner or user concept. The Husky Intelligence owner assigned to each customer or lead record is preserved as a custom merge field (labeled OWNER_NAME in your Mailchimp audience) so you can filter or attribute contacts by the rep who managed the account. Owner resolution by email match against existing Mailchimp users is not applicable since Mailchimp does not have an internal user-to-subscriber ownership model.

Husky Intelligence lead source values (referral, website, walk-in, etc.) become Mailchimp subscriber tags prefixed with LS_ (e.g., LS_referral, LS_website). Tags allow segmentation by acquisition channel without consuming a merge field slot. Multiple lead sources on a single record are each added as separate tags rather than collapsed, preserving the full acquisition history.

Mailchimp has no native quote object. Each active quote from Husky Intelligence migrates as three custom merge fields: QUOTE_STATUS (value from Husky's status picklist), QUOTE_AMOUNT (decimal value), and QUOTE_DATE (date of quote creation). Quoted line items are concatenated into a fourth merge field QUOTE_ITEMS as free-text for reference. These fields are informational — Mailchimp does not support quote workflows.

Jobs in Husky Intelligence carry status (scheduled, in-progress, completed), type (repair, installation, inspection), and cost data. These become Mailchimp tags (JOB_scheduled, JOB_completed, etc.) and custom merge fields JOB_STATUS, JOB_TYPE, SERVICE_DETAILS, and JOB_COST. Tag-based segmentation lets you build Mailchimp automations for customers based on recent service history without querying a separate object.

Each Husky Intelligence site associated with a customer becomes a Mailchimp subscriber tag prefixed with SITE_ (e.g., SITE_Main_Warehouse) and the site address stored in SITE_ADDRESS. Sites without an associated customer record are stored as standalone tags against the subscriber record. This preserves location context for field-service-to-marketing segmentation.

Husky Intelligence service agreements with contract status, start/end dates, and tier information are too complex for a single tag. We map contract status as a SERVICE_AGREEMENT tag (AGREEMENT_active, AGREEMENT_expired) and contract start and end dates as custom merge fields SVC_START_DATE and SVC_END_DATE. The full agreement terms are stored as free-text in SVC_TERMS for reference.

Timecard entries in Husky Intelligence are not a real-time reporting use case in Mailchimp. Each subscriber's most recent timecard total hours and date are stored in a custom merge field TIMESHEET_NOTES as free-text (e.g., 'Total 8.5h on 2025-03-15'). Historical timecard records are not individually imported; the summary gives context for customer conversations without overwhelming the Mailchimp contact profile.

Any custom properties added to Husky Intelligence customer or lead records via the property list become Mailchimp merge fields. We apply Mailchimp's naming rules: UPPERCASE, alphanumeric plus underscores, up to 10 characters. Properties with names exceeding these limits are renamed to a truncated equivalent. Merge field values with special characters are sanitized during import. A pre-migration field audit flags properties that exceed Mailchimp's ~40 merge-field-per-audience ceiling.

Mailchimp requires a valid email address for every subscriber record. Husky Intelligence customer or lead records that lack an email address cannot be imported as subscribers. We export these records as a separate CSV for your team to pursue via an alternate channel (phone outreach, list append service, etc.) before or after the main migration.

Husky Intelligence records with an opted-out communication flag or a bounce record are exported and imported into Mailchimp's suppression list rather than as active subscribers. This preserves consent status and prevents accidentally emailing unsubscribed contacts. The suppression list import uses Mailchimp's dedicated bulk-suppression API endpoint.

Husky Intelligence files attached to customer records, quotes, or jobs are not migrated. Mailchimp's contact record does not support file attachments, and there is no standard equivalent for document storage within the platform. Files remain accessible in Husky Intelligence until account closure. We recommend exporting and archiving attachment links before the migration completes.