Migrate from Advance Practice Management Suite to Microsoft Dynamics 365 Sales

Dynamics 365 Sales has no native healthcare data model — all patient extensions require custom Dataverse tables

Advance Practice Management Suite structures patient data as a unified healthcare record: insurance, allergies, conditions, medications, and immunizations are all first-class entities. Dynamics 365 Sales targets sales teams, not clinical practices, so it has no native equivalent for any of these data types. Every patient extension must be built as a custom Dataverse table before migration data can land. FlitStack creates the schema upfront and delivers a setup checklist so your Dynamics admin can configure Field-Level Security for HIPAA-relevant fields before the load runs.

Appointment metadata does not map to standard Dynamics 365 Activity fields

AdvancedMD stores appointments with appointment-type, assigned provider, location, and clinical-status fields. Dynamics 365's standard Task and Appointment activities use a generic subject/date/owner model with no appointment-type field and no structured location field. FlitStack creates a custom Appointment Dataverse table with a custom picklist for appointment type and text fields for provider and location, preserving the full scheduling context. Standard Dynamics activities are not used for clinical appointments. This ensures that appointment type, provider, and location information remain searchable and reportable in Dynamics reports and Power BI dashboards.

Insurance N:N family-member relationships require a custom junction table in Dataverse

Advance Practice Management Suite supports N:N insurance relationships — multiple family members linked to a single insurance plan record. Dynamics 365 supports only 1:N relationships natively between Contact and a custom InsurancePlan table. FlitStack resolves this by creating a custom ContactInsurance junction table that links each family member Contact to the shared InsurancePlan record, preserving the AdvancedMD coverage relationship without duplicating plan data across contacts. The junction table also stores the subscriber relationship and coverage effective dates, allowing billing workflows to retrieve insurance details directly from the linked Contact record.

Workflows and automation sequences cannot be migrated — must be rebuilt in Power Automate

Advance Practice Management Suite scheduling reminders, insurance-verification workflows, patient-outreach sequences, and billing alerts are built within the AdvancedMD automation engine and have no structural equivalent in Dynamics 365 Sales. They do not migrate. FlitStack extracts AdvancedMD workflow definitions as a structured export so your Power Platform admin has a rebuild reference. This is always disclosed upfront; the workflow gap is not a migration surprise. Your team should plan for the time required to rebuild each sequence in Power Automate, using the exported definitions as a step‑by‑step guide.

AdvancedMD billing records lack a direct Dynamics 365 invoice-status equivalent

Advance Practice Management Suite tracks invoice lifecycle status (Pending, Submitted to Insurance, Partially Paid, Paid in Full, Written Off) with detailed adjustment and payment history per claim. Dynamics 365 Sales has no native billing or claims module; the Invoice status pick-list values are generic. FlitStack creates a custom InvoiceStatus__c pick-list field on the Invoice custom table with AdvancedMD-specific status values, mapping each original status to a corresponding value that your billing team can recognise and act on.