Migrate from Paragon ERP to Dolibarr ERP

Paragon Items map to Dolibarr Products with SKU, description, and unit of measure preserved. The Paragon item type (stock, non-stock, service) maps to Dolibarr's product type field. Vendor associations migrate as Dolibarr supplier references on the product record. If the Paragon item uses a Style/Color/Size grid, we split each grid cell into a separate Dolibarr product and create a configurable parent product that references them via customizable options.

Paragon apparel grids store one row per Style/Color/Size combination with individual SKU, inventory, and pricing per cell. Dolibarr has no native grid system. We split the grid into individual Dolibarr products (one per size/color variant) and create a configurable parent product with customizable options for Size and Color. The parent product carries the base item price; variant-specific pricing and on-hand quantities map to the child product records. This is the most manual part of apparel migrations and requires a size run inventory count before migration.

Paragon Locations (warehouses, distribution centers, retail sites) map directly to Dolibarr Warehouses. Physical stock quantities per Item-Location combination migrate as Dolibarr stock entries tied to the resolved warehouse ID. We validate that each Paragon Location has a corresponding Dolibarr warehouse created before inventory import begins.

Paragon Customers map to Dolibarr Third Parties with the Customer checkbox enabled. Address records deduplicate by normalized address string and link to the Third Party. Customer-specific pricing and payment terms migrate as Extra Fields or direct fields on the Third Party record. Paragon's customer type (wholesale, retail, contractor) migrates as a Category tag in Dolibarr.

Paragon Vendors map to Dolibarr Third Parties with the Supplier checkbox enabled. Payment terms from Paragon (Net 30, Net 60, etc.) convert to Dolibarr Payment Term conditions. Vendor-specific lead times and EDI/PO configuration references migrate as notes since Dolibarr does not have a native EDI configuration object. We deduplicate vendor addresses before import.

Paragon's Department-Entity-Location GL segmentation has no single Dolibarr equivalent. Departments map to Dolibarr Categories for segmentation and reporting purposes. For multi-entity Paragon customers with separate DBAs, we review whether the customer needs true multi-company isolation (separate legal entities requiring separate Dolibarr instances) versus departmental segmentation (which Dolibarr Categories handle). This decision is made during discovery because it changes the migration architecture significantly.

Paragon Associations define record-to-record relationships using Attribute Values. Dolibarr has no native equivalent for cross-record associations. We evaluate each association type: those functioning as categorization become Dolibarr Categories; those functioning as true inter-record links (e.g., a substitution record linking two Items) become Note records with structured relationship metadata. We filter out abandoned Paragon attributes before migration to prevent over-populating the Dolibarr category namespace.

Paragon Sales Orders map to Dolibarr Customer Orders with status preserved (Draft, Submitted, Shipped, Invoiced). Line items reference migrated product IDs, quantities, and unit prices. Historical orders migrate with original timestamps preserved. Paragon's screen configuration for orders must be recreated in Dolibarr's Order module settings before import.

Paragon Purchase Orders map to Dolibarr Supplier Orders with vendor references resolved to migrated Third Party IDs. Order status (Draft, Approved, Received, Closed) migrates to Dolibarr's status model. Received quantities link to the corresponding warehouse stock entries. Historical PO data migrates with original timestamps.

Open Accounts Payable and Accounts Receivable records from Paragon migrate as Dolibarr Third Party accounting entries linked to the corresponding customer or vendor Third Party. Invoice reference numbers, amounts, due dates, and aging buckets migrate as individual invoice lines. We preserve original transaction dates and invoice numbers for audit trail purposes.

Paragon Users map to Dolibarr Users with login, name, and email preserved. Role assignments (Admin, Standard User, etc.) map to Dolibarr permission profiles. We do not migrate passwords or authentication credentials; the customer resets credentials post-migration. Users with no active Dolibarr equivalent are placed in a reconciliation queue.

Paragon maintains separate Address records referenced by Customers, Vendors, and Locations. We deduplicate addresses by normalized street, city, state, postal code, and country before import to prevent duplicate address records in Dolibarr. Shipping and billing address flags migrate as address type labels on the linked Dolibarr Third Party.