Migrate from Expandable ERP to Microsoft Dynamics 365 Business Central

Expandable's Part Master records map to Dynamics 365 Item entities. We extract part revision history, part parameters, lot and serial number flags, and user-defined fields via SQL query. Each part revision in Expandable becomes a separate Item version in Finance and SCM or a BOM version in Business Central. The part type (inventory, non-inventory, service) maps to the Item Type field. User-defined fields from QBE exports are mapped to custom Item attributes or dimension groups configured before import.

Expandable BOMs are versioned and linked to Part revisions. We load BOMs in reverse-indent order so that sub-assemblies are created before parent BOMs in Dynamics 365, preserving the multi-level assembly hierarchy. Each BOM version corresponds to the Expandable revision it was active for. Finance and SCM BOMs support per-site routing and production bill types; Business Central BOMs are simpler with version validation. We extract the BOM Effective Date from ECO records to set the Valid From date on each Dynamics 365 BOM version.

Expandable ECO and ECM records control revision changes to parts and BOMs. We extract ECO effective dates, affected part revisions, and affected BOM levels. In Dynamics 365 Finance and SCM, Engineering Change Management creates change orders that can be linked to BOM and formula changes. We use ECO effective dates to sequence BOM version activation in the destination. ECO-to-BOM linkage is preserved as a document attachment reference so that the change history remains auditable.

Expandable Sales Order headers and line items map directly to Microsoft Dynamics 365 Sales Order. Customer associations from Expandable map to the Dynamics 365 CustCustomerAccount. Line item pricing, discounts, and tax information migrate directly. Order status (open, completed, cancelled) maps to Sales Order Status. We preserve order history including fulfilled and invoiced lines for audit completeness. Open orders are flagged for priority processing during cutover.

Expandable Purchase Order headers and line items map to Dynamics 365 Purchase Order. Vendor assignments from the Expandable vendor master map to the VendAccount. Receipt records and partial receipt flags transfer to maintain receiving history. Multi-vendor purchase scenarios are supported with separate Purchase Orders created per vendor. PO approval workflows require rebuild in Dynamics 365 as a separate workflow configuration step.

Expandable Lot Master data (lot numbers, on-hand quantities, locations, expiry dates) maps to Dynamics 365 inventory transactions and lot tracking. We extract serial number traceability records as separate Item Tracking records in Finance and SCM. For Business Central, lot and serial number tracking is configured at the Item level. Inventory locations map to the Dynamics 365 Warehouse configuration. On-hand quantity validation is performed before cutover against a physical count to reconcile any discrepancies.

Expandable GL account balances and journal entries migrate to Dynamics 365 General Journal. Because Expandable has no native financial statement generator, we extract raw GL subledger data via SQL query so that the destination can reconstruct P&L, balance sheet, and cash flow statements. Chart of accounts mapping is performed during scoping. Journal batch numbers and posting dates are preserved. Year-end closing entries transfer as-is. Financial dimensions in Dynamics 365 (Cost Center, Department, Division) are either mapped from Expandable cost center codes or left unconfigured for the customer's implementation team to define.

Expandable Quality Events contain FDA compliance metadata (event severity, root cause classification, corrective action status, linked lot and part references) required for 21 CFR Part 820 traceability. We extract Quality Events as structured records and map them to Dynamics 365 Finance and SCM Quality Management non-conformance records, preserving event-to-part and event-to-lot relationships rather than flattening them to text notes. Business Central does not include native quality management in standard tiers; we advise customers requiring FDA compliance to license Finance and SCM or an ISV quality add-on.

Expandable does not natively handle RMA or CAPA; some customers run third-party standalone tools. During scoping, we identify whether RMA/CAPA data shares a database or API connection with Expandable. If the data is accessible, we consolidate it into Dynamics 365 Finance and SCM Return Orders or Quality Actions. If the standalone tool holds RMA/CAPA data without connectivity to Expandable, we treat it as a separate migration workstream and map the data to the appropriate Dynamics 365 entity during a follow-on engagement.

Expandable uses role-based Advanced Security. User accounts and role assignments are exported as a user-to-role mapping table. Dynamics 365 requires rebinding users to Security Roles and Teams. We export the mapping table and provide a role-equivalence guide showing which Expandable role maps to which Dynamics 365 Security Role, but actual User provisioning in the destination is performed by the customer's Dynamics 365 admin because it requires authentication setup (Azure AD for cloud, or Windows AD for on-premises deployments).

Expandable Vendor records map to Dynamics 365 Vendor entities. We extract vendor name, address, payment terms, and tax ID. Vendor-specific pricing agreements map to Purchase Agreement records in Dynamics 365 if the customer uses vendor contracts. Vendor contacts transfer as Contact records linked to the Vendor.

Expandable Customer records map to Dynamics 365 Customer entities. Customer name, address, payment terms, credit limits, and invoice addresses transfer directly. Customer-specific pricing and discounts from Expandable map to Sales Agreement records or are configured as Customer Price Groups in Dynamics 365.