Migrate from ERPAG to Microsoft Dynamics 365 Business Central

ERPAG Items with SKU, description, cost, price, stock levels, and barcode data map directly to Dynamics 365 Business Central Item records. We use the Get Item IDs and Get Item endpoints and map item_no to Number, description to Description, unit_cost to Unit Cost, unit_price to Unit Price, and quantity_on_hand to Inventory. For items that are BOM parents, we flag them for BOM attachment resolution in a subsequent pass. ERPAG's Advanced plan custom fields on Items require pre-migration schema creation in Business Central before data import begins.

ERPAG Customer records (contact info, billing address, shipping address, financial overview fields, and B2B portal assignment) map to Dynamics 365 Customer records. We export via Get Customer IDs and Get Customer endpoints, and the customer's email address becomes the primary lookup key in Business Central. The financial overview fields (credit limit, payment terms) map to Customer Posting Groups. B2B portal assignment does not migrate; we document the portal access list for the customer's admin to reconfigure in Business Central or via an AppSource B2B accelerator.

ERPAG Suppliers with contact data and purchasing terms map to Dynamics 365 Vendor records. The critical mapping is the double-SKU layer: ERPAG stores the supplier's own SKU alongside ERPAG's internal SKU on each Supplier Item record. We flatten this into two separate Business Central fields (Vendor Item Number on the Vendor ledger entries) and preserve the cross-reference mapping so purchase orders in Dynamics 365 can reference supplier SKUs during PO creation. Payment terms from ERPAG map to Business Central Payment Terms code.

ERPAG Sales Orders with line items, pricing, payment status, and packing list associations map to Microsoft Dynamics 365 Sales Order records. We export via Get Sales Order and Get Sales Order IDs endpoints and include the payment_status column. The Document Date, Posting Date, and Due Date fields are preserved from ERPAG. If the source Sales Order has been partially shipped or invoiced in ERPAG, we create the corresponding shipment and invoice documents in Business Central before closing the order.

ERPAG Invoices generated from Sales Orders carry status, amount, tax, and payment information that map to Microsoft Dynamics 365 Sales Invoice records. We export via Get Invoice IDs and Get Invoice endpoints. Credit notes migrate as Sales Credit Memos linked to the original invoice. Tax amounts from ERPAG must be mapped to Business Central Tax Group codes and VAT Business Posting Group configurations before import; incorrect tax group assignment is the most common post-migration reconciliation issue.

ERPAG 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. In Dynamics 365 Business Central, we resolve the Vendor No., Item No., and Location Code before import. Any partially received purchase orders in ERPAG create matching partially received POs in Business Central. We preserve ERPAG's internal PO number as an External Document No. for audit trail continuity.

ERPAG Quotations (estimates) with full pricing, validity dates, and custom fields map to Microsoft Dynamics 365 Sales Quote records. We export via Get Quotation endpoints and convert quotation status to Business Central Quote Status (Open, Closed, or Converted). Custom fields on Quotations require pre-creation in Business Central. Any quotations converted to Sales Orders in ERPAG prior to migration are handled as Sales Orders, not re-imported as quotes.

ERPAG Work Orders drive manufacturing execution with BOM references, production status, and cost data. We export work order records via the Cube Data export and map to Dynamics 365 Production Order. Estimated versus actual cost fields are preserved. The Work Order's BOM No. must resolve to a matching Routing No. or Production BOM in Business Central; if no BOM exists, we flag it for customer admin to create before the production order can be scheduled. Finished goods quantities from ERPAG work orders map to Item Ledger Entry entries in Business Central.

ERPAG BOMs defining multi-level product structures for manufacturing map to Dynamics 365 Production BOM records. 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 (sub-assemblies) requires flattening into a single-level BOM hierarchy for Business Central unless the customer licenses the Manufacturing module with multi-level routing. We document the nesting structure and recommend the flattening approach during scoping. Active versus inactive BOM status migrates as-is.

Each ERPAG warehouse with independent tax settings, currency, and price lists maps to a Dynamics 365 Location. We export all warehouse configurations including geo-location data. On import, multi-warehouse setup must be matched to the corresponding Business Central Location Code, and the Location's Bin Structure and Inventory Posting Group assignments must be configured before Items can be received or shipped. ERPAG warehouse-level price lists do not have a direct Business Central equivalent; we map them to Customer Price Groups and Sales Prices filtered by Location.

ERPAG custom fields on most objects (linking to external files or arbitrary value fields) are enumerated during scoping and mapped to Business Central custom fields. Custom field definitions exist on Advanced plan only. Business Central stores custom field definitions differently (as table extension fields via AL code or through the Custom Fields page in the UI). We pre-create all destination custom fields in a Sandbox environment before production migration so that the field IDs are stable. Custom field types (text, number, date, lookup) map directly to Business Central FieldClass = Normal with matching DataType.

ERPAG Users with role-based permissions gating access to documents and modules map to Dynamics 365 Users with User Permission Sets and Security Groups. We export user records and role assignments, but permission sets are destination-specific and must be rebuilt in Business Central. Active versus inactive user status migrates as-is, with inactive users created in Business Central with blank passwords pending individual provisioning. ERPAG's Advanced plan Customization and Automation role gates require corresponding Business Central permission set definitions.

ERPAG documents with file attachments and linked-document references are exposed through the file export but not via a dedicated API attachment endpoint. We handle attachments by exporting them as files, associating them to the corresponding Business Central record using the Record Links feature (table 2000000068) or Incoming Documents if the attachments are invoice PDFs. The document filename preserves the ERPAG internal document ID for audit traceability. We do not migrate linked-document references that point to external URLs that are no longer accessible.