Migrate from AI Works to Microsoft Dynamics 365 Business Central

AI Works financial accounts tagged as vendor-type map to Dynamics 365 Vendors; accounts tagged as customer-type map to Dynamics 365 Customers. The account number becomes the VendorAccountNumber or CustomerAccountNumber. We resolve the split using a type field on the AI Works account record and preserve the original AI Works account ID in a custom field ai_works_account_id__c for audit and reconciliation.

AI Works G/L accounts map directly to Dynamics 365 MainAccount records. Account type (Asset, Liability, Equity, Revenue, Expense) maps to the AccountType attribute. If AI Works uses a segment-coded chart of accounts, we parse the segments and configure the corresponding financial dimension set in D365 F&SCM before import.

AI Works invoices with status Open map to D365 SalesOrder or FreeTextInvoice depending on whether line item detail is present. Closed invoices with full payment history map to CustTrans records linked to the original invoice document. We preserve invoice date, due date, payment terms, and total amounts; tax calculations are recalculated in D365 against the active tax configuration.

AI Works purchase orders map to D365 PurchPurchaseOrderHeader with PurchPurchaseOrderLine detail. Purchase order status (Draft, Submitted, Confirmed, Received, Closed) maps to D365 PurchaseOrderStatus enumeration. Remaining receipt quantity is preserved for partially received orders so receiving can continue in D365 post-migration.

AI Works items map to D365 ReleasedProduct with product type (Item vs Service) preserved. The AI Works SKU becomes the product number. Inventory dimensions (Site, Warehouse, Color, Size) are created in D365 as active dimension fields if they exist in the AI Works product master, and item coverage settings are migrated as D365 item coverage rules.

AI Works custom fields stored as extended properties map to D365 UserDefinedField if the field type is supported (string, integer, decimal). Fields requiring enum or reference type are implemented as table extension fields via the D365 development environment. We document every custom field with its source property name, D365 target field, data type mapping, and whether the field is visible on the form or used only in reports. Fields without a D365 equivalent are flagged as requiring a custom development task post-migration.

AI Works users map to D365 User records matched by email address. If the D365 deployment uses Human Resources integration, users may map to Worker records first. Users without an active D365 license are held in a reconciliation queue for the customer's admin to provision before record import resumes.

AI Works payment term definitions (Net 30, Net 60, 2/10 Net 30) map to D365 PaymentTerm records with matching CashDiscountDays, DueDateDays, and CashDiscountPercentage. The mapping is deterministic for standard terms; custom terms are recreated in D365 by the finance admin using the Payment Terms form.

AI Works tax codes map to D365 TaxGroup (for sales tax) or TaxItemGroup (for item-level tax) records. Tax rates and jurisdiction assignments are migrated as TaxCode configurations. We flag any compound tax or VAT reverse-charge scenarios that require D365-specific tax setup beyond the standard TaxGroup assignment.

AI Works approval chains for purchase orders, invoices, and expense reports do not migrate as executable code. We deliver a written inventory of every active approval chain with its trigger condition, approver routing rule, dollar threshold, and a recommended Power Automate equivalent. The customer's finance admin or a D365 partner rebuilds the approval workflow in the D365 workflow designer post-migration.

AI Works addresses with multiple roles (invoice, delivery, primary) map to D365 PostalAddress records with AddressPurpose set for each role. D365 allows multiple purposes per address record, but only one can be marked as Primary. If the source has separate primary invoice and primary delivery addresses, we create two address records in D365 with the respective purpose flags rather than collapsing to a single primary address.

AI Works dimension codes (Department, Cost Center, Project, Location) map to D365 FinancialDimension records and their corresponding DimensionAttribute definitions. If AI Works uses a multi-segment account code (e.g., 100-200-300), we split each segment into its own financial dimension and create a DimensionDefaultRule to apply defaults based on the account structure.