Migrate from UPNIFY CRM to Mailchimp

UPNIFY Client records map to Mailchimp Audience members. We map Client first name, last name, email, and mobile phone to Mailchimp's standard contact fields. Any UPNIFY custom fields on Client (text, number, date, dropdown) map to Mailchimp merge tags (FNAME, LNAME, PHONE, and any custom merge tags prefixed with *). We create merge tags in Mailchimp Audience settings before import and preserve the field type context from UPNIFY so that date fields render correctly and dropdown fields map to Mailchimp radio or dropdown merge field types.

UPNIFY Companies have a one-to-many relationship with Clients. Mailchimp has no standalone Company or Account object, so we flatten company data onto each Contact. Company name, industry, website, phone, and address map to custom merge tags on the Mailchimp Contact (for example, COMPANY, INDUSTRY, WEBSITE, COMPANYPHONE). We resolve the Company-Client linkage at migration time by joining on the UPNIFY client_company_id foreign key and embedding the parent company data on each child Contact record. This preserves the relationship but does not create a separate company record in Mailchimp.

UPNIFY Prospects represent pre-qualified leads in a separate object from Clients. Mailchimp has no prospect lifecycle concept, so we migrate Prospects as Contacts and tag them with a Mailchimp Tag (for example, 'Prospect' or 'Lead') to indicate origin. Any UPNIFY lifecycle stage values on Prospect records become Mailchimp tags (for example, 'Qualified Lead', 'MQL') so that the customer's marketing team can target Prospect-tagged contacts in automation flows and segments. Prospect-specific custom fields map to Mailchimp merge tags in the same way as Client custom fields.

UPNIFY Opportunities carry deal value, pipeline stage, probability, expected close date, and owner. Mailchimp has no opportunity, pipeline, or deal tracking object. We do not migrate Opportunities as records. Instead, we export Opportunities to a structured CSV inventory (Opportunity name, value, stage, owner, close date, associated Contact email) and deliver it to the customer's admin for external preservation or import into a separate reporting tool. Pipeline stage definitions are documented separately so the customer can recreate any stage-based segmentation logic in Mailchimp using tags or segments if needed.

UPNIFY Quotations carry product line items, pricing, currency, and embedded exchange-rate metadata. Mailchimp has no quotation or pricing management capability. Product Connections in Mailchimp are for catalog display only and do not store pricing logic. We export Quotations to a CSV inventory (quotation number, contact email, product items, total value, currency, exchange rate used, date) and deliver it to the customer's admin. Multi-currency metadata is flattened: we extract the base currency amount and the exchange rate applied, store both as separate columns in the inventory CSV, and note the original currency code so the customer's team can restore context in an external quoting tool if needed.

UPNIFY Tags are applied across Clients, Companies, and Opportunities for segmentation. Mailchimp Tags serve the same organizational function at the Contact level. We extract all UPNIFY tag assignments per object and recreate them as Mailchimp Tags on the corresponding Contact record. UPNIFY tags with object-type prefixes (for example, 'Client: SMB', 'Opportunity: Enterprise') are migrated with the prefix stripped and stored as plain tags in Mailchimp (for example, 'SMB', 'Enterprise') unless the customer requests the prefix preserved. Tag counts are reconciled against total Contact count to ensure no tag assignments are lost during import.

UPNIFY Products from Catalogs (name, SKU, price, description) can map to Mailchimp Product Connections if the customer is on a Mailchimp plan that supports e-commerce integrations ( Essentials or higher). We map UPNIFY Product name to Mailchimp Product title, UPNIFY SKU to Mailchimp variant SKU, and UPNIFY price to Mailchimp price. Note that Mailchimp Product Connections are for storefront and abandoned-cart automation use cases; they do not serve as a product catalog lookup in email campaigns by default. If the customer does not use Mailchimp e-commerce features, we export Products to a CSV and flag that no Mailchimp equivalent is required.

UPNIFY Goals track team or user-level sales targets with periods and target values. Mailchimp has no goal or quota tracking. We export Goals to a structured CSV (goal name, owner email, period, target value, created date) and deliver it to the customer's admin. Owner assignment in the CSV references the email address of the UPNIFY user so that the customer's team can cross-reference against the Mailchimp user list if a third-party reporting tool is used to track goal performance post-migration.

UPNIFY Calendar entries include tasks, reminders, and appointments with owner and due date. Mailchimp has no task, calendar, or reminder object. We export Calendar entries to a CSV (task title, status, owner email, due date, associated Contact email if any) and deliver it to the customer's admin. Completed vs. open status is preserved in the CSV so that the team can import open tasks into a separate project management tool (Asana, Trello, Notion) or treat them as a handoff checklist during the migration window.

UPNIFY Users map to Mailchimp Audience managers by email match. Active vs. inactive status is preserved as a Mailchimp tag ('Active User', 'Inactive User') on the migrated Contact record so that the customer's admin can identify which contacts correspond to active UPNIFY users. Note that UPNIFY role and permission sets have no Mailchimp equivalent; role-based access control in Mailchimp is limited to plan tiers (Standard and above offer multiple admin levels) and does not replicate UPNIFY's user-level permission structure.