Migrate from Proteus ERP to Dolibarr ERP

Proteus ERP customer records map to Dolibarr ThirdParty objects. Contact data (name, email, phone, address) migrates directly. Buying habits and referral source fields from Proteus map to Dolibarr extra-fields that we configure during scoping. If the customer uses Proteus's CRM module, we also create Dolibarr Contact records linked to the ThirdParty. Deduping uses email as the primary key.

Proteus ERP vendor records map to Dolibarr ThirdParty with the Supplier type flag set. Vendor code mapping requires a collision check against existing Dolibarr supplier records; we prefix vendor codes with VND- during import if collisions are detected.

Proteus ERP item records (SKU, description, stock levels, pricing tiers, revenue center assignments) map to Dolibarr Product records. Multi-revenue-center flags from Proteus translate to Dolibarr warehouse locations (stock per warehouse). Pricing tiers map to Dolibarr price lists attached to the Product. We create warehouse records in Dolibarr before product import so stock levels land in the correct location.

Open and historical sales orders map to Dolibarr Orders. Header fields (customer reference, order date, status) migrate directly. Line items require the Product reference resolved to Dolibarr Product IDs at migration time. We stage product imports before order imports so that line items resolve without orphan references. Historical orders beyond two years may be scoped to archive-only migration to reduce file size.

Purchase orders map to Dolibarr Supplier Orders linked to the vendor ThirdParty record. PO-to-receive linkage migrates to Dolibarr's receipt workflow (receptions). Line items resolve against the Product table using SKU as the dedupe key.

Proteus ERP invoices map to Dolibarr Customer Invoices. GST/HST tax data from Proteus requires mapping to Dolibarr's VAT configuration. Payment status (paid, unpaid, partial) migrates to Dolibarr payment condition fields. Historical invoices beyond two years are date-range scoped based on the customer's reporting needs. We create the corresponding third party and product records before invoice import to satisfy foreign key constraints.

Proteus ERP's GST-compliant Chart of Accounts maps to Dolibarr's accounting module accounts. We build a COA translation table during scoping that aligns Proteus account codes and segment lengths to Dolibarr's account numbering convention (typically 6-digit numeric). Revenue, expense, asset, and liability accounts map individually; any accounts without a Dolibarr equivalent are flagged for the customer's admin to configure post-migration.

Proteus ERP employee records map to Dolibarr User objects. HR data (name, role, department, pay grade) migrates as User properties. Dolibarr's HR module must be activated if the customer wants leave tracking, expense reporting, or salary history to migrate; if HR is not active, we import employees as User records only.

Proteus ERP e-commerce orders are split by sales channel in the export. We merge channel-specific order records into a single Dolibarr Order per transaction, tagging the order source in an extra-field for reporting. Line items resolve against the Product table. Inventory deduction migrates as stock movement records in Dolibarr.

POS transactions from Proteus ERP map to Dolibarr cash reconciliation records. Transaction-level sales data creates Dolibarr bank statement line entries; the linked inventory reduction migrates as Product stock movements. We coordinate with the customer to identify their primary cash drawer or bank account as the Dolibarr target.

Proteus ERP custom fields added within CRM, accounting, or inventory modules are not included in the default export. During scoping we request a full field export including custom columns and map each to a Dolibarr extra-field of the equivalent type (string, integer, select, date, checkbox). We pre-create the extra-field definitions in Dolibarr before any record import so that data lands in the correct custom property on first write.

Proteus ERP owner or user records referenced on orders, invoices, and tasks map to Dolibarr User accounts. We resolve by email match against the Dolibarr destination User table. Any Proteus owner without a matching Dolibarr User goes to a reconciliation queue for the customer to provision before record import continues.