Migrate from Paragon ERP to Microsoft Dynamics 365 Business Central

Paragon Items map to Dynamics 365 Product2. The Style/Color/Size grid in Paragon produces multiple rows per product variant; we normalize these into a single Product2 with product dimensions (Color, Size, Style, Configuration) set via a product dimension group in Dynamics. The Paragon Item alias and substitution records map to the Sales and Service product associations in Dynamics. Costing method (Standard, Average, FIFO) transfers to the Dynamics product costing configuration. SKU (hs_sku equivalent in Paragon) becomes the Dynamics Product number field.

Paragon Customer records map to Dynamics 365 Customer entities. Dynamics maintains a separate Customer master that can be a Person or Organization, which covers both B2B and B2C customer types that Paragon handles through customer type fields. Customer addresses migrate as party addresses linked to the Customer. Customer-specific pricing and discounts in Paragon map to Dynamics price lists and line discount groups. Credit limits and payment terms transfer to the Customer posting profile in Finance and Operations or to the Customer card in Business Central.

Paragon Vendors map directly to Dynamics 365 Vendor entities. The Inventory Vendor associations (preferred vendor per item) transfer to the Dynamics vendor product master associations. Payment terms and vendor-specific discounts migrate to vendor posting profiles. EDI configurations from Paragon (if the vendor EDI setup exists) are flagged as requiring manual reconfiguration in Dynamics EDI modules because EDI partner profiles are destination-specific setup artifacts.

Paragon maintains a standalone address object referenced by Customers, Vendors, and Locations. These migrate to Dynamics 365 postal address tables tied to the Party record. We deduplicate addresses during migration using a hash of the address fields plus country code, keeping one canonical address per party-role combination. Multiple addresses per party (invoice versus delivery) map to Dynamics address purpose codes. Paragon's abandoned address records are excluded from the migration export.

Paragon Departments allocate GL postings to separate divisions and are used for profitability reporting by sale type. These map to Dynamics 365 financial dimension values under the Department dimension. The Paragon department code becomes the dimension value, and the department name becomes the dimension value description. We extract all active Paragon departments and pre-create the corresponding dimension values in Dynamics before any GL posting data migrates.

Paragon Entities (DBAs under a single legal entity) require careful decomposition in Dynamics. Each Paragon Entity maps to a separate Dynamics Legal Entity in Finance and Operations, with its own chart of accounts and posting profile, or to a Business Unit in Business Central with segment values on accounts. If Paragon has three DBAs (ParentCo, DBA-Alpha, DBA-Beta), we create three corresponding legal entities in Dynamics and map the account code segments accordingly. The source entity identifier is preserved as a custom field for audit trail and inter-entity reporting.

Paragon Locations represent separate warehouses or sites under an Entity and are set wherever GL departments are set. These map to Dynamics 365 Sites and Warehouses. We extract the location code, name, and address from Paragon, create the corresponding site and warehouse in Dynamics, and link them to the legal entity that owns the location. Inventory quantities and bin-level data transfer to the warehouse management module if the destination uses the Dynamics 365 Finance and Operations WMS license.

Paragon inventory levels are tied to Items and Locations. These migrate to Dynamics 365 inventory on-hand records keyed to the item number and inventory dimension (Site, Warehouse, Location, Batch, Serial). We migrate open quantities as the current on-hand balance; historical adjustment transactions are flagged as read-only ledger entries because Dynamics does not maintain an open inventory transaction log equivalent to Paragon's adjustment history. Paragon's special pricing per inventory item maps to Dynamics trade agreements.

Paragon Associations define how Attributes relate records to each other and can be multi-directional. Dynamics 365 has no direct equivalent to Paragon's flexible association model. We convert associations to one of three patterns depending on type: for item-to-item associations (substitutes, accessories), we use Product2 related products; for record-to-record metadata associations, we use custom lookup fields or many-to-many tables; for classification associations, we use option sets on the primary entity. We filter out abandoned attribute columns from the Paragon association export before mapping.

Paragon Attributes map to Dynamics 365 custom fields on the relevant entity (Item, Customer, Vendor, Order). The attribute prerequisite sequencing constraint is enforced in the migration runbook: we extract all active Paragon attribute definitions first, pre-create the corresponding Dynamics custom fields or option set values before any record import, then validate the schema before proceeding. This is a blocking prerequisite in Dynamics just as it is in Paragon.

Paragon Users migrate to Dynamics 365 Users. We extract user records with role assignments and map Paragon role names to Dynamics security roles. Authentication credentials do not transfer; users are provisioned with temporary passwords or invited via email-based activation in the destination tenant. Owner and assignment fields on records migrate by resolving the Paragon user reference to the Dynamics User ID via email match.

Paragon open orders migrate as active Sales Orders in Dynamics 365. Historical closed orders migrate as read-only archived order records to preserve audit history without cluttering the operational database. The Paragon screen configuration prerequisite must be validated before order import: all order type screens (sales order, purchase order, shipment, invoice) must have their screen definitions in place in Dynamics before the migration step runs, or the order import fails at the document type level. Open order line items, quantities, pricing, and taxes transfer to the Dynamics order lines with item number resolution via the product mapping.