Migrate from LeadTrac to Mailchimp

LeadTrac leads map 1:1 to Mailchimp audience members. Email address is the unique key for de-duplication. Leads without an email address are flagged for manual review since Mailchimp requires a valid email for subscriber records. The LeadTrac record ID is stored in a LEADTRAC_ID__c custom field on the Mailchimp audience member. Leads flagged for manual review appear in a separate export file for your team to resolve.

LeadTrac contacts map to Mailchimp audience members using email as the primary identifier. Contact records with a company association map the company name to Mailchimp's COMPANY merge field. Multiple contacts sharing one email collapse to a single audience member. When multiple LeadTrac contacts share the same email, the migration selects recent values, ensuring data appears in Mailchimp. The contact type (Client, Prospect) is stored in a CONTACT_TYPE__c custom field.

LeadTrac's lead status picklist values (New, Contacted, Qualified, Converted, Lost) become Mailchimp tags prefixed with the original status name (e.g., Status_New, Status_Contacted). The final status is also written to a LEAD_STATUS__c custom field for reference filtering. These tags are applied automatically during migration and can be used in Mailchimp segmentation rules to target leads at specific stages. The LEAD_STATUS__c field also enables API‑driven queries and reporting based on lead progression.

LeadTrac's lead source field (Website, Referral, Trade Show, etc.) migrates as Mailchimp tags (Source_Website) and as a SOURCE__c custom field on the audience member. Source attribution timestamps are preserved in a separate SOURCE_DATE__c custom field. The SOURCE__c field stores the raw source value for API queries, while SOURCE_DATE__c records when the source was first recorded. Together they enable you to analyze which channels produce the highest engagement over time.

LeadTrac company records associated with a contact migrate to Mailchimp's COMPANY merge field. When a LeadTrac contact has no company name, the COMPANY field is left blank — no Account object equivalent exists in Mailchimp. If a contact lacks a company name, FlitStack records the blank value for later enrichment via a third‑party data service. Company data can be used in Mailchimp segmentation to target contacts by organization.

LeadTrac notes attached to a lead or contact migrate as Mailchimp notes on the corresponding audience member. Notes preserve the original author name, creation timestamp, and full text body. Note ordering in Mailchimp is chronological by create date. This allows your team to view the communication history within Mailchimp, facilitating personalized outreach based on prior interactions. Note length is limited to Mailchimp's 2,000‑character limit; longer notes are truncated and flagged.

LeadTrac PDF agreements, settlement documents, and DocuSign-enriched files have no Mailchimp equivalent. FlitStack exports these as a ZIP archive keyed by contact email for manual distribution. Rebuilt document management requires a separate tool. The ZIP archive preserves folder hierarchy and file names, allowing you to re‑associate documents with contacts after download. Document metadata (e.g., file size, creation date) is included in a companion CSV for reference.

LeadTrac case records (common in debt settlement and legal CRM usage) have no Mailchimp equivalent. Case status, balance amounts, and settlement data are exported as a CSV reference file but do not map to Mailchimp objects — those workflows must be rebuilt outside Mailchimp.

LeadTrac appointments associated with a contact migrate as Mailchimp tags (Appointment_Scheduled, Appointment_Completed) with the appointment date written to a custom field APPOINTMENT_DATE__c. The actual scheduling functionality is not transferred. These tags let you filter contacts based on upcoming or past appointments, enabling targeted email reminders. The APPOINTMENT_DATE__c field can be used in automation to trigger messages relative to the appointment date.

LeadTrac custom properties (beyond name, email, phone, status) migrate to Mailchimp custom fields of the corresponding type (text, number, date, or radio button). Fields exceeding Mailchimp's 30-field limit on Standard plans are flagged for Premium provisioning or selective mapping before migration.

LeadTrac owner assignment migrates as a OWNER_EMAIL__c custom field on the Mailchimp audience member. If the owner email matches a Mailchimp account user, the Owner_Tag is applied for segmentation. No equivalent to LeadTrac's full user-permissions model exists. The Owner_Tag enables you to assign contacts to specific team members for follow‑up, while the custom field stores the original LeadTrac owner email for audit purposes. Multi‑owner scenarios are represented as additional tags.

LeadTrac SMS communication logs migrate as notes with the SMS body text preserved. Mailchimp Marketing SMS is a separate product with different contact lists — two-way SMS conversations cannot be recreated in Mailchimp without a third-party integration. FlitStack exports SMS logs as a CSV file that includes timestamps, direction (inbound/outbound), and message content, which can be stored for compliance purposes. For SMS activity, consider integrating an SMS platform after migration.