Migrate from Oncord to Microsoft Dynamics 365 Sales

Oncord's flat Contact object requires a structural split into the Dynamics 365 Account-Contact hierarchy. We extract the contact's email domain during migration and use it as the Account dedupe key, creating one Account per unique domain (or per customer-defined grouping rule if multi-domain accounts exist). Oncord's contact fields (name, email, phone, address, custom fields) map to Contact fields; the newly created Account inherits the company name from the contact's organization field or is generated from the domain. We preserve all Oncord field values in custom Contact fields (oncord_original_company__c, oncored_contact_id__c) for audit.

Oncord Groups function as static tagging and segmentation lists. We export every Group and its member contacts. In Dynamics 365, static Lists map to Campaign Membership (Campaign and CampaignMember) or to static Marketing Lists. We recommend Campaign membership for list-based follow-up sequences and static Marketing Lists for segmentation used inside opportunity context. Groups with more than 10,000 contacts are chunked across multiple Campaign records to stay within Dynamics 365's API limits.

Oncord CustomFields exposed via the internal API component map to custom fields on the Contact entity in Dataverse. We handle type mapping: Oncord text fields map to nvarchar, number fields to decimal or integer, date fields to datetime, and dropdown fields to picklist with the same option labels. We pre-create the custom field definitions in the destination Dynamics 365 org via the metadata API before importing any data, matching Oncord field labels to Dataverse display names.

Products are only present if the customer has the Commerce add-on ($40/month) active. We export product name, description, price, SKU, inventory count, images, and any custom product fields. In Microsoft Dynamics 365 Sales , we create Product2 records with the Standard Price Book entry, matching Oncord SKU to Product2 ProductCode. If the customer has tiered pricing or product variants, we create separate Product2 records with a parent-child relationship via the Product Association entity.

Oncord Events (RSVP functionality in the Marketing add-on) have no direct Microsoft Dynamics 365 Sales equivalent. Sales does not include a native event or registration management object. We capture event name, date, location, capacity, and attendee list as custom Contact fields (event_name__c, event_date__c, event_rsvp_status__c) and document each Event's attendee list separately for the customer's admin to work with in Dynamics 365. Full event management requires Dynamics 365 Marketing (separate license) or a partner event module.

Oncord Automation Workflows trigger on contact activity, group membership, or time-based schedules. We document the complete workflow structure including triggers, conditions, filters, delays, and CRM actions for every active workflow. This inventory is delivered as a written specification that the customer's Dynamics 365 admin uses to rebuild equivalent automations in Power Automate, Microsoft Dynamics 365 Sales desktop flows, or Dataverse workflows. Workflow logic does not migrate as code because Oncord's workflow engine has no export or translation path to Microsoft Power Platform.

Oncord Web Forms grow the contact database and carry custom field mappings per form. We export form definitions, field names, and the contact-property mappings. This inventory is delivered as a written specification for rebuilding in Microsoft Forms, Power Apps portals, or a partner form solution. Microsoft Dynamics 365 Sales does not include a native web form builder; Web-to-Lead is the closest standard replacement for lead capture from public-facing forms.

Oncord includes unlimited admin users on base plans. We export user records including name, email, and role designation. Oncord Owner assignments on Contacts map to Dynamics 365 OwnerId via email match against the destination User table. Oncord role semantics (Admin, Standard) map to Dynamics 365 Security Roles assigned post-migration by the customer's admin. Any Oncord Owner without a matching Dynamics 365 User goes to a reconciliation queue for provisioning before the Contact import phase.