Migrate from UPNIFY CRM to Microsoft Dynamics 365 Sales

Client is UPNIFY's primary contact object, storing name, company email, mobile phone, and communication history. We migrate all standard fields 1:1 to Dynamics 365 Contact. Custom client fields map as key-value pairs into pre-created Contact custom fields. The Account-Contact linkage is resolved by importing Companies first (as Accounts) and then linking each Client to its parent Account during the Contact insert phase.

Companies are a distinct B2B object in UPNIFY used to group multiple client contacts under one account. We migrate Companies to Dynamics 365 Accounts 1:1, preserving the Company-Contact linkage by sequencing Accounts before Contacts. Company-level custom fields and tag assignments migrate as Account custom fields and TopicAssignment records respectively.

Opportunities drive pipeline management and tie to customizable pipeline stages. We map UPNIFY stages to Dynamics Sales Processes via a customer-supplied stage-mapping document. Each UPNIFY pipeline becomes a Dynamics Record Type on Opportunity with its own Page Layout and stage whitelist. Opportunity owner assignment resolves via User email matching. Closed-Lost and Closed-Won date stamps migrate as CloseDate with status preserved.

Prospects represent pre-qualified leads in a separate object from Clients. Microsoft Dynamics 365 Sales uses a distinct Lead object for unqualified prospects, making the Prospect-to-Lead mapping 1:1. We preserve lifecycle-stage values in a custom field so the customer's admin can define a Lead qualification criteria rule for conversion to Contact and Account post-migration.

Quotations carry product line items, pricing, currency, and embedded exchange-rate metadata. UPNIFY stores the exchange rate as a nested object inside the Quotation record, which has no direct Dynamics equivalent. We flatten this metadata into separate Opportunity custom fields during transformation, extracting the base currency, target currency, and rate into typed decimal fields that import cleanly without schema mismatches.

Products are managed under Catalogs and support bulk export via the UPNIFY Administration panel. We migrate product name, SKU (mapped to ProductCode), price, and description into Product2 records with corresponding Standard Pricebook entries created during import. Stock-level data does not migrate consistently from UPNIFY and is flagged as a data quality note rather than a schema gap.

Goals track team or user-level sales targets with name, period, target value, and owner assignment. We map Goals to Dynamics 365 Goal records with the metric type preserved (currency, integer, or count). Owner mapping resolves the UPNIFY user to a Dynamics User by email match. Goal period (fiscal period or custom date range) migrates as the goal's start and end date.

Calendar entries include tasks, reminders, and appointments with owner and due date. We migrate task title, status (completed vs. open), due date, and owner assignment into Dynamics 365 Task records. Activity timeline ordering is preserved by setting ActivityDate to the original UPNIFY timestamp. Completed vs. open status carries through as Task Status (Completed, Not Started, In Progress).

Custom fields are supported on Clients, Companies, and Opportunities in UPNIFY, with types including text, number, date, and dropdown. We map these to destination custom fields pre-created in Dynamics 365 via the solutions explorer. Type mismatches between UPNIFY field types and Dynamics field types are flagged in the scoping document before migration begins, with the customer choosing whether to convert (e.g., UPNIFY number to Dynamics whole number vs. decimal).

Tags apply across objects (Clients, Companies, Opportunities) for segmentation. We export all tag assignments per object and reconstruct them in Dynamics 365 as either TopicAssignment records (for cross-object tagging) or as multi-select picklist values on the target entity (for entity-specific segmentation). The customer selects the tagging strategy during scoping based on their reporting needs in Dynamics.