Migrate from GleanView to Mailchimp

GleanView Contact records map to Mailchimp Audience members (type Member). The email address serves as the dedupe key during import. First name, last name, phone, and address fields map directly to Mailchimp's standard address and contact merge fields. Custom properties on GleanView Contacts (such as lifecycle stage, lead source, or industry) are read from the CSV headers and created as Mailchimp merge fields (MAX 255 characters per field) before import begins. Multi-select or rich-text custom properties may require truncation or reformatting.

GleanView Company records do not map to a separate Mailchimp object because Mailchimp has no Account or Company concept. Instead, the company name is stored as a merge field (COMPANY or BUSINESSNAME) on each related Contact's Audience member record. If multiple Contacts share the same company, that company name appears in each member's merge field. Alternatively, the company name can be applied as a tag to all members from the same company for segmentation purposes. The customer chooses the strategy during scoping.

GleanView Lead records map to Mailchimp Audience members in the same way as Contacts. Lead status, source, and owner properties are stored as merge fields or tags in Mailchimp. GleanView's Lead-to-Contact lifecycle is not represented in Mailchimp; all members exist as undifferentiated audience members regardless of their original GleanView status. We preserve the original lead status in a merge field (GV_LEAD_STATUS) for reference.

GleanView Deals (Opportunities) with pipeline stages, deal amounts, close dates, and owners have no equivalent object in Mailchimp. Mailchimp is an email marketing platform and does not manage sales pipeline data. We extract deal records to a CSV inventory, but they do not migrate into Mailchimp. The customer receives a written Deal inventory document listing all open and closed deals with their stage, amount, owner, and close date for manual follow-up in their new CRM or sales tool.

GleanQuote products, bundles, pricing rules, and cost-plus-markup configurations do not map to Mailchimp. Mailchimp has no product catalog or CPQ capability. We document the product catalog in a written inventory including SKU, name, base price, cost, margin, and any formula-driven pricing fields. Formula pricing that computed at render time is flagged separately because those values were not stored as flat values in the CSV export.

GleanQuote proposals, quote headers, and line items have no equivalent in Mailchimp. Quote PDFs stored in GleanSpaces are not included in CSV exports and cannot be automatically migrated. We generate a file manifest listing every linked proposal PDF with its GleanView URL and associated Contact or Deal so that the customer can manually re-upload these if needed in their new quoting tool.

GleanView email logs, calls, meetings, and notes attached to Contacts or Deals do not migrate into Mailchimp. Mailchimp tracks email campaign engagement (opens, clicks, unsubscribes) as a native metric, but GleanView's historical activity timeline has no structural home in Mailchimp. We deliver a written inventory of engagement records grouped by Contact for the customer's admin to reference during any future CRM selection.

GleanView custom fields on Contacts, Companies, and Leads are read from the CSV headers during discovery. We create Mailchimp merge fields matching the custom field names before import. Text fields map to Mailchimp text merge fields (255-character limit). Date fields map to date merge fields. Number and currency fields are stored as text merge fields because Mailchimp does not support numeric merge field types. Fields exceeding 255 characters are truncated with a notation in the field manifest.

GatherSpaces files including proposal PDFs, product images, and content library assets are not included in GleanView's standard CSV export. We generate a file manifest listing every linked file URL, its associated record (Contact, Company, Deal, or Quote), and the file type. The customer re-uploads these manually to Mailchimp's content studio or to a linked document storage tool. We do not migrate binary attachment files.