Migrate from Gold-Vision to Mailchimp

Gold-Vision Contacts map directly to Mailchimp Audience members. Email address is the dedupe key. Standard fields (first name, last name, phone, address) map to Mailchimp merge fields FNAME, LNAME, PHONE, and ADDRESS. Gold-Vision's unlimited custom fields on Contact become Mailchimp merge fields, subject to Mailchimp's limit of 30 merge fields per audience. We flag any overflow fields and recommend tags as an alternative label strategy for low-cardinality overflow fields.

Gold-Vision Accounts do not have a direct Mailchimp equivalent because Mailchimp has no Company or Account object. We carry the Account name as a merge field (COMPANY) on the related Contact record, preserving the organisation context for segmentation. If multiple Contacts share the same Account, they all receive the same COMPANY merge field value.

Gold-Vision Leads map to Mailchimp Audience members with a Lead_Source__c merge field carrying the original lead origin. Lead status and qualification data migrate as merge fields. Note that Mailchimp has no lead qualification workflow; if the team uses Gold-Vision's lead scoring, that score transfers as a merge field and the rebuild of lead scoring logic becomes a post-migration task.

Gold-Vision Campaign records with email send history map to Mailchimp Campaigns. We export campaign member associations (which contacts were sent which campaign) and carry open/click engagement data from Gold-Vision into Mailchimp Member Activity records. Gold-Vision's multi-stage campaign status maps to a text merge field campaign_status__c. Note that Gold-Vision campaign tracking is not equivalent to Mailchimp's send-level campaign tracking; we preserve what exists but do not recreate Gold-Vision's ROI reporting inside Mailchimp.

Gold-Vision Opportunities have no Mailchimp equivalent. We do not migrate Opportunity records. The deal value, stage, and close date are not transferable to Mailchimp's audience model. We flag this during scoping and recommend the customer export Opportunities as a CSV for internal record-keeping. If the team needs to retain Opportunity context, a custom field strategy (deal_value__c as a merge field) can be applied selectively to contacts where appropriate, but this is opt-in based on the customer's data strategy.

Gold-Vision Projects are standalone records with no Mailchimp equivalent. Projects, time entries, and task hierarchies do not migrate. We do not migrate Tickets, Quotes, or Invoices. These are CRM-specific objects outside Mailchimp's scope. The customer should export these as CSVs independently for record-keeping.

Gold-Vision Service Desk Tickets have no Mailchimp equivalent. Ticket records, conversation threads, and agent assignments do not migrate. We do not migrate Tickets. The customer should export ticket history as a CSV if required for compliance or audit purposes before the migration window.

Gold-Vision Quotes carry line items, branding templates, and e-sign metadata. Mailchimp has no quoting object. We do not migrate Quotes. E-sign document URLs from Gold-Vision can be preserved as a text merge field sign_url__c on the related Contact if the customer requests it, but this is an opt-in carryover, not standard scope.

Gold-Vision custom fields on Contact and Account objects become Mailchimp merge fields. We extract the full custom field schema per object during discovery, then map values during import. Mailchimp limits merge fields to 30 per audience; if the Gold-Vision schema exceeds this, we use tags for high-cardinality fields (categorical labels, multi-select values) and recommend the customer select the 30 most operationally critical fields for merge field conversion. The remainder are documented in the handoff deliverable.

Gold-Vision tags and categories applied to Contacts and Accounts migrate directly to Mailchimp Tags on the corresponding Audience members. Tags preserve the organisational taxonomy Gold-Vision users built for segmentation. Mailchimp's tag model is flat (no hierarchy), so any nested Gold-Vision category structure flattens to a single tag name per label. We recommend the customer review tag naming post-migration for consistency.

Gold-Vision communication logs (synced emails, logged calls, appointments from Outlook and Gmail) can be carried into Mailchimp Member Activity records as a historical engagement record. Email open and click events from Gold-Vision campaign sends map to Mailchimp open/click activity. We export the full communication log with timestamps, direction, and body snippet. Note that Mailchimp's activity model is optimised for email engagement; call and meeting logs may be better retained as a CSV export rather than forcing them into the Mailchimp timeline, which is email-centric.

Gold-Vision Users and Owners do not have a Mailchimp equivalent as Admin records. Owner-assigned Contacts carry the Owner name as a merge field (owner_name__c) if the customer requests it. We do not provision Mailchimp user accounts as part of the migration. The customer sets up Mailchimp user access independently of the data migration.