Migrate from Aptean Distribution ERP to Microsoft Dynamics 365 Business Central

Aptean Customer records map to D365 Customer (F&O) or Customer (Business Central). The customer group, pricing tier, credit limit, and payment terms migrate as typed fields. Hierarchical pricing structures stored in Aptean customer relationships replicate as Customer Price Groups or trade agreements in D365. We use the Customer account number as the dedupe key and preserve the Aptean customer reference field in a custom extension field for cross-system audit.

Aptean Vendor records migrate to D365 Vendor. Multi-currency support and harmonization-code-linked landed cost component fields (agency fees, freight, duties) map to the corresponding D365 vendor address and currency configurations. Vendor lead times from Aptean PO associations migrate as default product lead times on the vendor record for demand planning use.

Aptean Item records with lot/serial tracking, warehouse-specific stocking locations, and cost layers migrate to D365 Released Products or Business Central Items. Lot-expiry configurations and stocking locations map to D365 Tracking dimensions and location setup respectively. The Aptean item cost structure (FIFO, average, standard) maps to the corresponding D365 cost model. Cost layers from Aptean migrate as opening inventory value records in D365.

Aptean multi-warehouse configurations with directed putaway rules and speed-bin definitions migrate to D365 Warehouse management configuration. Wave-picking criteria, staging area definitions, and putaway rule templates map to D365 location directives and wave template configurations. We replicate the Aptean warehouse configuration as D365 warehouse setup so that putaway and picking logic is active at go-live rather than requiring post-migration configuration from scratch.

Aptean Sales Order lifecycle records (entry through fulfillment and invoicing) migrate to D365 Sales Order. Order status, backorder flags, promised delivery dates, and line-level pricing migrate as typed fields. We preserve the Aptean order number as an external reference number and migrate open orders in order-number sequence to maintain fulfillment continuity. Invoiced orders from Aptean migrate as Sales Invoice history records.

Aptean PO records with vendor lead times and import shipment associations migrate to D365 Purchase Order. Open PO balances link to the corresponding vendor and item records via the vendor number and product number dedupe keys. Closed and received POs migrate as purchase order history for financial audit continuity.

Chargeback records require a deduction-code crosswalk built during the data audit phase because Aptean retailer deduction codes (numeric, alpha-prefixed, or free-text) do not map directly to any D365 native object. In D365 F&O, we map deduction records to Vendor Rebate Agreements or free text credit memos depending on the deduction type. In Business Central, chargebacks map to custom or third-party deduction management extensions. We flag any unmapped deduction reason codes for customer review before cutover and write the final crosswalk into the migration transform configuration.

EDI 850, 810, and 856 documents stored in Aptean's proprietary format require extraction of the functional business content — order lines, invoice amounts, ship notice details — rather than the EDI envelope structure. We extract the functional content from whatever export format the Aptean system provides and transform it into D365-compatible flat or JSON structures. The customer configures a third-party EDI connector (TrueCommerce, SPS Commerce, or equivalent) to handle ongoing EDI processing in D365; we deliver a formatted EDI content file that maps to the connector's import template.

Aptean landed cost allocations are calculated at shipment receipt and allocated across items in the shipment, with the per-unit landed cost derived rather than stored as a static field. We extract the landed cost components (freight, duty, insurance) from the Aptean shipment record and write the final allocated per-unit values to D365 as custom item-level properties. In D365 F&O, we map to the native Landed Cost module if the customer's edition includes it; in Business Central, we create custom item fields for landed_cost_unit__c and landed_cost_components__c to preserve profitability reporting data.

Aptean GL account structure migrates cleanly to D365 Chart of Accounts with account type, currency assignment, and department/cost-center rollups preserved. We maintain the full account hierarchy for financial reporting continuity. Intercompany account mappings and financial dimension structures from Aptean replicate as D365 financial dimension sets.

Outstanding Aptean invoices, credit memos, and payment applications migrate with open/closed status flags preserved. We migrate open AP as Vendor Ledger Entries and open AR as Customer Ledger Entries with the original invoice number, due date, and amount. Records near the payment threshold are flagged for pre-cutover verification so that the customer's AP and AR teams confirm balances before D365 goes live.

Lot genealogy and serial number assignment history stored per transaction in Aptean migrate to D365 InventSerial and InventBatch tables (F&O) or Lot and Serial Number records (Business Central). The full traceability chain — receiving dates, stock movements, and customer shipment links — transfers as tracking dimension records. Lot expiry dates and quarantine status migrate as inventory status records in D365 so that FEFO picking rules are active from day one.

Aptean Distribution Resource Planning data synthesizes point-of-sale data, supplier lead times, and seasonal forecasts for 90-day inventory planning. This data does not map to a single D365 native object. We migrate the demand signals and forecast values as Demand Forecast records in D365 Planning (F&O) or as Demand Forecast entries in Business Central Planning, and we preserve the supplier lead time assumptions as item vendor lead time records. The D365 Planning module rebuilds the forward planning calculation from these inputs rather than importing Aptean's calculated plan output directly.

Aptean trade management stores multiple trade plans per agreement with accrual and deduction tracking. We migrate trade agreement pricing as D365 Sales Prices or Trade Agreements, and accrual balances as custom financial dimension allocations or period-end accrual journal entries. The customer reviews trade plan structure during scoping to confirm whether accrual methodology migrates as financial entries or requires a separate rebate management extension.

Import manifests from Aptean — including carrier, bill of lading, container, and customs declaration references — map to D365 Shipment header records or custom fields on the related purchase order. Harmonization codes, country of origin, and customs value migrate as purchase order line or item extension fields so that landed cost calculations and trade compliance reporting are available in D365 without re-entry.