Migrate from Pronto Xi to Microsoft Dynamics 365 Business Central

Pronto Xi's hierarchical Informix account codes with custom segments map to Dynamics 365 Main Account structure with Financial Dimension sets. We extract account codes, descriptions, and parent-child relationships via direct Informix queries, preserving the full hierarchical depth. The destination financial dimension framework requires configuration of dimension sets (such as BusinessUnit, CostCentre, Department) that replicate Pronto Xi's segment logic. We flag any accounts with invalid characters or lengths that exceed Dynamics 365's main account name limits and resolve these before import.

Pronto Xi customer records with address books, payment terms, tax codes, and contact details map to Dynamics 365 CustCustomerV3Entity and DirParty table structures. We handle multi-address scenarios by mapping the primary address to the Customer address and secondary addresses to LogisticsPostalAddress records with appropriate roles. Payment terms migrate as the corresponding Dynamics 365 code; any Pronto Xi-specific terms are created as new codes during the configuration phase.

Pronto Xi supplier records map to Dynamics 365 VendVendorV3Entity with the same address, contact, and payment term handling as customer records. We extract the supplier's ABN (Australian Business Number) and map it to the Tax Registration Number field. Any Pronto Xi-specific supplier categories require a new vendor group configuration in Dynamics 365 before import begins.

Pronto Xi item masters with BOM references, cost layers, reorder points, and product dimensions map to Dynamics 365 EcoResReleasedProductV2. We preserve the Pronto Xi item number as the product number, map the costing method (Standard, Average, FIFO) to the item's costing policy, and transfer unit of measure conversions. Item product dimensions such as size, colour, and configuration are mapped to Dynamics 365 dimension groups configured before product import.

Pronto Xi's multi-warehouse inventory location hierarchy maps to Dynamics 365 Warehouse and Site entities. We extract current stock quantities per location and map these to WMSInventoryOnHand records after the item and warehouse structures are validated. If Pronto Xi's location codes use a different naming convention than Dynamics 365's site-warehouse-location三级 structure, we apply a location mapping table during staging.

Outstanding invoices and credit memos require extraction before the source period close with full aging bucket data. We migrate open AR as CustTransOpen records in Dynamics 365, preserving invoice numbers, amounts, due dates, and original posting dates. Payments and credit notes applied to the invoices in Pronto Xi are sequenced and applied in the same chronological order in Dynamics 365 to maintain clean aging reports. Any partially applied invoices retain the remaining balance as open.

Open payables follow the same sequencing logic as AR. We extract vendor invoice records with payment terms, extract any credit notes, and apply them in chronological order against matching invoices in Dynamics 365. The migration preserves the original invoice date for aging calculations and the original posting date for financial reporting accuracy.

Pronto Xi BOMs with component items, quantities per assembly, and revision versions tied to manufacturing processes map to Dynamics 365 BOMDesigner and Formula entities. We extract BOM headers and component lines, preserving the active revision flag and the effective-from date. Any BOM steps referencing Pronto Xi-specific routing operations require a routing configuration in Dynamics 365 before the BOM can be activated.

Work orders with routing steps, labour allocations, and component consumption records tied to specific BOM versions map to ProdTable and ProdBomTable in Dynamics 365. We flag any work order steps referencing deprecated BOM revisions or inactive routes that may cause production order activation failures. Open and in-progress work orders are migrated; completed work orders are archived as historical records with their actual cost and output data.

Open sales orders with line items, pricing, discounting, and delivery scheduling map to SalesOrderHeaderV2 and SalesOrderLine entities. We extract order headers and lines, set destination order statuses based on fulfilment progress (Open, Invoiced, Delivered) to avoid inadvertent duplicate shipments, and preserve any order-specific pricing that deviates from the standard price list. Completed orders are migrated as invoice records rather than open orders.

Open purchase orders map to PurchTable and PurchLine entities following the same header-and-line pattern as sales orders. We preserve the vendor reference number, confirmed delivery dates, and any purchase-order-specific charges. Receipts already posted in Pronto Xi are not re-imported; only open purchase order lines awaiting receipt are migrated with their original line numbers preserved for reconciliation.

Linked documents stored in Pronto Xi's document management system are extracted via file references or direct Informix blob access. We extract files with their original naming conventions and associate them with the parent record in Dynamics 365's SharePoint integration or Dataverse document locations. Metadata such as document type, author, and creation date are preserved as SharePoint column values. Documents without a resolvable parent record are held in a document queue for manual classification.

Pronto Xi environments frequently contain bespoke modules built on the SDK or RAD framework. We identify each bespoke module during scoping, map its data structures to Dynamics 365 custom fields (via Power Platform or developer extensions), and flag any that have no equivalent destination object. Custom modules without a clear Dynamics 365 counterpart are migrated as lookup tables in Dataverse with a manual rebuild handoff documented for the implementation team.

Pronto Xi service module records include asset links, job scheduling, technician assignments, and contract details. These map to the Dynamics 365 Field Service Work Order entity with asset relationships, booking rules, and service agreement terms. We flag service contracts that reference Pronto Xi-specific pricing or SLA tiers requiring manual configuration in Field Service agreements.