Migrate from Fulfil to Microsoft Dynamics 365 Business Central

Fulfil Items with SKU, description, cost, price, reorder point, and bin location map directly to Dynamics 365 Item Master records. Lot and serial number traceability migrates as part of inventory ledger entries tied to Item tracking groups configured in Dynamics. User-defined custom fields on the Fulfil Item object require explicit mapping to Dynamics 365 extension fields or custom fields on the EcoResItem table. We create the Item tracking group and registration profile in Dynamics before inventory data loads to ensure traceability is active on receipt.

Fulfil multi-warehouse configurations with bin-level location data map to Dynamics 365 Warehouse and Location records. Bin location codes from Fulfil transfer to Dynamics location IDs under the corresponding warehouse. Inventory snapshots per warehouse are loaded as inventory on-hand transactions against the correct warehouse/location combination. If Fulfil uses location-specific landed costs, these map to Costing version entries in Dynamics.

Fulfil Purchase Orders with vendor assignment, expected dates, and line items map to Dynamics 365 Purchase Order records. The critical sequencing constraint is that open receiving records (receipt transactions) must be posted in Dynamics before the associated vendor account is inactivated or closed. We extract PO receipts as separate inbound shipment and product receipt transactions, post them in Dynamics 365 before vendor closeout, and then close the PO line.

Fulfil vendor records map to Dynamics 365 Vendor records with contact details, address, and payment terms preserved. Vendor account groups in Dynamics define posting setup (posting profile, terms of payment, cash flow forecast mapping). We extract vendor balance information from Fulfil's accounts payable data and load it as outstanding PO amounts and open vendor invoice records in Dynamics.

Fulfil Customer records including contact details, billing address, shipping addresses, and account-level pricing tiers map to Dynamics 365 Customer records. Custom fields on the Fulfil Customer object require explicit field-level mapping to Dynamics 365 extension fields on the CustCustomerV2Entity or via custom fields on the Account (or Customer) table. Ship-to addresses migrate as additional customer addresses linked to the primary customer account.

Fulfil Sales Orders map to Microsoft Dynamics 365 Sales Order records with order status, line items, fulfillment state, and channel attribution preserved. The channel attribution (Shopify, Amazon, direct) is stored in a custom field in Dynamics since the standard schema does not have a channel source field. Shipping and payment records associated with each order are pulled in the same pass and linked as sales order header and line notes.

Fulfil stores engraving, embroidery, and made-to-order customization as extended attributes on Sales Order Lines rather than as a distinct object. We parse the line-level JSON, extract the custom attribute name and value, and map them to Dynamics 365 Product Attribute values on the Sales Order Line (via the InventProductAttributeValue table) or to item variant records if the customization is product-specific. This requires pre-configuration of the attribute groups in Dynamics before order line migration begins.

Lot tracking and serial number assignments on Fulfil Items are tied to inventory transactions. We carry these through as Dynamics 365 inventory transactions with the corresponding lot ID or serial number on the InventTrans table. The Item tracking group in Dynamics must be configured to allow the specific lot or serial number dimension before receiving records are posted.

Fulfil vendor invoice records from the financials module map to Dynamics 365 Vendor Invoice records. Open invoices are loaded with matching PO receipt references; historical invoices are loaded as posted vendor invoices. The destination's chart of accounts structure determines the expense account mapping for each invoice line, which is why the chart of accounts reconciliation (see object mapping below) must be completed before financial records are migrated.

Fulfil financial accounts export per entity but require manual mapping to the Dynamics 365 chart of accounts. For multi-entity deployments, we collect the full account tree for each Fulfil legal entity and build a mapping table against the destination's account structure before any financial record transfer. Account codes, account type, and posting profile assignments are configured in Dynamics before Bills and Invoices are imported. This is a manual reconciliation step driven by the customer's finance team with FlitStack AI facilitating the data extract and destination schema setup.

Where Fulfil's manufacturing module is in use, work orders, BOMs, and production steps are accessible via API. BOM hierarchies are complex to sequence in Dynamics because the production bill of materials must be configured before production orders are created. We extract the BOM structure from Fulfil, map each component item to the corresponding Dynamics item, and create the BOM in Dynamics 365 with routing and work center definitions. Production orders are then created referencing the BOM. Business Central Essentials does not include manufacturing; if the customer is on Business Central Essentials, we flag manufacturing records as outside standard scope.

Fulfil's landed cost tracking for multi-location inventory with freight, duty, and insurance allocation maps to Dynamics 365 Finance and Operations Landed Cost module. This module is only available on the Finance and Operations tier, not Business Central. If the destination is Business Central, landed costs require manual configuration as additional cost categories on purchase order lines or as separate freight expense entries. We identify landed cost records during scoping and confirm the appropriate Dynamics tier before financial data migration begins.