Migrate from Vendasta to Mailchimp

Vendasta Accounts (SMB businesses) do not map to a standalone Mailchimp object because Mailchimp has no Account or Company record. Each Vendasta Account with active contacts is instead represented as a Mailchimp Audience, with the Account name stored as an Audience field or tag. If the customer manages multiple distinct SMB verticals, we create separate Audiences per vertical and document the Audience split logic. Account-level custom fields from Vendasta that cannot map to a standard Mailchimp field are stored as merge fields or Audience tags at migration time.

Vendasta Contacts map to Mailchimp Members within the target Audience. Core field mapping: first_name and last_name from Vendasta Contact.name, email_address from Contact.email, phone from Contact.phone, lifecycle_stage from Vendasta mapped to a Mailchimp merge field (lifecycle_stage__c) or applied as a Member tag for segmentation. We resolve duplicate email addresses during import using Mailchimp's built-in duplicate detection. Contacts without a valid email address are excluded and reported in the reconciliation output.

Vendasta's lifecycle_stage property (subscriber, lead, marketing qualified, sales qualified, customer, evangelist) does not have a native Mailchimp equivalent. We preserve it as a Mailchimp merge field (TEXT, 100 chars) applied to every Member. Additionally, we apply it as a Tag on each Member so the customer can use it in Mailchimp segmentation filters immediately post-migration without waiting for merge field configuration.

Vendasta partner-scoped custom fields on Accounts and Contacts are extracted during discovery, and each is evaluated against Mailchimp's supported merge field types. Text fields under 255 characters map directly to Mailchimp TEXT merge fields. Enumerated fields map to Mailchimp dropdown or radio merge fields with explicit value mapping. Fields exceeding 255 characters are flagged for truncation with the truncation noted in the migration manifest. Fields with no Mailchimp equivalent (multi-select arrays, JSON blobs, partner-specific IDs) are documented and excluded with a reason code.

Vendasta does not expose an explicit opt-in flag on the Contact object via API, but contact creation in Vendasta implies consent within the partner-to-SMB relationship. We export Vendasta Contacts as subscribed Members in Mailchimp. Any Vendasta contact records marked as unsubscribed, bounced, or cleaned are exported as the corresponding Mailchimp status (unsubscribed or cleaned) and imported into the suppression list at migration time to prevent inadvertent re-solicitation.

Vendasta Contacts may carry tags applied by partners for internal segmentation or workflow triggers. Tags migrate to Mailchimp Tags applied to the corresponding Member. Mailchimp Tags are not audience-scoped in the same way as Vendasta partner tags, so we prepend the original partner identifier to tag names where ambiguity exists. The full tag manifest is included in the migration output for the customer to review and rename post-migration if desired.

Vendasta Subscriptions represent recurring billing relationships tied to active product activations. Mailchimp has no subscription object. Active subscriptions are mapped to Member Tags (e.g., tag: active_subscription) or to a subscription_status merge field with values active, paused, cancelled. Cancelled subscription records are flagged but do not generate new Member status changes in Mailchimp because subscription state is a Vendasta billing concept not an email consent concept.

Vendasta Orders contain line items for active Marketplace products (listings, reputation tools, SEO services, advertising). Mailchimp has no order or product activation object, and these line items do not represent email marketing records. We extract the list of active product activations per Contact and apply them as Tags on the corresponding Mailchimp Member (e.g., tag: has_reputation_product, tag: has_seo_product) so the customer's marketing team can segment based on product ownership without rebuilding that logic in Mailchimp from scratch.