Migrate from Assured JobCheck to Mailchimp

Salesforce Contact maps directly to Mailchimp subscriber. Each Contact record creates one subscriber in the Mailchimp audience. Email address is the unique identifier and serves as the primary key for import operations. Any duplicate email addresses found in Salesforce are flagged during pre-import validation, and the system de-duplicates before submission. The duplicate detection uses case-insensitive matching to catch variations like [email protected] and [email protected]. The import process preserves the original Salesforce Contact ID in a custom merge field for traceability and future delta synchronization.

Salesforce Account Name migrates as a Mailchimp merge field (COMPANYNAME). Account.Industry maps to a Mailchimp tag. Account hierarchy (ParentId) has no Mailchimp equivalent — parent company name is stored as a second merge field for reference. We also extract the Account.Phone and Account.Website fields as additional merge fields (ACCTPHONE, ACCTWEBSITE) to preserve company-level contact information that may be useful for marketing outreach. For accounts without an industry classification, we apply an 'Unclassified' tag to maintain consistent tagging taxonomy.

The Salesforce Job object has no direct Mailchimp counterpart. We extract Job.Status, Job.Type, and Job.Adjuster__c and merge those values into tags on the related Contact's subscriber record. The job identifier (Job.Name) is preserved as a merge field (JOBIDENTIFIER) linking the subscriber to the originating job. Additional job metadata including Job.Amount, Job.CloseDate, and Job.Priority__c are stored as supplementary merge fields for use in conditional email content. The tag naming convention prepends JOB_ to avoid conflicts with other tag categories.

Adjuster name stored as a Salesforce text field maps to a Mailchimp merge field. The merge field name is truncated to fit Mailchimp's 30-character limit and uppercased. Multiple adjusters on one contact (rare) become pipe-delimited in the merge field or split into separate tags. We also extract the adjuster's email and phone from related contact lookup fields if available, storing them as separate merge fields (ADJUSTEREMAIL, ADJUSTERPHONE) to support marketing follow-ups to the adjuster as a secondary contact point.

Loss type pick-list values in Salesforce (Water, Fire, Mold, etc.) map to Mailchimp tag values. The raw description text becomes a merge field (LOSSDESCRIPTION). We export the full value-mapping table so your Mailchimp segments can filter by loss type tag. For multi-value loss types (e.g., a job involving both water damage and mold remediation), we create separate tags for each loss type and include all in the LOSSDESCRIPTION merge field with comma separation. The value-mapping table includes the original Salesforce pick-list label, the corresponding Mailchimp tag name, and the hex color code used in Mailchimp's tag interface for visual segmentation.

Job status values (Scheduled, In Progress, Completed, Invoiced) map to Mailchimp tags on the subscriber record. We also build a Mailchimp segment definition per status value so you can send job-stage-triggered emails without rebuilding the logic manually. Each segment uses the Mailchimp segment API with tag-includes conditions. We create a master segment called 'Active_Jobs' that includes all statuses except 'Completed' and 'Invoiced' for long-term re-engagement campaigns. The segment definitions are delivered as JSON alongside the mapping documentation for import into your Mailchimp account via the Segments API.

Both fields map directly to Mailchimp merge fields with uppercase naming. These are reference fields only — Mailchimp does not use them for segmentation but they are available in email templates via merge tag syntax. We recommend using these fields in templates for personalized communication such as policy confirmation emails or claim status updates. For contacts with multiple active policies, we create additional merge fields (POLICYNUMBER2, CLAIMNUMBER2) and apply a tag 'MULTI_POLICY' to flag these records for your marketing team's attention.

Decimal currency value migrates as a Mailchimp merge field. The field is stored as a string because Mailchimp merge fields do not enforce numeric formatting — we note this for your email template builder. For templates that require numeric calculations or currency formatting, we recommend using Mailchimp's built-in number formatting functions within your email HTML or leveraging Zapier/Make integrations for post-import formatting. We also create a companion tag 'HIGH_VALUE_CONTENTS' for contents estimates exceeding $50,000 to enable segment-based outreach for premium job opportunities.

Salesforce OwnerId is resolved by email match to a Mailchimp user account. If no match exists, the contact is imported without an owner tag. Owner information is exported as a tag (CSR_ASSIGNED) referencing the owner's name so you can filter by CSR in Mailchimp segments.

Salesforce Campaign membership maps to Mailchimp tags named after the campaign. If a Contact is a member of multiple Salesforce Campaigns, each campaign name becomes a separate tag on the subscriber record. We prefix campaign tags with 'SRC_' to distinguish them from job-status tags and other categories. Campaign member data including CampaignId, CampaignType, and MemberStatus are preserved as additional merge fields (SOURCECAMPTYPE, SOURCECAMPSTATUS) to support more granular segmentation based on campaign origin and engagement level.

Salesforce Tasks and Events have no Mailchimp equivalent. We preserve the last activity date as a merge field (LASTACTIVITY) and the activity type (Call, Meeting, Email) as a tag. Full activity history is exported as a JSON file for reference and potential re-import into a separate CRM.

Salesforce Files attached to Contact or Job records cannot be imported into Mailchimp. We export the file metadata (name, URL, created date) and re-upload photos and documents to Mailchimp's file manager where applicable. Job-related PDFs (contents lists, inspection reports) are noted as requiring separate distribution.