Migrate from PlanPlus Online to Mailchimp

PlanPlus Online Contact records map directly to Mailchimp Subscribers in the destination Audience. Email address serves as the primary key and dedupe field. Standard fields (first name, last name, phone, address) map to Mailchimp address and phone merge fields. Owner assignment from PlanPlus Online does not map to any Mailchimp field because Mailchimp has no record-level ownership model—ownership and team access are managed at the Mailchimp account level instead.

Mailchimp has no native Company or Account object. We preserve PlanPlus Online Company name, industry, and size data as custom merge fields (COMPANY_NAME, COMPANY_INDUSTRY, COMPANY_SIZE) on each Subscriber record linked to that company. If a Contact in PlanPlus Online has no associated Company, we populate the company merge fields with null. Customer should be aware that Mailchimp's reporting cannot segment by Company natively—segmentation is tag-based or merge field-based only.

PlanPlus Online Deals use an External Opportunity Portal with pipeline stages, deal values, and close dates. Mailchimp has no Opportunity, Pipeline, or Deal object. We do not migrate Deal records. We deliver a written export of all Deals including stage, value, close date, and associated Contact for the customer to load into a separate spreadsheet or CRM if tracking sales pipeline history post-migration is required.

PlanPlus Online custom fields on Contact records export as flat key-value pairs in the CSV. We map each custom field to a corresponding Mailchimp merge field of appropriate type: text fields to TEXT merge fields, date fields to DATE merge fields, and numeric fields to NUMBER merge fields. Mailchimp has a 40-merge-field limit per Audience, so we flag any PlanPlus Online Contact with more than 40 custom fields for manual field consolidation before migration. Tags in Mailchimp can supplement merge fields for data that does not fit the merge field budget.

PlanPlus Online calendar events export cleanly via sync connectors, but Mailchimp has no calendar or appointment object. Calendar events and meeting data do not migrate. We document which external calendars were connected (Google, Microsoft 365, Outlook) so the customer can re-establish sync connections in Mailchimp or their preferred calendar tool post-migration.

PlanPlus Online tasks export with priority, due date, status, and assignment. Mailchimp has no task management capability. Franklin Covey priority quadrant data (stored as a custom field in PlanPlus Online) migrates as a TEXT merge field if present, but task assignment and due dates do not map to any Mailchimp object. We recommend the customer use a dedicated task management tool alongside Mailchimp.

PlanPlus Online projects export with status, milestones, and task breakdowns. Mailchimp has no project management module. We do not migrate project data. Project Summary Reports published as webpages are captured as static HTML exports if accessible, but Mailchimp cannot host or display this content natively.

PlanPlus Online User accounts map to Mailchimp user accounts by email match. Active PlanPlus Online users become Mailchimp account collaborators with appropriate permission levels (Admin, Author, Viewer). Inactive PlanPlus Online users are flagged for the customer to decide whether to provision a corresponding Mailchimp account or archive the contact without a Mailchimp login.

Sync connections to Google Calendar, Microsoft 365, and Outlook are authentication configurations that do not carry over to Mailchimp. We document which external systems were connected so the customer can re-establish OAuth connections in Mailchimp's Integrations directory post-migration.