Migrate from Paragon ERP to Epicor Prophet 21

Paragon Items with Style/Color/Size grid dimensions map to Epicor Part records with Product Group and Stocking UOM set from Paragon's item category and stocking unit. The Paragon Style becomes the Epicor Part Number prefix, Size maps to a Part UOM Class, and GS1 color codes migrate to Part's Specification or a custom UD field. Costing method (FIFO, Average, Standard) maps from Paragon's costing field to Epicor's Costing ID on the Part. Paragon item alias and substitution records migrate as Part Alternate and PartRevision records in Epicor.

Paragon Inventory levels tied to Locations map to Epicor PartWhse (warehouse-level quantity) and PartBin (bin-level quantity) records. We resolve each Paragon Location ID to an Epicor Site ID before inventory records are inserted. If Paragon stores lot or serial data, we map to Epicor's PartLot and PartBin with serial tracking flags set on the Part. Inventory migration is sequenced after both Locations and Items are confirmed loaded because PartWhse requires a valid PartNum and Site reference.

Paragon Locations representing separate warehouses or sites under an Entity map to Epicor Sites. Each Paragon Location maps to an Epicor Site with the Site code, name, and address preserved. GL department associations on the Paragon Location are noted for later chart-of-accounts mapping. Sites must be established in Epicor before PartWhse and inventory transaction records can reference them.

Paragon's multi-entity structure with separate DBAs under a single legal entity maps to Epicor's Company records. Each Paragon Entity becomes an Epicor Company with its own chart of accounts, fiscal calendar, and tax jurisdiction settings. GL segment values from Paragon's entity-location-department hierarchy decompose into Epicor's Company-Site-Branch account structure. If the source has a flat chart of accounts, we create the segment mapping matrix before any GL balances are loaded.

Paragon Departments used for GL profitability allocation and reporting by sale type map directly to Epicor Department records. We preserve the department code and name and map source cost-center codes to Epicor's Department values used in GL journal entries and reporting.

Paragon Customer records map to Epicor Customer with ShipTo and BillTo addresses preserved as Customer records. The Paragon customer code becomes the Epicor Customer ID, and the customer name, phone, email, and payment terms map to standard Epicor Customer fields. Customer credit limits migrate as CreditLimit on the Customer. Open AR balances from Paragon are noted for AP/AR carryforward reconciliation separately.

Paragon Vendor records map to Epicor Vendor with vendor code, name, address, and payment terms preserved. Vendor associations linked to Items (inventory vendor records) migrate as PartPlant records with the preferred vendor flag set. EDI vendor configuration and PO setup from Paragon are flagged in the inventory document for the customer's Epicor admin to reconfigure because these are setup-level constructs rather than data records.

Paragon maintains a separate address object referenced by Customers, Vendors, and Locations. We deduplicate addresses during migration by comparing full address strings and create a single Epicor Address record per unique address, then link it to the appropriate Customer, Vendor, or Site via the respective relationship table. Country codes and tax jurisdiction mapping from Paragon's Canadian tax handling migrate to Epicor's Tax Region.

Paragon Attributes and Attribute Values are custom schema elements that do not have a direct Epicor standard-object equivalent. We map Paragon attributes to Epicor UD fields: short text attributes become string UD fields on the relevant Part or Customer table; list-type attributes become dropdown UD fields with the allowed values set to the Paragon Attribute Values. The migration user must pre-create the UD field schema in Epicor before records referencing attributes are imported; we provide the UD field creation manifest from the Paragon attribute export.

Paragon Associations define how records relate to each other through attributes. We export association data via Paragon's Universal Translator, filter out all abandoned attributes (Paragon includes these by default and they cause oversized noisy imports), and map the active associations to Epicor PartRevision BOM links, Part links, or custom UD table records depending on the association type. Association migration is sequenced after attribute schema is confirmed in Epicor.

Paragon Users map to Epicor Users by extracting user records and role assignments from the source. We preserve display name, email, and security role names in a user mapping table. Passwords and authentication credentials do not migrate; Epicor admin provisions new user access after migration. Assignment fields on records (Owner, CreatedBy) are mapped by email match against the Epicor user list with a reconciliation queue for any unmatched owners.

Paragon Sales Orders map to Epicor OrderHed (header) and OrderDtl (detail) records. Paragon Order Status maps to Epicor OrderRel.OrderReleasestatus and OrderHed.OpenOrder flag. Open orders migrate with their original order dates and requested ship dates preserved. Historical orders migrate as OrderHed records with a closed status flag. Line item SKUs are resolved against the Part migration to ensure PartNum references are valid at insert time. Screen setup from Paragon must be verified before this step because Paragon enforces screen configuration before transaction imports can succeed.

Paragon Purchase Orders map to Epicor POHeader and PODetail. Vendor references resolve via the Vendor mapping. Open PO statuses map to Epicor POHeader.OpenPo flag. Historical POs with full line detail migrate with close dates set. PO approvals and workflow routing are not migrated; we document the approval matrix from Paragon for the customer's Epicor admin to configure in Epicor's approval routing.

Open AP and AR records from Paragon are flagged as carryforward items requiring reconciliation separately from the main migration scope. These records involve complex GL distribution, payment terms, and tax calculation that must be verified by the customer's finance team against Paragon's trial balance before posting in Epicor. We extract the open AP/AR listing with customer/vendor references, aging buckets, and amounts for finance-led reconciliation rather than automated import.