Migrate from Claritysoft to Mailchimp

Claritysoft Contacts map directly to Mailchimp Audience Members. We migrate First Name, Last Name, Email Address, Phone Number, and Physical Address fields. The Email Address is the primary key and the field that determines Mailchimp subscriber status. Any contact missing an email address cannot migrate and is flagged for manual handling. Subscription status in Claritysoft maps to Mailchimp status flags: subscribed contacts map as subscribed, bounced emails map to cleaned (bounced), and unsubscribed contacts require a separate suppression list import to prevent re-sending.

Claritysoft Accounts (Companies) have no direct equivalent in Mailchimp. If the customer requires company-level segmentation in Mailchimp, we encode the Account name as a Mailchimp tag (e.g., tag: 'Account: Acme Corp') or as a custom field (COMPANY_NAME). This encoding is chosen during scoping based on the customer's segmentation needs. Account-to-contact relationships are resolved before migration and the owning Account is added to each contact record as a tag or field. This is a degraded representation of the relationship model, not a native account linkage.

Claritysoft Leads have no equivalent in Mailchimp. Mailchimp does not distinguish between a sales prospect and a marketing subscriber. We migrate Leads as Audience Members and set the status based on email consent: leads with explicit email consent migrate as subscribed; leads with no recorded consent migrate as unsubscribed or are excluded from the primary import and held in a reconciliation queue for the customer to re-confirm opt-in before adding to the audience. Lead lifecycle stages (New, Contacted, Qualified) do not transfer because Mailchimp has no lifecycle model.

Claritysoft Opportunities have no equivalent in Mailchimp. Mailchimp is an email marketing platform, not a sales CRM, and does not track deal amounts, pipeline stages, probabilities, expected close dates, or opportunity history. We do not migrate Opportunities as records. We flag the Opportunity count and stage distribution during scoping and note that pipeline reporting must be rebuilt in Mailchimp (via campaign performance against tagged audience segments representing pipeline stages) or abandoned entirely if the team no longer needs sales pipeline visibility.

Claritysoft Contact Custom Fields migrate to Mailchimp subscriber custom fields if the Mailchimp plan supports them. Standard tier and above support merge fields (TEXT, NUMBER, DATE, ADDRESS, PHONE, URL, IMAGE, RADIO, DROPDOWN, CHECKBOX). We create each custom field in Mailchimp before import and map the Claritysoft field type to the nearest Mailchimp field type. Multi-select or complex Claritysoft custom fields may encode as comma-separated text in Mailchimp. Advanced Custom Fields with calculated logic (Accelerator/Enterprise tier in Claritysoft) cannot be calculated in Mailchimp; the calculated value is stored as a static text field and the calculation logic is not migrated.

Claritysoft contact tags map directly to Mailchimp tags. Tags are flat labels in both systems, so the migration is straightforward. We extract all distinct tag values from Claritysoft contacts, create matching tags in Mailchimp before the main import, and apply tags to the corresponding Audience Members during import. Tag counts per contact are preserved. If Claritysoft tags contain hierarchical information (e.g., 'Industry: Manufacturing'), we flatten them to flat tags per Mailchimp's model.

Claritysoft Activities (Calls, Meetings, Tasks, Emails) have no equivalent in Mailchimp. Mailchimp does not have a native activity timeline or task management feature. We do not migrate activity records. Historical email engagement data (opens, clicks) from Claritysoft cannot transfer because Claritysoft stores engagement in its own activity log, not as subscriber-level metrics. If the customer needs call or meeting history in Mailchimp, they must link a third-party task management tool or document contacts externally. This is disclosed during scoping.

Claritysoft Custom Modules (available on Accelerator and Enterprise tiers) have no equivalent in Mailchimp. Custom Modules represent domain-specific data (Projects, Equipment, Subscriptions, Vehicles) that Mailchimp cannot store. We do not migrate Custom Module records. We flag the module schemas during discovery, note which modules contain data the customer considers critical, and encode selected fields as Mailchimp custom fields or tags if the customer chooses. Most Custom Module data cannot be meaningfully represented in Mailchimp's flat subscriber model.