Migrate from Access SupplyChain to Acumatica

Access SupplyChain customer records map to Acumatica's Business Account (BAccount) extended with Contact records. Primary billing addresses map to BAccount address fields; shipping addresses map as separate address records. Payment terms and credit limits migrate to the BAccount's FinSettings tab.

Vendor records from Access SupplyChain map to Acumatica BAccount with Vendor = true. Supplier addresses, contacts, and payment terms transfer to the Vendor DAC's corresponding fields. Multi-site suppliers with distinct addresses per site may require splitting into multiple vendor address records in Acumatica.

Access SupplyChain stock items marked as stocked inventory become Acumatica InventoryItem records with ItemType = Stock Item. Unit of measure, default warehouse, and lead times transfer. Lot/serial number settings map to Acumatica's lot/serial classes. Additional attributes such as safety stock levels, reorder points, and standard cost are also migrated to ensure accurate inventory valuation and replenishment planning.

Non-stocked products in Access SupplyChain migrate as Acumatica InventoryItem with ItemType = Non-Stock Item. These items appear on purchase documents but do not affect inventory counts. Custom fields on the source item map to User-Defined Fields on the InventoryItem DAC.

Service entries in Access SupplyChain become Acumatica InventoryItem with ItemType = Service. Service items are used on sales orders and purchase orders for labor or fees. Default tax category and account mappings from the source service definition are preserved. If the service has associated expense codes, those are transferred to the Acumatica expense account field for proper cost tracking.

Open and closed purchase orders migrate with all line items, quantities, and amounts. Status mapping converts Access SupplyChain status values to Acumatica POOrder.status values (Open, Pending Approval, Closed). Expected and actual receipt dates are preserved as custom fields if needed for reporting continuity.

Each PO line maps to a POOrderLine with vendor part number, ordered quantity, unit cost, and line description. The destination inventory item ID references the mapped Stock or Non-Stock item. Line-level custom fields migrate as User-Defined Fields on POLine. All line discounts, taxes, and freight charges are preserved as separate sub‑entities to retain pricing integrity.

Sales orders transfer with customer reference, order date, and ship-by date. Status conversion applies Acumatica's sales order stage values. Historical orders maintain their original order dates; in-flight orders are flagged for review before shipment processing in Acumatica. Any extended attributes attached to the line, such as project codes or cost centers, are also migrated as User-Defined Fields on the SOLine DAC to preserve analytical detail.

Sales order lines map to SOOrderLine with inventory item reference, quantity, unit price, and discount. The destination item ID points to the mapped inventory item. Line-level notes from Access SupplyChain transfer as SOLine-extensible fields or comments. If a site contains multiple zones, each zone becomes a separate INLocation under the same warehouse, preserving the physical layout for accurate picking and putaway processes.

Access SupplyChain sites with bin locations map to Acumatica INSite (warehouse) and INLocation (bin/zone) records. Multi-level site hierarchies are flattened into warehouse-location relationships. Zone types (receiving, picking, bulk) require mapping to Acumatica location classes. Warehouse assignments are validated against the target INSite, and any mismatches are flagged for manual review before final migration.

Contacts associated with vendors or customers migrate to the Contact DAC with the parent BAccount linked via Acumatica's entity-key mechanism. Email, phone, job title, and address fields transfer directly. Contact-specific custom fields map to User-Defined Fields on Contact. If a contact has multiple roles such as billing and shipping, each role is recorded as a separate contact reference to preserve communication preferences.

Access SupplyChain custom properties require mapping to Acumatica User-Defined Fields on the corresponding DAC. Field types are converted: text properties become PXString or PXLongString, numeric fields become PXDecimal or PXInt, date fields become PXDate. A schema setup plan details which DAC needs which UDFs before migration runs.

Documents attached to purchase orders, sales orders, or inventory items are extracted, re-uploaded to Acumatica Files, and linked to the corresponding record. File size limits follow Acumatica's attachment constraints. Inline images in notes are downloaded and re-hosted as Acumatica-attached files.

Access SupplyChain owner IDs are resolved by email match against Acumatica users. Unmatched owners are flagged before migration so the Acumatica administrator can create accounts or assign records to a fallback owner. Permissions and role assignments do not transfer — those are destination-side configuration.

Approval chains and workflow rules in Access SupplyChain have no direct Acumatica equivalent and do not migrate. Acumatica uses Approval Maps for document approvals and Business Events for automated triggers. We export Access SupplyChain workflow definitions as a reference document for rebuilding in Acumatica's automation framework.