Migrate from JobTread to Mailchimp

JobTread Customer records map 1:1 to Mailchimp Subscribers. Each customer with a valid email address becomes one subscriber record. Customers without email addresses are flagged for manual review — Mailchimp requires an email address as the unique identifier for every subscriber.

JobTread stores full_name as a single field. FlitStack splits the compound value on the last space into First Name and Last Name for Mailchimp's standard FNAME and LNAME merge fields. Customers with single-word names populate FNAME and leave LNAME blank.

Email serves as the primary key in Mailchimp's architecture and acts as the unique identifier for deduplication across all subscriber records. FlitStack validates email format using strict RFC 5322 pattern matching before any data loads into Mailchimp — addresses that fail validation are captured in the pre-migration audit report, flagged as invalid, and excluded from the initial bulk load to prevent bounce-back issues and maintain list hygiene from migration day forward.

Phone numbers from JobTread migrate directly into Mailchimp's PHONE merge field using a standardized format. When JobTread stores mobile and office numbers in separate fields for a single customer, FlitStack concatenates both values into one PHONE field with a delimiter for clarity. This ensures all contact电话号码 remain associated with the subscriber record and available for any future SMS or phone-based outreach configured within Mailchimp's platform.

JobTread's structured address components — street, city, state, postal_code, and country — map to Mailchimp's structured ADDRESS merge field using its required addr1, city, state, and zip subfields. The addr2 subfield and country subfield are optional in Mailchimp but get populated automatically when those values exist in the corresponding JobTread address fields, preserving the complete physical location data for each subscriber throughout the migration.

Mailchimp does not offer a native Company or Account object in its data model, so company names extracted from JobTread must be stored as custom merge field data attached to each Subscriber record. FlitStack creates a Company__c custom merge field and writes the JobTread company name value onto every subscriber belonging to that company. When one JobTread company has multiple associated customer contacts, each subscriber receives the identical Company__c value, maintaining the company relationship association across your entire Mailchimp audience.

JobTread Job records are not native Mailchimp entities. We store the most recent Job Name in a JobName__c custom merge field. Job status values (Proposal, Active, Won, Lost, Completed) are applied as Mailchimp Tags — one tag per job status — enabling segmentation by project lifecycle directly in Mailchimp.

Estimated budget amounts from JobTread migrate to a JobBudget__c merge field. Mailchimp merge fields accept text values up to 255 characters — currency amounts are stored as strings (e.g., '$24,500') rather than numeric to preserve formatting. Large budgets exceeding 255 characters are truncated and flagged.

Mailchimp does not host files. Attachments on JobTread Customer or Job records (proposal PDFs, change-order documents, photos) cannot be stored in Mailchimp. FlitStack exports a manifest of all attachment URLs from JobTread as a reference CSV — your team stores files in a separate tool (Google Drive, Dropbox) and links to them in Mailchimp campaigns manually.

JobTread Workflows trigger on job-status changes, date-based reminders, and field-update conditions. Mailchimp has no construction-workflow engine — automation triggers are email-open and click-based. Workflow definitions must be rebuilt as Mailchimp Customer Journeys (Standard or Plus plan) or abandoned. FlitStack exports workflow definitions as a JSON reference for your Mailchimp admin.