Migrate from VIENNA Advantage to Microsoft Dynamics 365 Business Central

VIENNA Advantage Business Partners cover customers, vendors, and employees under a single entity with a type classification flag. We split during the transform step: BP_Type=Customer maps to Dynamics 365 Account, BP_Type=Vendor maps to Vendor, and BP_Type=Employee maps to Worker or Contact in Human Resources. The original Business Partner name, address, and contact details transfer to the appropriate destination entity fields. This split must be resolved before any downstream record (Orders, Invoices, Projects) can be imported because each destination entity has a distinct schema and relationship structure.

VIENNA Advantage Products with SKU, UOM, pricing, and BOM linkage map directly to Dynamics 365 Item records. The product type (stock item, non-stock item, service) determines the Item Type field in Dynamics 365. Standard price and cost transfer to the Price and Cost fields on Item. BOM structures are not migrated as code; we deliver a Bill of Materials reconstruction note listing each product's BOM with components and quantities for the destination admin to rebuild in Manufacturing.

VIENNA Advantage Sales Orders map to Microsoft Dynamics 365 Sales Orders with line items preserved including product, quantity, unit price, discount, and tax. Order status maps to the Microsoft Dynamics 365 Sales Status values. The Business Partner reference is resolved to the Account lookup created in the Business Partner split step. Warehouse assignment on each line maps to the Location or Site reference in Dynamics 365.

Purchase Orders map directly to Dynamics 365 Purchase Orders. Vendor references resolve to the Vendor entity created during the Business Partner split. Line items carry product, quantity, unit cost, and tax. Order status maps to the Purchase Order Status values. GL account assignment on expense lines is preserved as the posting profile in Dynamics 365.

GL journal entries are extracted by fiscal period using date-range queries to avoid payload limits. Each entry carries debit and credit amounts mapped to the Dynamics 365 General Ledger Entry structure, with dimension tags mapped to Financial Dimensions defined in the destination's dimension set. We validate that all referenced GL accounts exist in the Dynamics 365 Chart of Accounts before loading; missing accounts are flagged in a pre-load reconciliation report for the customer's finance team to provision.

VIENNA Advantage AR invoices map to Microsoft Dynamics 365 Sales Invoice records. Payment status and partial payment identifiers carry across as invoice-level fields. Each invoice references the Business Partner (now Account) lookup created during the Business Partner split. Invoice lines include the product, quantity, price, and tax breakdown consistent with the order or standalone invoice type.

AP invoices map to Dynamics 365 Vendor Invoice records. The Vendor reference resolves to the Vendor entity from the Business Partner split. Payment terms, due date, and partial payment identifiers transfer to the destination. Invoice lines carry GL account, financial dimension, and amount consistent with the VIENNA Advantage posting configuration.

Payments in VIENNA Advantage link to invoices (AR or AP) via payment identifiers. We map payments to the relevant Customer or Vendor ledger entries in Dynamics 365 using the invoice reference to resolve the account. Partial payment amounts and payment method (cash, bank transfer, cheque) carry across as payment journal line attributes. Unmatched payments are flagged in the reconciliation report for the customer's AP/AR team to investigate before close.

VIENNA Advantage warehouse records with locator, on-hand quantity, reorder point, and expiration dates map to Dynamics 365 Locations (site and warehouse) and Stockkeeping Units (SKU by location). We extract the full warehouse-level stock balance and map it to the destination inventory model (standard or moving average) configured in the destination Finance and Operations or Business Central instance.

Projects with phases, assigned resources, billing rules, and time entries map to Dynamics 365 Project Operations or Business Central Projects. Task hierarchies and billable vs. non-billable flags map to project task and line structures. Time entries carry hours, resource, and date for billing or costing purposes. Project contracts and customer assignments link to the Account created from the original Business Partner.

Documents stored in VIENNA Advantage's inbuilt DMS are extracted as binary files with metadata including storage path, version history, and workflow routing flags. The folder structure is reconstructed in the destination SharePoint location or Dataverse attachment store, and each document is re-associated to its parent record (Account, Sales Order, Purchase Order, or Project) using the metadata we extract alongside the binary. Without re-association, documents are orphaned with no contextual link. We validate every document link post-load using a parent-record lookup.

Custom fields added via the VIENNA Advantage Canvas framework are stored per module with type, required, and default-value metadata. We extract the full custom field schema alongside the data, map each to a corresponding custom field in Dynamics 365 (using the destination's field type closest to the source type), and include the custom field definitions in the destination schema provisioning step. Custom Canvas module extensions that constitute standalone module objects are mapped to Dynamics 365 custom entities with lookup relationships to standard entities.