Migrate from Gauss Box CRM & Sales to Mailchimp

Gauss Box Contacts map to Mailchimp Members. The email address is the dedupe key. First name, last name, phone, address, and any custom attribute-set fields map to Mailchimp's standard fields (FNAME, LNAME, PHONE, ADDRESS) or to custom merge fields we create in the destination Audience during migration. Contact status (active/inactive) from Gauss Box maps to a Member status merge field since Mailchimp Members always default to subscribed status during import.

Gauss Box Organizations have no direct Mailchimp equivalent. Organization name maps to a COMPANY merge field on the Member record. If a single Contact in Gauss Box is linked to multiple Organizations, we store primary organization as COMPANY and secondary organizations as tags (format: org:{name}). Industry, size, and D&B data fields from Gauss Box become custom merge fields if they exist on the Contact record, or remain unmapped if they exist only on the Organization object without a Contact linkage.

Gauss Box Leads map to Mailchimp Members in a separate Audience or a tagged segment within the primary Audience, depending on whether the customer wants to keep marketing-qualified leads and marketing-raw leads separate. The lead work status from Gauss Box (e.g., new, contacted, qualified) maps to a custom merge field LEAD_STATUS to preserve the original qualification stage. HubSpot's typical lifecycle-stage logic does not apply here; the mapping is driven by whatever status values exist in the customer's specific Gauss Box attribute set.

Gauss Box attribute-set custom fields on Contacts, Organizations, and Leads have no standardized names across accounts. During discovery we enumerate every active attribute set and map each field to a Mailchimp custom merge field with an appropriate type (text, number, date, dropdown to radio, checkbox to text). Mailchimp limits merge fields to 40 characters in the tag name and 255 characters in value length. Long-text Gauss Box attributes are truncated to 255 characters with a warning flag in the migration report. Merge fields are created per Audience, so multi-Audience structures require the same attribute set to be mapped in each Audience.

Gauss Box Deals (with pipeline stages, values, budget, and product associations) have no equivalent in Mailchimp. Mailchimp has no opportunity, pipeline, stage, or deal-value object. We exclude Deals from migration scope. We deliver a written inventory of all Gauss Box Deals (stage, value, owner, associated products) as a CSV so the customer's admin can import them into a separate CRM if needed, or retain the list for manual reference.

Gauss Box Activities (interactions linked to Deals and Contacts) have no Mailchimp equivalent. Mailchimp tracks campaign-level engagement (opens, clicks, unsubscribes) but not individual sales interaction records. We exclude Activities from migration scope. For contacts that have email address history within Activities, we capture the associated email addresses as Members in the Audience if they are not already present, but we do not migrate the interaction metadata itself.

Gauss Box Products (with category, type, price, and tax configuration) have no Mailchimp equivalent. Mailchimp supports product catalogs for abandoned-cart automation in e-commerce integrations but does not store standalone product records as a migration target. We exclude Products from migration scope. If the customer uses Mailchimp's e-commerce integration (Shopify, WooCommerce), the product catalog lives there, not in the contact migration. We note this in the scope document and flag any deal-product associations that will be lost.

Gauss Box documents attached to Contacts, Organizations, and Deals have no equivalent in Mailchimp. Mailchimp does not support file attachments on Member records. We exclude document migration from scope. We deliver a file listing of all Gauss Box documents (filename, record type, record ID) as a written inventory so the customer's admin can assess whether the documents should be archived externally, re-uploaded to a Google Drive or SharePoint structure, or re-linked in a CRM that supports document management.

Gauss Box Owner assignments on Deals, Leads, and Activities do not map to Mailchimp because none of those objects migrate. Contact owner assignments from Gauss Box are not stored as Member fields in Mailchimp. If the customer wants owner attribution preserved (e.g., which sales rep owns which contact), we map the Gauss Box owner email to a custom merge field OWNER_EMAIL on the Member record. Mailchimp's built-in User management (for team accounts) is a separate permission model unrelated to contact ownership.