Migrate from WORKetc to Mailchimp

WORKetc Contact records map to Mailchimp Audience members. The Contact's email address is the Mailchimp primary key and dedupe field; we deduplicate on email during the transform phase before any import. Standard fields (First Name, Last Name, Phone, Address) map to Mailchimp's standard merge fields (FNAME, LNAME, PHONE, ADDRESS). The Contact owner assignment does not map — Mailchimp does not have a User-assignment model. Any duplicate email addresses across WORKetc Contacts are resolved by keeping the most recently updated record or merging into a single member with multiple WORKetc source tags.

WORKetc Company records are parent entities linked to multiple Contacts. Since Mailchimp does not have a Company or Account object, we flatten company data into the Contact-level mapping: the Company name becomes the COMPANY merge field on the linked Audience Member, and the Company phone and address append to the member's address data. If a Contact has no individual address but the parent Company does, we promote the Company address. Company-level custom fields migrate as additional merge fields on the member.

WORKetc Lead records map to Mailchimp Audience members, typically placed in a 'New Leads' segment or tagged with the WORKetc lead status value. We preserve the Lead's source, status, and conversion flag as Mailchimp tags (e.g., tag: lead_source=Gallery, tag: status=qualified). If the Lead converted to a Contact in WORKetc, the Contact import takes precedence to avoid duplicate records. We do not migrate unconverted Leads that have no email address — Mailchimp requires an email address for Audience members.

WORKetc custom field definitions and values on Contact, Company, and Lead records map to Mailchimp Merge Fields within the target Audience. We map WORKetc field types to Mailchimp merge field types: text fields to TEXT, date fields to DATE, number fields to NUMBER, and dropdown/multi-select fields to either RADIO or CHECKBOX depending on single versus multi-select. Mailchimp allows up to 40 merge fields per Audience; we flag any migration exceeding this limit and prioritize the most business-critical fields.

WORKetc distinguishes between full Users and Contractor Portal users with different permission scopes. Contractor records without standard email addresses may not be importable to Mailchimp without a valid email. We flag any Contractor records missing an email address and ask the customer whether to exclude them or supply a placeholder email for migration. Contractors who do migrate receive a CONTRACTOR tag in Mailchimp. This separation matters for GDPR and marketing consent contexts.

WORKetc Deals map to Mailchimp as a reference CSV export rather than a live object. Mailchimp has no deal or opportunity tracking. We export Deal records (name, amount, stage, associated Contact, close date) as a separate CSV file delivered alongside the Audience migration. The customer uses this for offline reference or imports it into a separate CRM if needed. Deal stage pipeline names are exported as tags that can be applied to the related Contact if the customer wants to preserve deal context in Mailchimp.

WORKetc Projects with their Types, Stages, and weighted progress values have no Mailchimp equivalent. We export Project records as a separate CSV reference file including Project name, stage, progress percentage, associated Company, and associated Contacts. The Project Types and Stages weighted progress system (where each stage carries a custom percentage weight rather than a simple task-completion ratio) is exported with full stage configuration as metadata so the customer can reconstruct progress logic in their project management tool of choice.

WORKetc support tickets with conversation threads and attachment references export as a separate CSV. Mailchimp does not have a support case or helpdesk object. We export ticket headers (subject, status, priority, linked Contact, linked Company, created date) and deliver the conversation thread content as a separate structured file. The customer admin can import ticket reference data into their helpdesk platform or keep it as an offline archive. Attachment binary files are not migrated unless the destination Mailchimp account has the Content Studio add-on.

WORKetc Workflow rules and automation triggers are not exposed via API and cannot be programmatically extracted. We do not migrate workflows. We deliver a written inventory of every active WORKetc Workflow describing its trigger conditions, actions, and object scope, so the customer's admin can reconstruct the logic in Mailchimp's Customer Journeys or in a dedicated automation tool post-migration. The customer is responsible for rebuilding workflows in Mailchimp Customer Journeys, which uses a different trigger-action model.