ERP migration
Field-level mapping, validation, and rollback between PayTraq and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
PayTraq
Source
Dolibarr ERP
Destination
Compatibility
10 of 13
objects map 1:1 between PayTraq and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from PayTraq to Dolibarr is an open-source transition that trades PayTraq's flat-rate cloud model for Dolibarr's modular self-hosted architecture. PayTraq's Clients and Suppliers merge into Dolibarr's Third Parties object filtered by type code, and Products and Services merge into a single Dolibarr Products table with the type flag preserved. We sequence Chart of Accounts and opening balances first, then migrate Third Parties, followed by inventory items and open transactions. PayTraq's 5000-request daily API limit and the absence of a warehouse bulk export require us to read stock levels per product-warehouse combination individually, which extends extraction time for inventory-heavy instances. Multi-currency settings, tax codes, and price lists transfer as Dolibarr configuration records or custom fields. Prepaid expense allocation schedules and financial loan amortization timelines are not exposed via PayTraq API and are flagged for manual reconstruction by the customer's accountant post-migration.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a PayTraq object lands in Dolibarr ERP, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
PayTraq
Chart of Accounts
Dolibarr ERP
Account (Comptes / Plan de compte)
1:1PayTraq's GL account codes and types (Asset, Liability, Equity, Revenue, Expense) map directly to Dolibarr's Plan Comptable. Account groups and cost-center tagging migrate as Dolibarr Categories on the Account object. We establish the full chart of accounts in Dolibarr before any transaction migration begins so that all journal entry debit and credit lines reference valid account IDs. Account numbering convention is preserved from PayTraq's code structure.
PayTraq
Client
Dolibarr ERP
Third Party (Tier / Tiers)
1:1PayTraq Clients map to Dolibarr Third Parties with Type = Customer (code 0). We preserve client code as ref_internal, payment terms as conditions_reglement, and currency as fk_multicurrency with the associated rate stored in multicurrency_tx. Tax ID migrates to siret or siren fields for EU businesses. Any custom client properties migrate as Dolibarr extrafields on the Societe object.
PayTraq
Supplier
Dolibarr ERP
Third Party (Tier / Tiers)
1:1PayTraq Suppliers map to Dolibarr Third Parties with Type = Supplier (code 1). Supplier code, payment terms, and default currency migrate similarly to the Client mapping. Purchase terms specific to PayTraq supplier records (such as minimum order quantity or lead time) migrate as extrafields if the customer has configured these in PayTraq, otherwise they are documented for manual entry in Dolibarr.
PayTraq
Product and Service
Dolibarr ERP
Product (Article / Produit)
many:1PayTraq separates Products and Services into distinct CSV import templates. Dolibarr uses a single Products object with a type flag (0 = product, 1 = service). We merge both PayTraq streams into one Dolibarr Products table, setting type based on the source template. Unit of measure (PayTraq's unit field) maps to Dolibarr's units and weight units fields. Cost price from PayTraq becomes the pmp (weighted average cost) in Dolibarr.
PayTraq
Invoice
Dolibarr ERP
Invoice (Facture client)
1:1PayTraq Sales Invoices map to Dolibarr Factures clients. Invoice headers (date, number, client reference, due date, payment terms) migrate with the client resolved to the Dolibarr Third Party ID. Line items reference the Dolibarr Product ID (resolved from the product merge in Step 4), with quantity, unit price, VAT rate, and discount amount preserved. Multi-currency invoices store the currency as fk_multicurrency with the exchange rate in multicurrency_tx. Status (Draft, Open, Paid, Cancelled) maps directly.
PayTraq
Purchase Order
Dolibarr ERP
Purchase Order (Commande fournisseur)
1:1PayTraq Purchase Orders map to Dolibarr Commandes fournisseurs with supplier resolved to the Dolibarr Third Party ID. Line items migrate with product reference, quantity, and price. Status flags (received, partially received) migrate to Dolibarr's status field and the reception status. Any PayTraq PO lines not yet received are flagged in the migration report for reconciliation against expected deliveries.
PayTraq
Journal Entry
Dolibarr ERP
Banking / Financial Entries (Écritures comptables)
1:1PayTraq Journal Entries map to Dolibarr accounting entries (Ecritures). Each entry's debit and credit lines are mapped to the corresponding Dolibarr account ID (resolved from Step 1). We preserve the journal entry date, number, and label, and map the entry type to the corresponding Dolibarr journal code. Prepaid expense journal entries linked to the Prepaid Expenses GL account group are flagged for manual review since PayTraq does not expose the allocation schedule via API.
PayTraq
Warehouse / Inventory
Dolibarr ERP
Warehouse (Entrepôt) + Stock
1:1PayTraq warehouses map to Dolibarr Entrepôt records. On-hand stock levels per product-warehouse combination are read individually via PayTraq's product API because PayTraq lacks a bulk warehouse export. Each stock record is written to Dolibarr's llx_product_stock table with the product reference, warehouse reference, and quantity. This step runs after Products (Step 4) and Warehouses are established in Dolibarr.
PayTraq
Employee
Dolibarr ERP
Contact (Contact)
1:1PayTraq employees migrate to Dolibarr Contacts with category = Employee. We preserve first name, last name, email, phone, job title, and hire date (stored as an extrafield since Dolibarr Contacts do not have a native hire date field). Compensation fields and payroll history migrate as extrafields or are flagged for the HR team to rebuild depending on data sensitivity.
PayTraq
Fixed Asset
Dolibarr ERP
Asset (Immobilisation)
1:1PayTraq Fixed Assets migrate to Dolibarr Immobilisations with acquisition date, acquisition cost, and linked GL account from the PayTraq asset record. Depreciation method (straight-line, declining) and accumulated depreciation amount migrate to the Dolibarr asset record's fields where available; the depreciation schedule itself (monthly breakdown) is flagged for manual reconstruction because PayTraq does not expose the full schedule via API.
PayTraq
Financial Loan
Dolibarr ERP
Loan (Prêt)
1:1PayTraq financial loan records (principal, interest rate, term) migrate to Dolibarr Prêt with the loan amount, start date, and GL account references preserved. The amortization schedule (monthly principal and interest breakdown) is not exposed via PayTraq API, so we migrate the loan header record and flag the schedule for manual reconstruction in Dolibarr's loan module by the customer's accountant.
PayTraq
Tax Code
Dolibarr ERP
Tax (Taxe / TVA)
lossyPayTraq tax rates referenced on invoices migrate to Dolibarr TVA configuration. Each PayTraq tax code (rate and name) becomes a Dolibarr tax rate linked to the appropriate account in the chart of accounts. Tax agency setup in Dolibarr (mandatory for VAT reporting) is not automated and requires manual configuration by the customer's accountant post-migration.
PayTraq
Price List
Dolibarr ERP
Price List (Prix spécifiques)
lossyPayTraq price lists (multiple tiers per product) migrate to Dolibarr Prix spécifiques attached to the Product record. Each price level migrates as a separate price line with the customer or customer category filter, currency, and effective date preserved. Multi-currency price lists store the currency reference in the price line.
| PayTraq | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Chart of Accounts | Account (Comptes / Plan de compte)1:1 | Mapping required | |
| Client | Third Party (Tier / Tiers)1:1 | Fully supported | |
| Supplier | Third Party (Tier / Tiers)1:1 | Fully supported | |
| Product and Service | Product (Article / Produit)many:1 | Fully supported | |
| Invoice | Invoice (Facture client)1:1 | Fully supported | |
| Purchase Order | Purchase Order (Commande fournisseur)1:1 | Fully supported | |
| Journal Entry | Banking / Financial Entries (Écritures comptables)1:1 | Fully supported | |
| Warehouse / Inventory | Warehouse (Entrepôt) + Stock1:1 | Mapping required | |
| Employee | Contact (Contact)1:1 | Fully supported | |
| Fixed Asset | Asset (Immobilisation)1:1 | Fully supported | |
| Financial Loan | Loan (Prêt)1:1 | Fully supported | |
| Tax Code | Tax (Taxe / TVA)lossy | Fully supported | |
| Price List | Price List (Prix spécifiques)lossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
PayTraq gotchas
API boolean values must be literal true/false
Daily API limit of 5000 requests constrains migration speed
Warehouse inventory has no bulk export path
Prepaid expense allocation schedules are not directly migratable
Decimal formatting and date format strictness on API writes
Dolibarr ERP gotchas
Foreign key constraint errors on cross-distribution database restore
SQL injection vulnerabilities in version 9.0.1
Custom fields stored as JSON in extraoptions require field-by-field deserialization
Decimal precision and rounding configuration affects price fields
No native iOS/Android app forces reliance on browser
Pair-specific challenges
Migration approach
Discovery and data audit
We audit the PayTraq instance for client and supplier counts, invoice volume and status distribution (draft, open, paid), product and service count, warehouse locations and stock record count, journal entry volume, employee records, fixed asset count, and loan record count. We extract the chart of accounts and identify any accounts in the Prepaid Expenses or Loan groups that require manual reconstruction. We also review PayTraq's multi-currency configuration, active tax codes, and price list tiers. The discovery output is a written migration scope with estimated row counts per object, a timeline range, and a list of records flagged for manual reconstruction.
Chart of accounts establishment in Dolibarr
We establish the full chart of accounts in Dolibarr first, before any transaction or master data migration. Each PayTraq account code, name, type (Asset, Liability, Equity, Revenue, Expense), and group assignment maps to a corresponding Dolibarr account in the Plan Comptable. Account categories for cost-center tagging are created in Dolibarr if the customer uses them. The chart of accounts must be validated and approved by the customer's accountant before proceeding to transaction migration.
Master data migration in dependency order
We migrate master data in dependency order: Third Parties (Clients and Suppliers merged, with type filter), then Products and Services (merged into one Dolibarr Product table), then Warehouses (created before stock migration), then Employees. Third Party imports resolve the currency reference and tax ID. Product imports set the type flag (product or service) and PMP (cost). Employee imports use the Contact object with Employee category. Each phase emits a row-count reconciliation report against the PayTraq source counts.
Warehouse inventory extraction and stock migration
Because PayTraq has no bulk warehouse export, we read current stock levels by iterating through each product-warehouse combination via the PayTraq API. This step is rate-limited by PayTraq's 5000-request daily cap, so large inventory sets require multiple days of extraction across scheduled sessions. We reconstruct the stock snapshot in Dolibarr's llx_product_stock table, writing product ID, warehouse ID, and quantity for each combination. On-hand quantities at the time of extraction are preserved as static values in Dolibarr; any post-extraction changes in PayTraq are captured in a delta migration step.
Transaction migration
We migrate open and historical invoices, purchase orders, and journal entries after master data and chart of accounts are established. Invoice line items resolve the Dolibarr Product ID from the product merge in Step 3. Journal entry lines resolve the Dolibarr account ID from the chart of accounts established in Step 2. Multi-currency amounts store the currency reference and exchange rate. Status flags (paid, partially paid, overdue) migrate directly. Any journal entries linked to fixed assets or loans are flagged in the reconciliation report for the accountant to review.
Reconciliation report and manual handoff items
We deliver a full reconciliation report comparing PayTraq source counts against Dolibarr destination counts for every object. We document every record flagged for manual reconstruction (prepaid expense schedules, loan amortization timelines, depreciation schedules) with the source values needed to rebuild them. We provide a written inventory of any PayTraq automations, payment gateway configurations, or custom reports that require rebuilding in Dolibarr, as these do not migrate. We support a one-week post-migration hypercare window for data discrepancy resolution.
Platform deep dives
PayTraq
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across PayTraq and Dolibarr ERP.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
PayTraq: 1 request per second average, bursts up to 5 requests; 5000 requests per 24 hours.
Data volume sensitivity
PayTraq doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during PayTraq to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your PayTraq to Dolibarr ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave PayTraq
Other ways to arrive at Dolibarr ERP
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.