Migrate from Sentian Solutions to Microsoft Dynamics 365 Sales

Sentian's person record maps directly to Dynamics 365 Contact. The primary company link is resolved via AccountId lookup on the Contact record. When Sentian stores multiple company associations for a single person, we attach the most-recently-modified company as the primary AccountId and surface other company associations as Account Contact Relationships on the Contact record, preserving the full relationship history from the source system.

Sentian company records map one-to-one to Dynamics 365 Account. Parent-child hierarchies defined in Sentian map to the Account.ParentAccountId field, maintaining organizational structure in the destination. Multi-address company records populate the Account postaladdress fields; any secondary addresses beyond the primary billing and shipping locations are migrated as custom address fields on the Account.

Sentian leads with status values of 'unqualified' or 'new' map to Dynamics 365 Lead records, preserving all lead fields and activity history. For leads already converted in Sentian — those marked as closed-won or closed-lost — we map the record to an Opportunity in Dynamics 365 instead to preserve the deal history and prevent duplicate records when the resulting contact and opportunity are also migrated separately.

Sentian deal records map to Dynamics 365 Opportunity with all standard fields transferred. Each pipeline defined in Sentian maps to a corresponding Dynamics 365 Sales Process (implemented as a Business Process Flow). Pipeline stage names are mapped value-by-value to Opportunity StageName pick-list values, with the mapping scoped under the appropriate process to maintain stage context across different sales workflows.

Sentian's pipeline construct becomes a Dynamics 365 Business Process Flow. We create a process per Sentian pipeline, mapping each stage name to a corresponding stage in the flow. Probability and forecast-category fields are reapplied based on Dynamics 365 stage metadata.

Stage values require per-process value mapping in Dynamics 365 since stage names are scoped to specific Business Process Flows. We match Sentian stage labels to Dynamics 365 stage names and set probability percentages to match Sentian's original probability values. Stage-entry timestamps from Sentian are preserved in a custom datetime field on the Opportunity record for historical continuity and reporting purposes.

Sentian custom fields stored as key-value properties on standard objects map to Dataverse custom columns on the equivalent table. Field data type is inferred from Sentian's property type (text, number, date, pick-list) and a corresponding Dataverse attribute type is created before migration.

Sentian email activity records map directly to Dynamics 365 Email records. The email subject line, description body, to and from address fields, and sent-on timestamp are all preserved during migration. Each email is linked via the regarding_objectid attribute to the parent Contact, Lead, or Opportunity record, maintaining the activity timeline in Dynamics 365 Sales.

Sentian call log activities map to Dynamics 365 PhoneCall records, while Sentian meeting records map to Appointment entities. Call duration, subject line, and original owner are all preserved in the destination system. Both PhoneCall and Appointment records link to the originating record through the regarding_objectid lookup field, ensuring activity history remains associated with the correct CRM entity.

Sentian note entries migrate as Dynamics 365 Annotations attached to the relevant CRM record. Any rich-text formatting applied in Sentian is preserved as HTML content in the Annotation body field. The note's created-on timestamp and owning user are both migrated to support audit continuity and compliance requirements in the destination system.

Sentian file attachments are downloaded from the source API and re-uploaded to Dynamics 365 SharePoint Online document locations that are linked to the parent record. When SharePoint integration is not provisioned in the tenant, files attach as Annotation documentbody blobs in Dataverse instead. The original file names and MIME types are fully preserved throughout the transfer process.

Sentian user records are resolved by email address against Microsoft 365 users provisioned in the Dynamics 365 tenant. Unmatched owners are flagged in a pre-migration report — administrators must either invite these users to Dynamics 365 first or designate a fallback system user for their records. The original Sentian owner ID is stored in a custom reference field on each record for traceability and audit purposes.

Sentian custom objects map one-to-one to Dataverse custom tables. Any relationship fields on Sentian custom objects that reference Contacts or Accounts are mapped to lookup columns in the corresponding Dataverse custom table. N:N relationships defined between custom objects in Sentian require the creation of junction tables in Dataverse to maintain the many-to-many cardinality in the destination system.

Sentian tag or label data attached to records has no native equivalent in Dynamics 365 Sales. We migrate tag values as a custom text field (Source_Tags__c) for reference, or map them to Dynamics 365 Topics if your workflow uses topic clustering.