Migrate your Paragon ERP data

Items are the core inventory object in Paragon ERP with support for Style/Color/Size grids, costing methods, alias and substitution records, and vendor associations. The platform requires correct column names for import. We map source SKUs to Paragon item IDs and preserve alias/substitution relationships during migration.

Inventory levels are tied to Locations and Items. The import supports bulk adjustments, special pricing, production defaults, and inventory attributes. We sequence inventory migration after Locations are established and map warehouse codes between source and Paragon location identifiers.

Customer records are referenced throughout the order and shipping modules. Paragon does not surface a standalone CRM object — customer data lives in the Sales and Order modules. We extract customer records and map associated addresses and contact associations to preserve relationships.

Vendors are linked to Items via Inventory Vendor records. We preserve vendor associations and payment terms during migration and map vendor codes to match any existing EDI or PO setup already configured in Paragon.

Paragon maintains a separate address object referenced by Customers, Vendors, and Locations. The platform has dedicated import/export instructions for address data. We deduplicate addresses during migration and map them to their parent records after validating Canadian and US tax exemption configurations.

Departments allocate GL postings into separate divisions within a single GL account and are used for profitability reporting by sale type (wholesale, contractor, retail). We map source cost-center codes to Paragon department IDs and preserve the department hierarchy during chart of accounts migration.

Entities represent separate DBAs under a single legal entity. This is a distinct Paragon-level construct. We preserve the entity structure when migrating chart of accounts and ensure GL postings land under the correct entity during cutover validation.

Locations represent separate warehouses or sites under an Entity and are set wherever GL departments are set. We map source facility codes to Paragon location IDs and ensure inventory quantities and staging areas are correctly associated after migration.

Associations define how any Attribute in the system relates records to each other. The export includes all attributes, including abandoned ones, making the file large and noisy. We filter out unused attributes before import, retain the structural associations, and upload via the reports-and-data import card under Settings.

Paragon supports virtually unlimited custom Attributes and Attribute Values. These must be configured before any import can reference them. We extract attribute definitions from the source system and sequence attribute creation as the first step in the migration runbook.

Users are managed under User Management in Settings. We extract user records and map role assignments, but we do not migrate passwords or authentication credentials. Owner and assignment fields on records are remapped to destination user IDs after migration.

Order and transaction data must have screen setup completed before import. Paragon supports order status, reservation, and fulfillment tracking. We extract open and historical orders, map line items to Items, and validate against the destination screen configuration before upload.