Migrate from Glaze CRM to Mailchimp

Glaze CRM Contact records map to Mailchimp Audience members. The email address is the primary key and subscribe status is set based on the contact's opt-in flag in Glaze CRM. First name, last name, phone number, and any standard address fields map directly. We resolve the company association (Glaze CRM Company lookup) to a Merge Field rather than a related object because Mailchimp has no Account concept. If Glaze CRM stores multiple contacts per company, each becomes a separate Audience member.

Glaze CRM Lead records and Contact records merge into a single Mailchimp Audience. We apply a dedupe strategy: if the same email address appears in both Lead and Contact objects, the Contact record takes precedence and the Lead record is suppressed. Lead-specific fields (lead source, lead status, lead score if present) migrate as Merge Fields. Lead owner assignment does not transfer because Mailchimp has no user-ownership model for audience members.

Glaze CRM Company records do not have a direct Mailchimp equivalent. We extract the company name from the Contact or Lead's associated Company lookup and write it to a Merge Field (typically named COMPANY or COMPANY_NAME) on the Audience member record. Full company address, industry, employee count, and other Company fields cannot be represented in Mailchimp's schema without custom Merge Fields; we recommend a selective approach where only the company name is mapped unless the customer specifies additional fields during scoping.

Glaze CRM custom fields on Contacts and Leads map to Mailchimp Merge Fields. We infer field type from sample data: text fields become Mailchimp TEXT merge fields, date fields become DATE merge fields, numeric fields become NUMBER merge fields, and dropdown or single-select fields become either RADIO or DROPDOWN merge fields. Multi-select fields require special handling — we concatenate selected values into a single TEXT merge field string. Merge Field tags must follow Mailchimp's TAG naming convention (uppercase, alphanumeric, underscores). We create Merge Fields via the Mailchimp API before any member import begins.

Glaze CRM tags on Contacts and Leads map directly to Mailchimp Tags on the corresponding Audience member. Tags are applied via the Mailchimp Tags API after the member record is created or updated. Glaze CRM tags with hierarchical naming (e.g., industry-retail, segment-enterprise) are preserved as flat strings and reapplied as-is. If a contact has more than 50 tags, we flag this during scoping because Mailchimp's UI becomes unwieldy with high tag counts.

Glaze CRM Deals have no Mailchimp equivalent. Mailchimp has no opportunity, deal stage, or pipeline concept. We do not migrate Deal records. We document every Deal field (deal name, amount, stage, expected close date, owner) in a written inventory delivered to the customer so they can decide whether to export to a spreadsheet or accept loss. If the customer uses Mailchimp's paid plan with a connected CRM integration, they can rebuild deal context in the connected CRM after migration.

Glaze CRM Pipeline configurations (stages, probabilities, automations per stage) do not transfer to Mailchimp. We document the existing pipeline stages and probability weights in a written handoff document. If the customer needs pipeline visibility, they should consider connecting Mailchimp to a lightweight CRM (HubSpot Free, Zoho Free, or the native Mailchimp CRM on Essentials+) post-migration.

Glaze CRM Tasks (subject, due date, assignee, linked entity) have no Mailchimp equivalent. We do not migrate task records. Completed vs. open status is a CRM concept that Mailchimp does not model. We document the task inventory in the written handoff so the customer can plan a rebuild in their chosen task management tool (Asana, Trello, a connected CRM) post-migration.

Glaze CRM document attachments (file metadata: filename, upload date, linked record) cannot be stored on Mailchimp Audience members. We document the document inventory separately and flag that file binaries require separate handling through Glaze CRM's file export process if needed. This work is outside standard migration scope.

Glaze CRM Users representing team members who own deals or tasks have no Mailchimp equivalent. Mailchimp's user model is account-level (users who log in and send campaigns), not record-level (users who own individual contacts). Owner assignments from Glaze CRM are documented as a reconciliation list delivered to the customer's admin for manual assignment in their chosen post-migration system.