Migrate from Paragon ERP to Odoo ERP

Paragon Items with Style/Color/Size grid rows decompose into Odoo Product Templates (one per Style) with Product Variants generated from each unique combination of Color and Size attribute value. The Paragon item hs_sku or alias becomes the Odoo Product Template's default_code. We extract the full grid export from Paragon's Universal Translator, pivot it into Odoo's variant generation format, and create Attribute sets (Color, Size) in Odoo before importing the template. GS1 color codes from Paragon are stored as a custom field on the Odoo variant for EDI and barcode alignment. Paragon's costing method (Standard, Average, FIFO) maps to Odoo's product costing configuration per template.

Paragon Locations (warehouses) map to Odoo Warehouse records, each with their own Stock Location hierarchy (Internal Location > Shelf > Bin). Inventory quantities by Item and Location migrate as Odoo Stock Quants, with lot and serial number support preserved where Paragon tracks these. We map Paragon location codes to Odoo warehouse IDs during the transform phase and validate that On-Hand quantity totals match between systems before closing the migration window. Paragon's special pricing and production defaults on inventory migrate as Odoo pricelist rules or reordering rules on the Product Template.

Paragon Customer records map to Odoo Partner records with partner_type = contact. The customer name, email, phone, and all addresses migrate directly. Paragon maintains a separate Address object referenced by Customers, Vendors, and Locations; we deduplicate addresses during migration by matching address string plus postal code and create a single Odoo Partner record with multiple delivery addresses (multi-address on one partner, not separate records). Customer payment terms from Paragon migrate as Odoo Property Payment Term on the Partner record.

Paragon Vendor records map to Odoo Partner records with partner_type = vendor. Vendor codes and EDI identifiers from Paragon are preserved in the Odoo Partner record for PO and EDI workflows. The vendor association on Paragon Items (which vendor supplies which SKU) migrates as Odoo Supplier Info records on the Product Template, including the vendor product code and lead time. Payment terms from Paragon vendor records map to Odoo Property Payment Term on the vendor Partner.

Paragon's separate address object is resolved during Customer and Vendor migration by matching address fields. We deduplicate identical address strings and assign each unique address to the correct Odoo Partner as a delivery, invoice, or contact address. Multi-entity Paragon setups may have the same physical address used by different Entities; we preserve the Entity context by linking each address use to the correct Odoo company record in multi-company configurations.

Paragon Departments allocate GL postings into separate divisions for profitability reporting (wholesale, contractor, retail). These map to Odoo Analytic Accounts at the company level. We extract the department hierarchy from Paragon, create a corresponding Analytic Account structure in Odoo, and configure Analytic Distribution on Odoo journal entries during migration so that historical GL postings land in the correct Analytic Account. Department codes become Analytic Account codes for reconciliation.

Paragon Entities represent separate DBAs under a single legal entity. In Odoo, these map to the multi-company configuration: each Paragon Entity becomes an Odoo Company record, with shared Warehouses optionally scoped per company. We create all Odoo Company records first, configure inter-company rules (if any), and then map GL segment references in Paragon to the corresponding Odoo company_id on all migrated records. Multi-entity Paragon setups with inter-company AP/AR require Odoo inter-company journal entries to be configured post-migration.

Paragon Locations (separate warehouses or sites under an Entity) map to Odoo Warehouse records, each with a Stock Location hierarchy. We map Paragon location codes to Odoo warehouse IDs, preserving the location-specific inventory quantities and shipping point assignments. If Paragon locations have distinct GL department assignments for cost allocation, we set the corresponding Analytic Account on each Warehouse or configure Stock Rules per warehouse to route fulfillment correctly in Odoo.

Paragon custom Attributes and Attribute Values migrate as Odoo Product Attributes and their corresponding Attribute Values (for product variants). We extract all active attribute definitions from Paragon first, create them in Odoo before any product import, and assign them to the relevant product categories. This sequencing mirrors the prerequisite-first rule that Paragon enforces on its own import but which is not automatic in Odoo; we enforce it in the migration runbook to ensure data integrity. Abandoned Paragon attributes are excluded from the Odoo import scope.

Paragon Associations define how Attribute records relate to each other (e.g., which style variants can be combined with which color options). Odoo does not have a native Associations equivalent, so we map these to Odoo Product Category hierarchy and Tags. Complex multi-attribute Association rules that enforce valid variant combinations in Paragon are documented as Odoo product variant configuration rules in the migration handoff document, for the customer's admin to implement via Odoo Studio or developer customization if the business logic is strict.

Paragon User records map to Odoo User records by matching email address. Role assignments in Paragon map to Odoo Access Rights groups (Inventory User, Sales User, Accountant, etc.). We do not migrate passwords or authentication credentials. Owner and assignment fields on Paragon records (Items, Orders) are resolved against the User mapping table during migration, with any unresolved owners flagged in the reconciliation report for the customer's admin to provision before final record import.

Open Paragon Sales Orders and Purchase Orders migrate to Odoo Sale Orders and Purchase Orders respectively, preserving order status (draft, confirmed, done), line items with quantities and prices, and partner references. Paragon's transaction screens must be configured before order import in Paragon; in Odoo, we pre-create the warehouse and partner records first so that Order validation does not fail on missing references. Historical closed orders (fully invoiced, shipped) are migrated as sale order records with their final state for reporting continuity. We do not migrate workflows or approval rules; the customer's admin configures Odoo order approval sequences post-migration.