ERP migration

Migrate from PayTraq to Dolibarr ERP

Field-level mapping, validation, and rollback between PayTraq and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.

PayTraq logo

PayTraq

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

77%

10 of 13

objects map 1:1 between PayTraq and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

PayTraq logo

PayTraq

What's pushing teams away

  • Setup is tedious with users describing the initial configuration as non-intuitive and time-consuming to complete.
  • Missing warehouse export and import functionality forces manual re-entry of inventory data when migrating off the platform.
  • No native eCommerce integrations (no OpenCart or similar) means businesses with online stores must build custom bridges or abandon the platform.
  • System performance lags reported by multiple users who describe the interface as needing speed improvements.
  • Feature gaps compared to larger ERPs mean growing businesses eventually outscale PayTraq and migrate to NetSuite, QuickBooks Online, or Sage Intacct.

Choosing

Dolibarr ERP logo

Dolibarr ERP

What's pulling them in

  • Free open-source core with no per-user license fee makes it the lowest-cost entry point for small teams needing ERP and CRM in one package.
  • Self-hosted deployment gives full data ownership and eliminates vendor lock-in, especially attractive to businesses with compliance requirements.
  • Modular architecture means teams enable only the features they use, keeping the interface uncluttered and reducing learning curve.
  • Fast installation with no technical knowledge required — one reviewer set up multiple businesses in minutes using their own hosting.
  • Active community forum and marketplace of third-party add-ons provide support and extension options without mandatory subscription costs.

Object mapping

How PayTraq objects map to Dolibarr ERP

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

maps to

Dolibarr ERP

Account (Comptes / Plan de compte)

1:1
Mapping required

PayTraq'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

maps to

Dolibarr ERP

Third Party (Tier / Tiers)

1:1
Fully supported

PayTraq 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

maps to

Dolibarr ERP

Third Party (Tier / Tiers)

1:1
Fully supported

PayTraq 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

maps to

Dolibarr ERP

Product (Article / Produit)

many:1
Fully supported

PayTraq 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

maps to

Dolibarr ERP

Invoice (Facture client)

1:1
Fully supported

PayTraq 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

maps to

Dolibarr ERP

Purchase Order (Commande fournisseur)

1:1
Fully supported

PayTraq 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

maps to

Dolibarr ERP

Banking / Financial Entries (Écritures comptables)

1:1
Fully supported

PayTraq 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

maps to

Dolibarr ERP

Warehouse (Entrepôt) + Stock

1:1
Mapping required

PayTraq 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

maps to

Dolibarr ERP

Contact (Contact)

1:1
Fully supported

PayTraq 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

maps to

Dolibarr ERP

Asset (Immobilisation)

1:1
Fully supported

PayTraq 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

maps to

Dolibarr ERP

Loan (Prêt)

1:1
Fully supported

PayTraq 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

maps to

Dolibarr ERP

Tax (Taxe / TVA)

lossy
Fully supported

PayTraq 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

maps to

Dolibarr ERP

Price List (Prix spécifiques)

lossy
Fully supported

PayTraq 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.

Gotchas + challenges

What specifically takes care here

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 logo

PayTraq gotchas

Medium

API boolean values must be literal true/false

Medium

Daily API limit of 5000 requests constrains migration speed

High

Warehouse inventory has no bulk export path

High

Prepaid expense allocation schedules are not directly migratable

Low

Decimal formatting and date format strictness on API writes

Dolibarr ERP logo

Dolibarr ERP gotchas

High

Foreign key constraint errors on cross-distribution database restore

High

SQL injection vulnerabilities in version 9.0.1

Medium

Custom fields stored as JSON in extraoptions require field-by-field deserialization

Medium

Decimal precision and rounding configuration affects price fields

Low

No native iOS/Android app forces reliance on browser

Pair-specific challenges

  • PayTraq warehouse items have no bulk export path

    PayTraq provides no bulk export or import mechanism for warehouse inventory items. We work around this by reading current stock levels via the PayTraq API for each product-warehouse combination individually, reconstructing the inventory snapshot from those individual reads. For instances with hundreds of products across multiple warehouses, this step runs across multiple API sessions due to PayTraq's 5000-request daily cap and 1-request-per-second rate limit, extending extraction time significantly compared to a flat CSV export.

  • PayTraq API boolean values require literal true/false strings

    PayTraq's API rejects boolean fields passed as 0 or 1, requiring explicit true or false strings. Our extraction pipeline transforms all boolean fields during read operations to match PayTraq's constraint. If the destination Dolibarr instance receives data from another source before migration completes, its own API write operations to PayTraq must also observe this format constraint, otherwise silent 400 errors occur on import.

  • Prepaid expense allocation schedules are not API-accessible

    PayTraq stores prepaid expense allocation schedules on purchase invoices linked to GL accounts in the Prepaid Expenses group. These schedules are not exposed via API or CSV export. We migrate the invoice header and GL postings but flag every prepaid expense record for manual reconstruction in Dolibarr. The customer's accountant must rebuild the unallocated amount and monthly allocation timeline in Dolibarr's corresponding GL entries post-migration.

  • Dolibarr database migration errors after version upgrades

    Dolibarr's upgrade process runs database migration scripts between versions, and these scripts have been reported to fail on certain hosting environments (particularly MySQL/MariaDB with strict mode or specific character set configurations). The GitHub issue tracker shows migration errors related to index key length limits (max 767 bytes for unique indexes) and character set mismatches. We run Dolibarr upgrades in a staging environment before applying them to production, and we document the PHP version, database version, and character set configuration required for a clean upgrade path.

  • Dolibarr custom fields require module activation before use

    Dolibarr custom fields (extrafields) are attached to core objects only after the ExtraFields feature is enabled in Dolibarr's module configuration. Migrations that expect custom field targets to be ready at import time will fail if the module is not active. We activate the ExtraFields module and define all target extrafields in Dolibarr before beginning the data import phase, and we validate that the extrafield definitions match the incoming PayTraq field types (text, integer, float, date, select, etc.).

Migration approach

Six steps for a successful PayTraq to Dolibarr ERP data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

PayTraq logo

PayTraq

Source

Strengths

  • All-in-one ERP combining accounting, inventory, sales, and purchasing in a single cloud platform.
  • Transparent flat-rate pricing with no per-transaction fees or feature gating across tiers.
  • Double-entry accounting engine with prepaid expense allocation and multi-currency support.
  • Real-time multi-user collaboration with bank-level security and automatic backups.
  • CSV bulk import templates for Clients, Suppliers, Employees, Products, and Services.

Weaknesses

  • API rate limit of 1 request per second (5000 per 24 hours) constrains bulk data extraction speed.
  • No published bulk/batch API endpoint — data extraction relies on individual API calls and CSV downloads.
  • Warehouse inventory items lack a native bulk export/import workflow, complicating outbound migration.
  • No eCommerce platform integrations require third-party bridges or manual data entry for online sales.
  • Limited advanced reporting compared to enterprise ERP alternatives, driving churn for scaling businesses.
Dolibarr ERP logo

Dolibarr ERP

Destination

Strengths

  • Free core software with AGPL license and no per-user mandatory fee for self-hosted deployments.
  • Modular architecture lets teams activate only needed features, keeping the interface focused and the database lean.
  • Self-hosted option provides full data sovereignty and avoids recurring SaaS subscription costs.
  • Built-in CSV/Excel import and export wizard with saved profiles simplifies recurring data operations.
  • Low-code Module Builder allows functional extensions without writing PHP code.

Weaknesses

  • No native documented REST API for programmatic bulk operations — all migrations depend on the import/export wizard or direct database access.
  • Reporting and analytics are weak without paid add-ons, and built-in charts are limited compared to modern SaaS platforms.
  • UI design is described as dated by multiple reviewers, with infrequent visual updates to the default theme.
  • Community-only support for self-hosted deployments means no SLA or guaranteed response time for issues.
  • Security vulnerabilities (CVE-2024-5314, CVE-2024-5315) in version 9.0.1 with no immediate patch reported.

Complexity grading

How hard is this migration?

Standard ERP migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across PayTraq and Dolibarr ERP.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    PayTraq: 1 request per second average, bursts up to 5 requests; 5000 requests per 24 hours.

  • Data volume sensitivity

    B

    PayTraq doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your PayTraq to Dolibarr ERP migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about PayTraq to Dolibarr ERP data migrations

Answers to the questions buyers ask most during PayTraq to Dolibarr ERP migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Straightforward migrations with under 5,000 Third Parties, 2,000 invoices, and single-warehouse inventory land in three to five weeks. Migrations with multi-warehouse inventory, large journal entry histories, or active fixed asset and loan records extend to eight to twelve weeks because PayTraq's 5000-request daily API cap requires multiple extraction sessions for inventory-heavy instances and because prepaid expense, depreciation, and loan schedules require manual reconstruction by the customer's accountant.

Adjacent paths

Related migrations to explore

Ready when you are

Move from PayTraq.
Land in Dolibarr ERP, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day