Migrate from Unanet CRM by Cosential to Microsoft Dynamics 365 Sales

Unanet Companies map 1:1 to Dynamics Accounts. Company name, address, phone, website, industry, and employee count map to Account fields directly. Parent-child company hierarchies in Unanet map to the Account.ParentAccountId lookup, requiring top-down migration sequencing. We also preserve the original Unanet company identifier in a custom field for cross-reference during delta runs.

Unanet Contacts map to Dynamics Contacts. First name, last name, email, phone, mobile phone, job title, and address fields map directly. The primary company association becomes AccountId; secondary company associations migrate as Account Contact Relationship records. We retain the original Unanet contact ID in a custom field to support reconciliation and delta tracking.

Unanet Pursuits map to Dynamics Opportunities. Pursuit name becomes Opportunity.Name, estimated amount maps to EstimatedValue, and close date maps to EstimatedCloseDate. Pursuit stage translates to Opportunity.StageName via value-by-value mapping, with probability and forecast category re-applied from the Dynamics side. Original Unanet pursuit ID is stored in a custom field for traceability across migration runs.

Stage names map value-by-value from Unanet pursuit stages to Dynamics opportunity stages. Probability and forecast category re-applied per Dynamics stage configuration. Stage-entered timestamps preserved as custom datetime fields for reporting continuity. We also capture the original Unanet stage identifier in a custom field to enable audit trails and downstream analytics.

Unanet call activities migrate as Dynamics PhoneCall records. Subject, description, duration, start time, and owner preserved. Parent record reference re-linked to the mapped Account or Contact based on Unanet pursuit association. We log the original Unanet activity ID in a custom field to facilitate reconciliation and ensure no call records are missed during the cutover window.

Unanet email activities migrate as Dynamics Email records. Subject, body (plain text or HTML), sent/received timestamp, and owner preserved. Re-linked to mapped Account or Contact using the Unanet contact and pursuit association. We also capture the original Unanet email ID in a custom field for audit tracking and to support delta capture after initial migration.

Unanet meeting activities migrate as Dynamics Appointment records. Subject, location, start/end times, duration, and attendees preserved where available. Owner and parent record links re-mapped to the target Account or Contact. We retain the original Unanet meeting identifier in a custom field to enable reconciliation and to track any updates made after the initial export.

Unanet notes migrate as Dynamics Annotations. Note subject, body text, created date, and owner preserved. Rich-text formatting in Unanet notes is flattened to plain text for Dynamics compatibility. We also keep the original Unanet note ID in a custom field to support delta tracking and to ensure all annotations are linked correctly after migration.

Unanet custom fields on Companies, Contacts, and Pursuits map to Dataverse custom fields with the __c suffix. Field types (text, number, currency, picklist, date, boolean) are preserved with type-aware mapping. Note the Sales Professional 15-table limit—complex Unanet setups may require Sales Enterprise licensing.

Unanet users are matched to Dynamics SystemUsers by email address. Unmatched owners are flagged before migration with a fallback owner assigned to prevent record landing without a valid owner. Active/Unactive status preserved where applicable. We also record the original Unanet user ID in a custom field for audit trails and future reference.

Unanet proposal automation and pursuit templates do not have a native Dynamics equivalent. We export template structure, field mappings, and content library references as JSON. Rebuild typically uses Dynamics 365 Sales, Conga CPQ, or a custom Power Apps solution. Your team should plan a separate project timeline for rebuilding these templates in the target system.

Unanet account planning data and territory assignments migrate as custom fields on Account. Dynamics Territory Management (Enterprise) can be used to rebuild territory hierarchies post-migration with territory assignment rules. We also export the existing territory definitions and assignment logic as a reference document to assist with the post-migration rebuild.