Migrate from Paragon ERP to Acumatica

Paragon customers map directly to Acumatica Customers with primary contact, billing address, and shipping address fields aligning 1:1. Paragon customer types (wholesale, contractor, retail) map to Acumatica Customer Classes, requiring a value-mapping entry for each type before the customer import runs. If Paragon stores credit limits or payment terms, those map to the CreditLimit and TermsID fields respectively, provided corresponding Terms records exist in Acumatica.

Paragon vendors map to Acumatica Vendors with the vendor's main address, remit-to address, and payment terms aligning directly. Paragon vendor categories need a corresponding Vendor Class record created in Acumatica before the vendor import runs — each unique Paragon category requires a matching VendorClassID in Acumatica's Vendor Classes screen. Without pre-created vendor classes, the import script will fail on the category mapping step.

Paragon items carry style/color/size grid data as attributes — Acumatica handles this via the Stock Item's Dimensions tab (Size, Color, Template). We split Paragon's attribute columns into separate dimension records in Acumatica before linking them to the parent item. Non-stock Paragon items map to Acumatica Non-Stock Items.

Paragon purchase orders map to Acumatica Purchase Orders with vendor line items. The PO number, date, terms, and line description/quantity/unit cost carry over. Acumatica requires the vendor record to exist before the PO can be linked — vendor import must complete first.

Paragon sales orders map to Acumatica Sales Orders. Line items (item ID, quantity, unit price, warehouse) migrate as order details. Acumatica requires the customer and inventory items to exist before the sales order can post — customer and item imports run first in dependency order.

Paragon chart-of-accounts entries map to Acumatica GL Accounts. Account number, name, type (Asset, Liability, Equity, Income, Expense), and active status carry over directly. Sub-account structure in Paragon maps to Acumatica's Segment Codes or Sub-Account field depending on your chart configuration.

Paragon Departments track profitability by division (wholesale, contractor, retail) and map to Acumatica Branches if each department represents a separate legal entity. If departments are internal cost centers within one entity, they map to Acumatica's sub-account segment or a custom Project dimension — the Paragon Department export determines the mapping approach.

Paragon Entities represent separate DBAs under one legal entity and map to Acumatica Branches. Each Paragon Entity needs its own Acumatica Branch configured with a default GL posting account set. Paragon's entity-specific AP and AR accounts link to the corresponding branch's subledger control accounts.

Paragon Locations map to Acumatica Warehouses with Warehouse ID, name, and address carrying over directly. Each warehouse must be associated with an Acumatica Branch — if Paragon locations span multiple entities, multiple branches need pre-configuration before warehouse import. The branch-warehouse linkage is mandatory in Acumatica before inventory can be assigned to a location.

Paragon lot and serial numbers attached to inventory receipts migrate as Lot/Serial classes in Acumatica's Stock Items screen. Each lot/serial class must be linked to an Inventory ID before the historical lot data can import — we create the link during the item migration step.

Paragon shipment records map to Acumatica Shipments linked to the originating Sales Order. Shipment date, carrier, tracking number, and shipped quantities migrate. Acumatica requires the linked Sales Order to be in an open status before the shipment can be created — order import must precede shipment import.

Paragon AP and AR receipts map to Acumatica Payments. Vendor payments link to vendor documents; customer payments link to AR invoices. The original receipt date, amount, and payment method carry over. Unapplied balances in Paragon become open payment records in Acumatica.

Paragon's shared attributes table stores custom data for any object — customers, items, orders, etc. We read every unique attribute from the Paragon export and create corresponding custom fields in Acumatica (e.g., Customer__c, Item__c) using Acumatica's screen customization. The attribute value maps to the custom field value per record. Attributes without a clear Acumatica equivalent are preserved as reference fields.

Paragon user records resolve to Acumatica Users by email match. The user's display name, email, and active status carry over. Paragon role assignments (e.g., Admin, Warehouse Manager) do not map directly to Acumatica roles — your Acumatica admin assigns Acumatica roles by email group post-migration.

Paragon EDI integration settings lack a native Acumatica equivalent, so we export the complete EDI configuration as a structured JSON document. This includes partner profiles, transaction set definitions (such as 810, 850, 856), and field-level mapping rules. Your Acumatica implementation partner then rebuilds the EDI setup using Acumatica's import/export scenario framework or through a certified third-party EDI connector like TrueCommerce or SPS Commerce.