Migrate from Aptean Distribution ERP to Dolibarr ERP

Aptean Customer records with hierarchical pricing tiers, customer groups, and reference customer links for trade agreements map to Dolibarr ThirdParty records in customer mode. The customer_code from Aptean becomes the Dolibarr code field used as the dedupe key. Pricing tiers stored as Aptean customer group properties map to Dolibarr ExtraFields with price level categorization. Customer address structures migrate with the full address hierarchy (ship-to, bill-to) preserved as Dolibarr address records.

Aptean Vendor records with multi-currency support and landed cost component fields (agency fees, freight, duties by harmonization code) map to Dolibarr ThirdParty in supplier mode. The vendor_code from Aptean becomes the Dolibarr code field. Cost structure hierarchy migrates as Dolibarr ExtraFields on the ThirdParty record so that landed cost components are preserved for re-import planning.

Aptean Item records with lot/serial tracking, warehouse-specific stocking locations, and cost layers map to Dolibarr Product records. The item number becomes Dolibarr's ref field. Lot-expiry configurations and warehouse-specific stocking locations migrate as Dolibarr warehouse stock entries linked to the Product. Unit cost and standard price from Aptean map to Dolibarr cost price and selling price fields respectively.

Aptean multi-warehouse configurations with directed putaway rules, speed-bin definitions, wave-picking criteria, and staging configurations map to Dolibarr Warehouse records. Dolibarr's warehouse model supports physical locations but directed putaway logic requires configuration post-migration; we document the original Aptean rules in a warehouse configuration reference guide for the customer's admin to re-implement.

Aptean Sales Order lifecycle from entry through fulfillment and invoicing maps to Dolibarr Order (customer mode). Order status, backorder flags, and promised delivery date logic preserve. Line items migrate with product reference resolved to the Product record, quantity, and unit price. Open orders migrate with status preserved; closed orders migrate as historical records with their final status.

Aptean Purchase Order records tracking vendor lead times and import shipment associations map to Dolibarr Order (supplier mode). Open PO balances migrate with status flags preserved. Line items link to the corresponding vendor ThirdParty and item Product records via lookup resolution.

Aptean chargeback records tied to customer deduction codes and retailer contracts have no native Dolibarr equivalent. We create a Dolibarr ExtraFields module for ThirdParty (customer mode) to hold deduction reason codes and a second ExtraFields set on Invoice records to hold chargeback reference fields. During scoping, we build a deduction-code crosswalk mapping each retailer's numeric or alpha-prefixed codes to Dolibarr-compatible string values. Unmapped codes flag for customer review before cutover.

Aptean EDI 850, 810, and 856 documents stored in a proprietary format do not migrate as parsed EDI documents. We extract the functional business data from the Aptean export: order lines from 850 documents map to Dolibarr Order lines; invoice amounts from 810 documents map to Dolibarr Invoice lines; ship notice details from 856 documents map to Dolibarr Expedition (shipping) records with tracking reference. EDI control numbers and transaction timestamps migrate as ExtraFields for audit trail purposes. If Aptean professional services provide a formatted EDI archive, we parse the functional content directly from that export.

Aptean landed costs are calculated at shipment receipt and allocated across items in that shipment; per-unit landed cost is derived, not stored as a static item property. We extract the landed cost components (freight, duty, insurance, agency fees by harmonization code) from the Aptean shipment record, compute the per-unit allocation, and write the final allocated values as ExtraFields on the Dolibarr Product record: pu_landed_cost_freight, pu_landed_cost_duty, pu_landed_cost_total. The original shipment-to-items allocation methodology is documented in a landed cost reference table for customer re-implementation in Dolibarr if needed.

Aptean GL account structure with account type, currency assignment, and department/cost-center rollups maps to Dolibarr Account records. The full account hierarchy (parent-child relationships) migrates for financial reporting continuity. Account type flags (asset, liability, equity, revenue, expense) map to Dolibarr Account categories. Multi-currency accounts preserve currency assignment as Dolibarr ExtraFields.

Outstanding Aptean invoices, credit memos, and payment applications migrate with open/closed status flags preserved. Customer invoices map to Dolibarr Invoice (customer mode); supplier invoices map to Dolibarr Invoice (supplier mode). Credit memos migrate as negative-invoice records. Payment records link to the corresponding invoice. We flag records near payment threshold for pre-cutover verification with the customer's AP/AR team.

Aptean lot genealogy and serial number assignment history stored per transaction map to Dolibarr Product lot/serial batch records linked to stock movements. Full traceability chains including receiving dates, stock movements, and customer shipment links preserve as Dolibarr stock批次 (batch) entries with batch_number, expiry_date, and stock_movement references. We verify that the destination Dolibarr instance has the lot/serial tracking module enabled during scoping.