Migrate from Perfectview to Mailchimp

PerfectView Relations combine company and individual contact data. We split each Relation into one primary Mailchimp contact (the primary contact within the Relation using address-type fields and role designation) plus additional contacts for each additional individual with an email address in the Relation. The original Relation name becomes a Mailchimp merge field (RELATION_NAME) and the Relation type becomes a Mailchimp tag for grouping. Relation custom fields map to Mailchimp merge fields of equivalent type (text, date, number). We validate email address format before import to prevent hard bounces on the Mailchimp API.

Where a Relation contains multiple individuals with distinct email addresses, each individual becomes a separate Mailchimp contact. Role designation (Decision Maker, Influencer, User) migrates as a merge field. The individual's name, email, phone, and address fields map directly to Mailchimp's FNAME, LNAME, EMAIL, PHONE, and ADDRESS merge fields.

Company data embedded in a Relation has no direct Mailchimp object equivalent. Company name migrates as a merge field (COMPANY). Industry, employee count, and revenue data become additional merge fields. Company-based segments in PerfectView map to Mailchimp Tags (e.g., Industry tags or territory tags) so that campaigns can still be filtered by company attributes.

PerfectView Leads (if present as distinct from Relation-based leads) migrate as Mailchimp contacts with a LEAD_STATUS merge field and a 'Lead' tag. Lead source data becomes a merge field. Lifecycle stage values from PerfectView map to a merge field rather than Mailchimp's subscriber status, since subscriber status is a system field controlled by double opt-in and unsubscribe actions.

PerfectView Activities (calls, emails, meetings, tasks) have no Mailchimp equivalent. Mailchimp tracks email engagement (opens, clicks, unsubscribes) natively but does not store CRM-style activity timelines. We do not migrate Activities. Instead, we deliver a written inventory of activity counts per Relation so the customer can assess whether to archive the data in a document store or exclude it from migration scope.

PerfectView Cases have no Mailchimp equivalent. Mailchimp does not support helpdesk or support ticket functionality. We deliver a case count and status summary as a written inventory document for the customer's admin to determine what to archive.

PerfectView Quotes do not migrate to Mailchimp. Mailchimp has no quoting or pricing module. We deliver a written count of Quote records with line-item summary so the customer can decide whether to export as CSV to a document store or handle via a separate quoting tool integration post-migration.

PerfectView Document storage has no Mailchimp equivalent. Mailchimp supports template attachments and file hosting for email campaigns but not a general document repository. We deliver a written document inventory (file count, types, Relation associations) for the customer to archive separately or link via an external document management integration.

PerfectView custom fields on Relations map to Mailchimp merge fields. Text fields map to Mailchimp text merge fields; date fields to date merge fields; number fields to number merge fields; dropdown fields to radio merge fields. We pre-create all merge fields in the Mailchimp Audience before importing contacts. Merge field names are truncated to the Mailchimp maximum of 30 characters and sanitised of special characters.

PerfectView Owner assignments (the user responsible for a Relation) have no Mailchimp equivalent as a CRM owner model. We map Owner to a merge field (OWNER_EMAIL) and optionally add an Owner-tag for filtering. This allows segmentation by sales rep without an owner assignment model.