Migrate from Paragon ERP to Infor CloudSuite Corporate

Paragon Items (products with Style/Color/Size grid support) map to Infor CloudSuite Industrial's Item Master. The Paragon Style/Color/Size dimension structure maps to Infor's product dimensions or requires configuration as a multi-dimension item structure. Item costing methods (FIFO, average, standard) transfer to Infor's cost element setup. GS1 color codes and Canadian tax settings from Paragon do not have direct Infor equivalents and require manual configuration post-migration or a custom field mapping. We resolve the Paragon Item ID to an Infor Item Number at migration time and preserve the original Paragon SKU in a reference field.

Paragon inventory levels tied to Location records map to Infor Inventory by Site. We sequence inventory migration after Location setup in Infor because inventory requires a valid Site reference to land correctly. Paragon's special pricing, production defaults, and inventory attributes transfer as Infor extended properties or inventory-specific fields. Stock on hand, reorder points, and safety stock levels migrate with location-aware Quantity records.

Paragon Customer records map to Infor Customer. Paragon does not have a standalone CRM object; customer data lives in the Sales and Order modules and is referenced throughout shipping and invoicing. We extract customer records with their address associations and payment terms, then map to Infor Customer with bill-to and ship-to address links. Customer-specific pricing rules from Paragon migrate as Infor price lists scoped to the Customer.

Paragon Vendors map to Infor Vendor. Vendor associations on Items (Inventory Vendor records) transfer to Infor's item-vendor linking. We preserve vendor codes, payment terms, and EDI or PO configuration notes from Paragon as a reference document for the customer's admin to re-enter in Infor's vendor setup forms because EDI configuration is not a data migration field.

Paragon maintains a separate address object referenced by Customers, Vendors, and Locations. We deduplicate addresses during migration (identical addresses across multiple Customer records consolidate to one address record in Infor), then link to the respective Customer, Vendor, or Site records. Infor stores addresses within the Customer, Vendor, and Site records rather than as standalone address objects, so we decompose the Paragon address export into the correct Infor address segments at insert time.

Paragon Departments allocate GL postings into separate divisions and are used for profitability reporting by sale type. They map to Infor Departments with the same segment purpose. We map source cost-center codes to Infor Department IDs and verify that the GL account structure supports the department-level posting that the customer uses for internal P&L reporting.

Paragon Entities represent separate DBAs under a single legal entity. These map to Infor Companies, which serve as the legal-entity-level segment in Infor's multi-company structure. We preserve the entity hierarchy from Paragon when migrating chart of accounts and ensure GL postings land under the correct Company segment in Infor. Multi-entity Paragon deployments (three or more DBAs) increase migration complexity because each Entity may have its own GL range, which must be decomposed into separate Infor Company records.

Paragon Locations represent separate warehouses or sites under an Entity and map to Infor Sites. We map source facility codes to Infor Site IDs and ensure inventory quantities and stock positions associate with the correct Site. Infor Sites also carry the financial segment for warehouse-level GL allocation, so the location mapping is a prerequisite for inventory migration.

Paragon supports virtually unlimited custom Attributes and Attribute Values. Infor CloudSuite represents custom attributes as Extended Properties or User-Defined Fields (UDFs) on standard objects. We extract the full Paragon attribute definition schema during discovery and pre-create the corresponding UDF structure in Infor before any data import. This step mirrors Paragon's own attribute-first requirement but in the destination system. Attributes that exist in Paragon but have no populated records are flagged for the customer to confirm before creation in Infor.

Paragon Associations define how any Attribute relates records to each other. The Paragon export includes all attributes, including those that were created and then abandoned, which inflates the association file. We filter to retain only active attribute associations (those where the attribute still exists and is not marked abandoned) before loading into Infor. Infor represents inter-record relationships as cross-reference tables or related-party links; we map the Paragon association type to the equivalent Infor relationship type during the transform step.

Paragon order and transaction data requires screen setup to be completed before import. We verify that the customer has configured the required Infor transaction screens (order, PO, shipment, invoice) during the prerequisite phase and then migrate open and historical orders with line items mapped to the correct Infor Item Number. Closed orders and historical invoices transfer with their original transaction dates preserved as a reference for the customer's finance team to verify. We do not post transactions to Infor's live GL; all transaction history loads as imported records with a flag indicating source system for audit.

Paragon Users map to Infor Users with role assignments preserved as Infor role memberships. We extract user records and map role names, but passwords and authentication credentials do not migrate and must be provisioned fresh in Infor. Owner and assignment fields on Paragon records (Orders, Items) are resolved to the Infor User ID at migration time. Users without a matching Infor account go to a reconciliation queue for the customer's admin to provision before record import resumes.