Migrate from Shipedge to Acumatica

ShipEdge Products (SKU, product name, description, weight, dimensions) map to Acumatica Stock Items. The Stock Item's Template ID governs default warehouse, posting class, and unit-of-measure schedule. FlitStack resolves UOM conversions (eaches → cases) using ShipEdge's variant-level UOM data and maps them to Acumatica's UOM Schedule attached to the Stock Item. Active / discontinued status carries as the Stock Item's Availability field.

ShipEdge variant records (size, color, style modifiers on a parent SKU) map to either Acumatica's variant attributes on the Stock Item or to separate Non-Stock Items if the variant represents a kitted or drop-shipped component. The mapping plan determines whether variants collapse to attributes or spawn distinct Stock Item records based on whether ShipEdge tracks them as independent inventory units.

ShipEdge Suppliers map to Acumatica Vendors. ShipEdge supplier-level notes, payment terms, and lead-time data load into the Vendor's Terms tab and the Purchasing Details screen. Remit-to addresses become Vendor Locations in Acumatica. If ShipEdge tracks multiple contacts per supplier, those map to Vendor Contacts in Acumatica.

ShipEdge POs migrate to Acumatica Purchase Orders, preserving PO number, vendor reference, line items (linked to Stock Items or Non-Stock Items), and expected delivery date. ShipEdge PO approval workflows do not migrate — they become an Acumatica approval map note for the purchasing team to rebuild using Acumatica's Approval Router.

Open ShipEdge Sales Orders map to Acumatica Sales Orders. The customer in ShipEdge must first exist as an Acumatica Customer (with Customer Class and Tax Zone assigned). ShipEdge order lines map to Sales Order details linked to Stock Items. Shipment status (unshipped, partially shipped, shipped) carries as the Sales Order's status field — fully shipped lines are closed in Acumatica.

ShipEdge current quantity-on-hand per warehouse becomes an Acumatica Inventory Receipt (IN.20.20.00) that posts opening balances to the Inventory account for the target Branch and Warehouse. FlitStack generates one receipt per ShipEdge warehouse. The IN Preferences setting for 'Update GL' is evaluated per Acumatica's recommended sequence — inventory balance first, GL posting verified, then GL flag enabled for ongoing transactions.

ShipEdge warehouses map to Acumatica Warehouse records attached to an Acumatica Branch. The Branch carries the legal entity and financial posting group; the Warehouse carries location-level settings (address, lead time, default carrier). Multi-tenant ShipEdge setups (3PL managing multiple clients) map each client's inventory to a separate Acumatica Branch with its own warehouse.

ShipEdge carrier records (carrier name, account number, service types) map to Acumatica Ship Via codes. Rate-shopping preferences — ShipEdge's live rate comparison across carriers — do not transfer. We export the carrier configuration as a structured JSON file that the Acumatica consultant uses to configure Shipping Rules in the WMS screen. FedEx, UPS, USPS, and DHL service types become individual Ship Via entries with their respective account credentials.

ShipEdge's per-order activity timeline (picker assignment, label print, batch assignment, carrier scan events) has no direct Acumatica equivalent at the Sales Order level. FlitStack preserves the activity log as an attached note on the Sales Order with timestamps and usernames so the fulfillment team retains the audit trail even if the granular events don't map to an Acumatica screen.

ShipEdge's channel and marketplace connections (Shopify, Amazon, Walmart, Magento) and 3PL integration credentials have no Acumatica equivalent. We export the connection configuration as a reference document. The Acumatica implementation team rebuilds channel integrations via Acumatica's eCommerce connectors, Celigo, or a middleware like Tray.io.

ShipEdge kit definitions (parent SKU composed of component SKUs with fixed or variable quantities) map to Acumatica's Inventory Kit or Non-Stock Item depending on whether the kit is shippable from inventory or made-to-order. FlitStack preserves the kit structure as a component explosion so the Acumatica consultant can rebuild it using the Bill of Materials screen if light manufacturing is in scope.

ShipEdge RMA records map to Acumatica Return Sales Orders (a Sales Order with a negative quantity type) linked to the original Sales Order via the Order Nbr. reference. RMA receipt into inventory is modeled as an Inventory Receipt against the same Stock Item, with the reason code preserved in a custom field.