Migrate from VAIL-ERP to Microsoft Dynamics 365 Business Central

VAIL-ERP patient records span demographics, insurance details, and referral sources across the patient module. We map patient fields 1:1 where field names align (FirstName, LastName, DateOfBirth, Gender, Address fields) and perform value mapping on insurance codes, referral sources, and clinical flags to custom Dataverse columns on Contact. The patient-to-encounter linkage is preserved via a custom relationship entity because Dynamics 365 Finance/Supply Chain does not have a native clinical encounter model.

Clinical encounters in VAIL-ERP carry encounter-type codes, provider assignments, timestamps, and links to patient records. Dynamics 365 does not include a clinical encounter model in its standard ERP or HR apps. We create a custom Dataverse entity (Encounter or ClinicalEvent) to receive encounter records, with provider assignments mapped to User or Contact lookups and encounter timestamps preserved. The customer's healthcare data model requirements are confirmed during scoping.

VAIL-ERP HR module stores employee profiles with job titles, department assignments, compensation history, and effective-dated changes. We map employee records to Dynamics 365 Human Resources Worker entity (if Human Resources app is licensed) or to the Employee table in Business Central (if HR is not separated). Department assignments resolve via the department reference data loaded first. Effective-dated compensation history migrates as a separate Compensation History entity in Dynamics 365 Human Resources.

VAIL-ERP department and cost-center records appear across HR, finance, and inventory modules as foreign-key references. We extract department records first as reference data, map them to Dynamics 365 Business Unit or custom Department dimension, and resolve all downstream employee, financial, and inventory foreign-key references during the import phase. Department codes become the primary financial dimension in the chart-of-accounts structure.

VAIL-ERP supplier records carry contact details, agreed pricing, contract references, and payment terms. We map these to Dynamics 365 Vendor records in Finance or Supply Chain Management, with VAIL-ERP pricing agreement references stored as notes and payment terms mapped to the Dynamics 365 PaymentTerms entity. Vendor addresses resolve to the VendTable postalAddress structure.

VAIL-ERP inventory items include part numbers, descriptions, stock levels, reorder points, and multi-site location assignments. We map item records to Dynamics 365 Released Products with warehouse management dimensions (site, location, variant) if Supply Chain is licensed, or to Item records in Business Central if only Finance is in scope. Stock levels migrate as open inventory transactions into InventOnHand. Part numbers map to ProductNumber and the VAIL-ERP item cost to the current costing version.

VAIL-ERP chart of accounts defines the financial structure used by all transaction entries. We extract the full account list and map account codes to the Dynamics 365 chart-of-accounts structure (MainAccount and FinancialDimension). Any inactive or archived accounts from VAIL-ERP are flagged and set to Inactive in Dynamics 365 to preserve audit continuity. Account type (Asset, Liability, Equity, Revenue, Expense) maps to AccountType.

AP/AR ledgers and journal entries in VAIL-ERP carry account codes, transaction dates, amounts, and currency. We preserve the chart-of-accounts mapping and import open items as General Journal Lines with LedgerDimension resolved to the Dynamics 365 account structure. Closed periods migrate as historical journal batches; open items import with their current status preserved. Currency codes map directly from VAIL-ERP to Dynamics 365 CurrencyISOCode.

Tax codes in VAIL-ERP apply to financial transactions and inventory items with rate, jurisdiction, and applicability flags. We map tax code definitions to Dynamics 365 Tax Group and Tax Code entities, flagging any tax codes used in open transactions for manual review before import. Sales tax and purchase tax are separated into distinct Tax Group assignments based on the VAIL-ERP applicability flag.

VAIL-ERP user accounts carry role assignments tied to module access. We map user records to the destination Dynamics 365 User object (backed by Azure Active Directory), preserve role mappings as Security Role assignments, and note that Dynamics 365 permission structures may differ from VAIL-ERP module-level access. Users without a matching Azure AD account are held in a reconciliation queue for the customer's IT admin to provision before record migration proceeds.

VAIL-ERP attaches documents to patients, encounters, suppliers, and HR records. We export document metadata (file name, type, attached entity, date) alongside the files themselves and reattach them in Dynamics 365 either as SharePoint Document Library files linked via the native SharePoint integration or as Dataverse Annotation records attached to the parent record. File content is preserved in its original format.

VAIL-ERP supports custom fields across multiple modules for healthcare-specific attributes such as insurance codes, referral sources, and clinical flags. We enumerate all discovered custom field definitions during the discovery phase (an extra iteration required because VAIL-ERP has no published schema export), then create corresponding typed fields in Dynamics 365 (custom Dataverse columns for HR/CRM scenarios, custom fields on standard tables for Finance/Supply Chain). Custom fields discovered after the mapping is finalized require a re-run of the affected module's import phase.