Migrate from Sentia to Microsoft Dynamics 365 Sales

Sentia Contacts with lifecycle stage indicating unqualified prospect status map to Dynamics 365 Lead. Sentia Contacts with lifecycle stage indicating qualified buyer status map to Dynamics 365 Contact attached to a corresponding Account. We compute the split at migration time using Sentia's lifecycle and status properties, and preserve the original Sentia lifecycle stage in a custom field sentia_original_lifecycle__c on both Lead and Contact for audit and reporting continuity.

Sentia Company records map directly to Dynamics 365 Account. The Sentia company name becomes the Account name field and serves as the deduplication key during import. We create Account records before any Contact import so that the CustomerId lookup relationship is satisfied at the moment of Contact insert. Company names are matched case-insensitively and duplicates are flagged for customer confirmation.

Sentia Deal records map to Dynamics 365 Opportunity. The Sentia pipeline stage property maps to Dynamics 365 StageName, and the pipeline assignment maps to a Microsoft Dynamics 365 Sales Process that we configure before migration. Deal monetary values, close dates, and probability percentages migrate directly to the corresponding Opportunity fields.

Each Sentia pipeline becomes a Microsoft Dynamics 365 Sales Process with corresponding stage values. Stage probability percentages migrate from Sentia custom properties to StageProbability on the Sales Process. We validate that stage names match exactly with Dynamics 365 allowed values and flag any non-standard characters requiring normalization before import.

Sentia Lead records (distinct from Contact in Sentia's data model) map directly to Dynamics 365 Lead. Lead source and status properties migrate to Dynamics 365 LeadSource and LeadStatus. Any Sentia lead scoring value preserves in a custom field sentia_lead_score__c for sales team prioritization after migration.

Sentia activity records attached to Contacts or Deals migrate to Dynamics 365 Task, Event, or EmailMessage records linked via the Regarding (objectid) field to the corresponding Contact, Lead, Account, or Opportunity. Activity timestamps preserve the original creation date so the timeline reflects when the work actually happened rather than when migration ran.

Sentia custom fields available on the customer's active tier migrate to Dynamics 365 custom fields of equivalent data type. We discover the full field schema via Sentia's metadata API during discovery and validate against Dynamics 365 field type constraints (text length, picklist values, boolean formats). Custom fields on the Basic tier may expose fewer types than Ultimate; we flag any unavailable fields before migration begins.

Sentia Owner records map to Dynamics 365 User records by email match. Any Sentia Owner without a matching Dynamics 365 User enters a reconciliation queue for the customer admin to provision before record import resumes. Owner assignments on Contacts, Accounts, Deals, and Activities resolve against the validated User table during migration.

Sentia tags migrate as either Dynamics 365 Topics (for content classification) with TopicAssignment records, or as a custom text field on the target entity, depending on the customer's preference. Tags used for sales segmentation typically map to a custom multi-select text or option-set field on Contact or Opportunity.