Migrate from Teleforce CRM to Mailchimp

Teleforce Contact records map directly to Mailchimp Audience Members by email address as the primary key. First name, last name, phone, and address fields map to Mailchimp's standard ADDRESS and PHONE merge fields. We de-dupe on email during import — if a contact appears twice in the Teleforce export, the first record by creation date wins unless the customer specifies a preferred supersession rule. Active vs archived status in Teleforce determines subscription status in Mailchimp (subscribed, unsubscribed, or cleaned).

Teleforce Companies do not map to a native Mailchimp object because Mailchimp has no account hierarchy. We handle this as a configuration decision during scoping: either Company names become Mailchimp Tags (one tag per company, applied to all contacts at that company), or Company data populates a text merge field on each Contact. The customer chooses the strategy. We recommend tags if company-level segmentation is used in Teleforce; we recommend merge fields if individual contact records need to retain the company reference.

Teleforce custom fields on Contacts map to Mailchimp Merge Fields on the target Audience. We match on field label and infer type: text fields map to Mailchimp text merge fields, numeric fields to number merge fields, date fields to date merge fields, and phone fields to phone merge fields. The customer must provide a complete list of Teleforce custom field definitions during discovery because the export mechanism for field metadata is not confirmed. Merge field tags are generated from the field label (uppercased, spaces removed) following Mailchimp naming conventions.

Teleforce Leads appear to be a distinct object or lifecycle stage but the exact schema is not publicly documented. We treat Leads as a separate export from Contacts during scoping and import them as Audience Members with subscribed status (or the equivalent status flag the customer specifies). Any lead-to-contact conversion logic in Teleforce is not migrated as automation — we document the conversion logic in writing so it can be replicated as a Mailchimp segmentation filter or Customer Journey trigger.

Teleforce Deals (pipeline opportunities) have no equivalent in Mailchimp. Mailchimp does not track deal stages, revenue amounts, or pipeline boards. We do not migrate Deals. We deliver a written inventory of all open Deals with stage, value, owner, and close date so the customer's team can decide whether to track these in a separate spreadsheet, a dedicated CRM (HubSpot, Pipedrive, or similar), or within Mailchimp's Notes and Tags if the volume is small enough for manual management.

Teleforce Pipelines group Deals into stage-based boards with visual Kanban layout. Mailchimp has no pipeline or deal management object. Pipelines are not migratable. We document the pipeline name, stage names, stage order, and stage probability for each Pipeline so the customer's team can reference it during rebuild in a CRM if needed.

Teleforce Activity records (call logs, email threads, SMS threads, chat history) linked to Contacts via the unified inbox are not confirmed as independently exportable and have no Mailchimp equivalent. Mailchimp tracks campaign send history and automation trigger logs per subscriber, but not inbound call records or chat transcripts. We flag activity data as not migratable upfront and document the customer's activity volume estimate so the team can assess whether historical activity matters for the Mailchimp use case.

Teleforce Owner records (sales reps assigned to Contacts, Companies, and Deals) have no equivalent in Mailchimp's audience model. Mailchimp does not support per-record owner assignment. Owner email addresses from Teleforce can be mapped to a merge field if the team wants to retain a reference to which rep owns each contact, but this is informational only. We flag this as a configuration choice during scoping.