Migrate from UPNIFY CRM to Salesforce Sales Cloud

UPNIFY Client records map directly to Salesforce Contact. Standard fields (name, email, mobile phone, company association) migrate 1:1. Custom client fields (text, number, date, dropdown) map to Salesforce custom Contact fields prefixed with upnify_ for traceability. The client's company_link field resolves to the AccountId on Contact, which requires Companies to import first. Communication history stored on the Client record migrates as a Contact Activity timeline via Bulk API 2.0.

UPNIFY Companies map to Salesforce Account. The Company is a distinct B2B object used to group multiple Client contacts under one account. We import Accounts first so that the AccountId lookup on Contact resolves at insert time without parent-record errors. Account Name, Website, Industry, and Phone migrate as standard fields. Company-level custom fields map to custom Account fields with upnify_ prefix.

UPNIFY Opportunities drive pipeline management and tie to customizable pipeline stages. Each opportunity maps to Salesforce Opportunity with stage, amount, close date, owner, and probability preserved. UPNIFY stage names and IDs map to Salesforce StageName values via a customer-supplied stage-mapping document. Record Type is set based on the pipeline assignment in UPNIFY. Opportunity custom fields migrate as custom Opportunity fields.

UPNIFY Prospects represent pre-qualified leads in a separate object from Clients. Prospects migrate to Salesforce Lead with name, email, phone, company, and lifecycle-stage values preserved in a custom field upnify_lifecycle_stage__c. Lead Status maps from UPNIFY's prospect status property. We flag any Prospect records that already have a converted Client relationship in UPNIFY to avoid duplicate Contact creation during migration.

UPNIFY Quotations carry product line items, pricing, currency, and embedded exchange-rate metadata per line item. The multi-currency metadata (stored as embedded exchange rates per quotation record) must be flattened into a standard price field during import because Salesforce Quotes use the org-level currency and PricebookEntry without embedded rate metadata. We extract the original quotation total, convert to the customer's target Salesforce org currency using the embedded rate, and store the original UPNIFY currency and rate in custom Quote fields upnify_original_currency__c and upnify_exchange_rate__c for audit.

UPNIFY Products managed under Catalogs map to Salesforce Product2. Product name, SKU (hs_sku equivalent), price, and description migrate as standard fields. Stock-level data does not migrate because UPNIFY does not populate it consistently. Pricebook2 entries are created during import to support Quote and OpportunityLineItem relationships. Bulk export of products runs via UPNIFY Administration before API probing if the API access scope is insufficient.

UPNIFY Goals track team or user-level sales targets with period, target value, and owner assignment. Goals migrate as Salesforce Task records with a custom Task record type Goal, storing goal name, period, target value, and owner in custom fields upnify_goal_name__c, upnify_goal_period__c, and upnify_target_value__c. Goals are user-scoped so we resolve the owner to the Salesforce User via email match.

UPNIFY Calendar entries include tasks, reminders, and appointments with owner, due date, and status. Task title, status (open/completed), due date, and owner assignment migrate to Salesforce Task. Completed vs. open status is preserved. ActivityDate is set to the original UPNIFY timestamp to maintain timeline ordering. Task assignment migrates by resolving the UPNIFY user reference to Salesforce OwnerId via email match.

UPNIFY Tags are applied across Clients, Companies, and Opportunities for segmentation. We export all tag assignments per object and reconstruct them in Salesforce as multi-select picklist fields on the respective objects (upnify_tags__c on Contact, Account, and Opportunity). The customer chooses tag strategy during scoping: either migrate all tags as a single concatenated picklist or collapse to the top N tags and archive the rest.

UPNIFY custom fields are supported on Clients, Companies, and Opportunities with field types including text, number, date, and dropdown. We pre-create destination custom fields with matching API names (upnify_ prefix) and type-mapped Salesforce field types before migration. Dropdown fields in UPNIFY map to Salesforce picklist fields with values explicitly mapped. Any type mismatch is flagged during discovery for manual resolution.

UPNIFY Users are mapped by email address to Salesforce User records. Active vs. inactive status is preserved. Role and permission sets differ per CRM and require manual reassignment post-migration in Salesforce Profile and Permission Set configuration. We provision the mapping table during scoping and hold any User without a matching Salesforce record in a reconciliation queue.

UPNIFY Connect WhatsApp conversation bundles are sold as separate credit packs (e.g., Connect 5K at $449 one-time) stored in a separate data store from the CRM contact record. Conversation history cannot be ingested into Salesforce's native messaging model because WhatsApp message thread format is not a standard Salesforce object. We export conversation metadata (contact, timestamp, direction) as a structured CSV for the customer's records but do not migrate it as an active CRM object. Salesforce's native Messaging product or an AppExchange WhatsApp connector is recommended as the replacement.