Migrate from Vtiger Sales to Mailchimp

Vtiger Contact records map to Mailchimp Audience members as the primary migration object. Email address is the dedupe key. Standard Contact fields (first name, last name, phone, address) map to Mailchimp merge fields FNAME, LNAME, PHONE, and ADDRESS. Custom Contact fields map to additional merge fields created in the target Audience, typed by data type (text, number, date, dropdown). The Contact's linked Organization is resolved separately and stored either as an ORGANIZATION merge field or as a tag on the member, depending on the organization's segmentation strategy chosen during scoping.

Vtiger Leads require a migration status decision because Mailchimp has a single member model versus Vtiger's separate Lead and Contact objects. Leads can be imported as subscribed members (if the lead source implies consent), as pending members (if the lead was collected without confirmed opt-in), or archived with a note. We recommend importing as pending for leads sourced from inbound forms and subscribed for leads from confirmed event attendance or direct sign-ups. The original lead source and lead status from Vtiger are stored as merge fields for segmentation in Mailchimp.

Mailchimp has no Organization or Account object; company-level data must be represented differently. We recommend storing the Vtiger Organization name as an ORGANIZATION merge field on the linked Contact records. For segmentation by company, we create a tag named after each Organization and apply it to all Contacts belonging to that Organization. This preserves the organizational relationship for filtering without creating a separate entity in Mailchimp. If the customer uses Organization for territory or industry classification, those fields also map to tags or merge fields during this step.

Deals (Potentials) track pipeline stage, amount, and probability in Vtiger. Mailchimp has no deal or opportunity object. For migrations where deal context is commercially sensitive, we tag the linked Contact records with the deal stage (e.g., tag: DealStage_Prospecting, tag: DealStage_ProposalSent) and store deal amount and close date as merge fields on the contact. We do not create a parallel deal record in Mailchimp. Instead, we deliver a written Deal inventory listing every Vtiger Deal with its stage, amount, linked Organization, and linked Contact so the customer's admin can manage deal context through a CRM or spreadsheet outside Mailchimp.

Vtiger custom fields on Contacts, Leads, and Organizations map to Mailchimp merge fields. We create merge fields in the destination Audience using the same field label and a normalized merge tag (uppercase, underscores, max 10 characters). Data types are mapped: Vtiger text and phone become Mailchimp text; Vtiger date becomes Mailchimp date; Vtiger picklist becomes Mailchimp radio or dropdown; Vtiger multi-select becomes Mailchimp text (comma-separated). Mailchimp caps merge fields at 40 per Audience, which we flag during scoping if the customer's field count approaches this limit.

Vtiger global tags applied across modules (Contacts, Organizations, Leads, Deals) migrate to Mailchimp audience tags. We extract every distinct tag value from the Vtiger database, deduplicate the tag namespace, and apply matching tags to the corresponding Mailchimp audience members during import. Tag-to-member assignments are written as batch operations against the Mailchimp Members API. Tags are case-sensitive in Mailchimp, so we normalize during the transform step to avoid creating duplicate tags like 'VIP' and 'vip'.

Vtiger User records include name and email for the assigned record owner. We map owner assignments to a Mailchimp merge field OWNER_EMAIL on the member record, or to a tag OWNER_[name] if segmentation by sales rep is needed. Mailchimp does not have a CRM-style owner model; ownership is informational in this context. We resolve each Vtiger User by email and store the resolved name as a merge field. If the destination Mailchimp account has multiple Admin users, we recommend mapping the owner's Mailchimp admin role during the post-migration onboarding call.

Vtiger Quotes are document objects linked to Deals, Contacts, and Organizations. Mailchimp has no quote or proposal object. We do not create quote records in Mailchimp. We deliver a written Quote inventory listing every Vtiger Quote with its linked Contact, Organization, line items, total amount, status, and validity dates so the customer's admin can follow up on pending quotes outside Mailchimp's campaign environment.