Migrate from OptifiNow to Mailchimp

OptifiNow Contacts map directly to Mailchimp Audience Members using email as the dedupe key. We preserve first name, last name, email address, phone number, and opt-in status (hs_email_optout or equivalent). Custom contact fields from OptifiNow migrate to Mailchimp merge fields (FNAME, LNAME, PHONE, and any custom text or date fields). We do not migrate social collaboration data, contact source attribution, or ownership assignments as Mailchimp has no equivalent Owner field.

OptifiNow Accounts do not have a direct Mailchimp equivalent. We typically aggregate Accounts as Tags on the corresponding Contact record (e.g., tag: 'Account: Acme Corp') or merge account name into a custom merge field (ACCOUNTNAME). If the customer has many-to-one account hierarchies, we flatten them to a primary account tag. We do not create a separate Account object in Mailchimp because no such object exists.

OptifiNow Leads migrate to Mailchimp Audience Members with a segmentation tag (e.g., tag: 'Lead Source: Referral') to distinguish them from converted Contacts. We preserve lead source, assignment rules, and any lead score custom field as a Mailchimp merge field or tag group. Unqualified leads that the customer does not want in Mailchimp are excluded based on a scoping decision made during discovery.

OptifiNow Opportunities (deals with pipeline stages, probabilities, and close dates) have no Mailchimp equivalent. Mailchimp has no deal, opportunity, or pipeline object. We exclude Opportunities from the migration scope entirely and document this gap in the handoff report so the customer's admin does not expect deal data in Mailchimp. If deal tracking is required post-migration, the customer must evaluate a CRM addition or replacement.

OptifiNow stores automated email sequences, triggers, and delays as internal workflow definitions that do not export as runnable automation packages. We document OptifiNow sequence templates as plain-text records in the handoff inventory, including trigger conditions, delay values, and email content. The customer rebuilds these in Mailchimp's Automation builder. This is a disclosed limitation that affects marketing teams relying on automated nurture sequences.

OptifiNow supports custom objects via API, but Mailchimp has no custom object support whatsoever. Any OptifiNow custom objects (e.g., Policy, Loan, Subscription, Property) cannot be migrated to Mailchimp. We document custom object types and field definitions in the handoff inventory. If the customer needs this data visible post-migration, they must either maintain OptifiNow for that data or evaluate a different destination platform.

OptifiNow email engagement logs (sent, opened, clicked) linked to Contacts migrate to Mailchimp as contact-level activity history. We map the original send timestamp and engagement type (Opened, Clicked) to Mailchimp's contact activity feed via the Mailchimp API. Historical email content from OptifiNow does not migrate as Mailchimp campaign records; we document the email body and subject line in a plain-text activity log attached to the contact.

OptifiNow stores call logs, meeting records, tasks, and notes as activity objects linked to Contacts and Accounts. Mailchimp tracks only email-related activity (opens, clicks, unsubscribes) on individual contacts. Call duration, meeting attendance, task status, and note content have no Mailchimp equivalent. We exclude these engagement types from the migration and note them in the handoff report. If call or meeting logging is required, the customer needs a separate CRM or a Mailchimp integration with a calling tool.