Migrate your ERPAG data

Items are the core inventory object with SKU, description, cost, price, stock levels, and barcode data. We export via the Get Item IDs / Get Item endpoints and map to the destination's product or item object. Multi-warehouse stock quantities are queried per warehouse and merged or split according to destination logic.

Customer records include contact info, billing address, shipping address, financial overview fields, and B2B portal assignment. We pull via Get Customer IDs / Get Customer and handle the customer-specific price tier assignment that maps to B2B portal categories on import.

Supplier records hold contact data, double-SKU fields (the supplier's own SKU alongside ERPAG's SKU), and purchasing terms. We export via Get Supplier endpoints and preserve the cross-SKU mapping so purchase orders land cleanly in the destination system.

Sales Orders carry line items, pricing, payment status, and packing list associations. We export via Get Sales Order / Get Sales Order IDs and include the payment_status column exported in the XLS. These map 1:1 to the destination's sales or order object.

Invoices are generated from Sales Orders and carry status, amount, tax, and payment information. We export via Get Invoice IDs / Get Invoice. Credit notes are a related document type available in ERPAG and are included in the invoice export scope.

Purchase Orders reference Suppliers and Items with double-SKU entry, automatic fulfillment logic, and goods-received state. We export via Get Purchase Order endpoints and include goods received notes. PO generation from minimum-stock triggers is scoped separately and not migrated as static records.

Quotations (estimates) are convertible to Sales Orders and carry full pricing, validity dates, and custom fields. We export via Get Quotation endpoints and map to the destination's quote or estimate object, preserving the BoM-based estimate flag where present.

Work Orders drive manufacturing execution and carry BOM references, production status, and cost data. We export work order records via the Cube Data export. Estimated vs. actual cost fields are preserved separately to support margin analysis in the destination.

Each warehouse can carry independent tax settings, currency, and price lists. We export all warehouse configurations including geo-location data. On import, multi-warehouse setup must be matched to the destination's site or location model; some destinations do not support per-warehouse currency and require consolidation.

Custom fields exist on most objects and can be linked documents (pointing to external files) or arbitrary value fields. We enumerate all custom field definitions during scoping and map them to destination custom fields, flagging linked-document fields for separate file migration handling.

Users carry role-based permissions that gate access to documents and modules. We export user records and role assignments, but permission sets are destination-specific and must be rebuilt. Active vs. inactive status is preserved for licensing reconciliation.

BOMs define multi-level product structures for manufacturing. We export BOM records as part of the Items export where BOMs are associated, or as standalone work order source data. Multi-level BOM nesting is preserved as a parent-child structure in the destination.

Documents in ERPAG can carry file attachments and linked-document references. The platform exposes these through its file export but not via a dedicated API attachment endpoint. We handle attachments by downloading via authenticated session and re-uploading to the destination alongside the associated record.

The B2B portal allows customers, resellers, and field agents to create orders, view financial overview, and pay invoices via Stripe. Portal configuration (price tiers, categories, access rules) is Advanced-plan only. We export portal assignments and recreate customer portal access rules in the destination where equivalent functionality exists.