Migrate from NeoDeck Holdings to Microsoft Dynamics 365 Sales

NeoDeck patient records map as Dynamics 365 Sales Contacts. The primary challenge is that NeoDeck stores patient-level clinical data (DOB, MRN, insurance) as native properties. These map to custom fields on the Contact record (e.g., PatientMRN__c, DateOfBirth__c) since Dynamics 365 Sales has no standard patient-demographics fields.

NeoDeck provider and staff contacts migrate as Dynamics 365 Sales Contacts with a Provider__c custom flag. Referring-provider relationships map to Account Contact Relationships or a custom Provider_Relationship__c junction table so you can track which providers are associated with which patient accounts.

NeoDeck organizations and practice entities map directly to Dynamics 365 Sales Accounts. The account name, website, industry (mapped to Healthcare or Medical Equipment), number of employees, and annual revenue transfer as standard Account fields. NeoDeck's practice-address fields map to the Account's primary address.

NeoDeck billing cases and revenue events map as Dynamics 365 Sales Opportunities. StageName maps from the NeoDeck billing-status value (Submitted, Paid, Denied, Appeal) using value mapping since Dynamics 365 Sales Opportunity stages are sales-pipeline-oriented by default. Probability defaults based on the billing status mapping.

NeoDeck clinical encounters have no direct Dynamics 365 Sales equivalent. FlitStack creates a custom neo_Encounter__c Dataverse table with columns for EncounterDate__c, Patient__c (lookup to Contact), Provider__c (lookup to Contact), EncounterType__c, ChiefComplaint__c, DiagnosisCodes__c, ProcedureCodes__c, and Notes__c. This table links to the Patient Contact record.

NeoDeck e-prescribing records require a custom neo_Prescription__c Dataverse table. Fields include PrescriptionDate__c, Patient__c (lookup), Prescriber__c (lookup to Contact), MedicationName__c, Dosage__c, Frequency__c, RefillsAllowed__c, and Status__c. Power Automate workflows recreate the prescribing logic post-migration. Each prescription record links to the patient and prescriber via lookups, enabling full traceability and downstream reporting. Additionally, the Status__c field tracks lifecycle stages such as Active, Completed, and Cancelled, and the RefillsAllowed__c integer field controls refill eligibility.

NeoDeck billing claims map to a custom neo_Claim__c Dataverse table linked to the originating Encounter and Patient Contact. Key fields include ClaimNumber__c, ClaimStatus__c, PayerName__c, PolicyNumber__c, TotalCharge__c, AmountPaid__c, DenialReason__c, and SubmissionDate__c. Dynamics 365 Sales standard Opportunity does not carry this level of claim-specific detail.

NeoDeck activity logs — calls, emails, and meeting notes attached to patient or provider records — map to Dynamics 365 Sales Task, Email, and Appointment entities. Original timestamps, activity type, and owner are preserved. Subject carries the NeoDeck activity type prefix for traceability.

NeoDeck file attachments on patient records, encounters, and claims re-upload to Dynamics 365 Sales as Note entities with the DocumentBody populated from the downloaded file. Salesforce-style Salesforce Files are not the target; Dataverse Notes with file attachments is the native pattern for Dynamics 365 Sales.

NeoDeck custom objects migrate as custom Dataverse tables in Dynamics 365 Sales. Each custom object association is evaluated: N:N relationships in NeoDeck require junction Dataverse tables; 1:N relationships map as Dataverse lookup columns. Custom object field types (pick-list, date, number) map to equivalent Dataverse column types.

NeoDeck owner and staff user IDs resolve by email match against Dynamics 365 Sales SystemUser records. Unmatched owners are flagged before migration. You can either invite them to Dynamics 365 Sales or assign their records to a fallback owner — no record lands without a valid OwnerId.

NeoDeck insurance policy data stores as custom fields on the Contact or as a separate object. FlitStack creates a neo_InsurancePolicy__c custom table with PolicyNumber__c, PayerName__c, GroupNumber__c, SubscriberId__c, CoverageStart__c, CoverageEnd__c, and CopayAmount__c, linked to the Patient Contact. This table also captures relationship to the patient via a lookup to the Contact record, allowing queries such as all policies for a given patient or all claims tied to a specific payer.