Migrate from YetiForce CRM to Mailchimp

YetiForce Contacts map directly to Mailchimp Audience members. The primary key is email address, which serves as the unique identifier in Mailchimp. We extract contacts using YetiForce's CSV Export or API (with batch chunking due to the lack of bulk endpoints in Webservice Standard), deduplicate by email, and import via Mailchimp's Bulk API. Phone number, address, and custom field values migrate to Mailchimp contact fields or merge fields if the plan supports them. Contact status (active/inactive) maps to subscriber status in Mailchimp.

YetiForce Organization records map to Mailchimp Companies (available when Mailchimp CRM features are enabled on the account). Organization name maps to Company name, industry maps to Industry, website maps to Website, and address fields map to the Company address object. Organizations must be imported before Contacts if the customer wants contact-company associations, since the Company ID serves as the lookup key on the contact record. Mailchimp Companies are optional; if CRM features are not enabled, Organizations do not migrate.

YetiForce Leads map to Mailchimp Audience members with a Lead_Source custom field or tag capturing the original lead source value. Lead status is preserved in a custom field or tag. Mailchimp does not have a separate Lead object equivalent to Salesforce's Lead-Contact split; all prospects live in the Audience. We tag Leads to distinguish them from Contacts during import, allowing segmentation in Mailchimp without requiring a separate CRM.

YetiForce Potentials (deals) map to Mailchimp Opportunities when Mailchimp CRM features are enabled. Potential name maps to Opportunity title, amount maps to Opportunity value, close date maps to Expected Close Date, and sales stage maps to Pipeline stage. Potentials tied to an Organization require the Organization to be imported first so that the Company ID lookup is satisfied. Mailchimp Opportunities do not support custom fields in the same way as full CRMs; we map the most critical fields and store additional metadata in tags.

YetiForce Users cannot be migrated as user records since Mailchimp's team management model is entirely different. We resolve Users by email address against the destination Mailchimp account's team members list and flag any YetiForce Users without a corresponding Mailchimp account for the customer's admin to provision. Owner assignments on Contacts, Organizations, and Potentials map to Mailchimp Tags or custom fields if the destination Mailchimp account supports the CRM features.

YetiForce contact-level custom fields map to Mailchimp merge fields (text, number, date, address, phone) for structured data, and to Tags for categorical data. Merge fields require configuration in Mailchimp before import; we create them via the Mailchimp API during the schema preparation phase. Fields with picklist values in YetiForce map to Mailchimp Tags or to a pre-configured custom interest group. Fields with no Mailchimp equivalent are flagged for the customer's admin to decide on disposition.

YetiForce file attachments stored in the file system do not migrate to Mailchimp because Mailchimp does not have a file attachment model on contact records. We extract attachment metadata (file name, linked record ID, upload date) and write it to a CSV inventory delivered alongside the migration. The customer's admin can re-attach relevant files manually post-migration if needed. PDF documents linked to Potentials or Organizations are included in the same inventory.

YetiForce Tickets have no Mailchimp equivalent. Mailchimp is an email marketing platform and does not include helpdesk functionality. Ticket data (title, status, priority, category, related contact and organization references) is extracted to a CSV inventory with a count of records and a field-by-field column listing. The customer's admin receives this inventory as a reference for rebuilding ticket context in a dedicated helpdesk platform if needed. We do not migrate ticket conversations as they require a ticketing system context.