Migrate from Planports CRM to Mailchimp

Planports Contact records map to Mailchimp audience members. Email address is the dedupe key. Standard fields (first name, last name, phone) map to Mailchimp's built-in merge fields (FNAME, LNAME, PHONE). The WhatsApp conversation thread stored on the Contact card does not migrate because Mailchimp does not support WhatsApp history; we document the limitation and recommend re-authorizing the WhatsApp Business API channel in the destination CRM if WhatsApp continuity is required separately.

Planports Lead records (captured from Meta Instant Forms, Google Ads, TikTok, or web forms) map to Mailchimp audience members. The source attribution field (e.g., Meta Instant Form, Google Ads) migrates as a Mailchimp tag or group so the customer can segment by acquisition channel post-migration. Lead status and assignment fields have no Mailchimp equivalent and are noted in the field mapping matrix for customer review.

Planports industry-specific custom fields (health tourism referral sources, treatment packages; real estate property IDs and viewing schedules; digital agency campaign IDs and ad spend) require field-level mapping to Mailchimp merge tags. Mailchimp merge tags use uppercase alphanumeric tokens (e.g., *|INDUSTRY|*, *|PROPERTY_ID|*). We pre-create the merge tag schema in Mailchimp before import and validate that field types map correctly (text to text, picklist to dropdown merge tag, date to date merge tag). Custom fields with no clear Mailchimp equivalent go to a custom text merge tag with a note in the mapping matrix.

Planports tags applied to Contacts and Leads (e.g., 'Hot Lead', 'Health Tourism', 'Real Estate Prospect') map to Mailchimp Tags. If the customer uses Planports segments for campaign targeting, we replicate those segments as Mailchimp Saved Segments using the equivalent filter conditions on merge tag values and tags.

Planports Company records (the business entity attached to a Contact) have no Mailchimp equivalent as a standalone object. We surface the company name as a merge tag (COMPANY) on the audience member record so the Contact's company affiliation is preserved, but the Company record itself is not migrated as a separate entity.

Planports Deals with pipeline stages, deal value, and probability percentages have no structural equivalent in Mailchimp's audience model. Mailchimp does not track pipeline stages, deal value, or probability. We flag every Deal record during data audit, document the count and stage distribution, and recommend the customer evaluate a CRM (HubSpot, Pipedrive, or Salesforce) if deal pipeline tracking is required in the destination stack.

Planports Quotes (line items with pricing and approval status) and Orders (post-sale records) cannot migrate to Mailchimp. These are financial and order management records that belong in an ERP or commerce platform, not an email audience system. We document the Quote and Order counts during the data audit as part of the inventory delivered to the customer.

Planports Activity records (calls, emails, meetings, tasks, notes) logged against Contacts and Deals have no Mailchimp equivalent. Mailchimp tracks campaign engagement (opens, clicks, unsubscribes) natively after migration but does not import historical activity timelines. We document the activity volume during audit and flag that the customer's sales team should expect a blank activity timeline in Mailchimp for all historical records.

Planports Kanban boards track sales and marketing workflow stages that have no Mailchimp representation. We flag the existence of Process boards and their card counts during audit, noting that any conditional routing logic or stage-based triggers configured on Process boards do not migrate.

Planports User records and deal ownership assignments (hubspot_owner_id) do not map to Mailchimp because Mailchimp does not have a user or owner model. Owner attribution on migrated records is dropped unless the customer requests owner email addresses be stored as a custom merge tag for internal reference.