ERP migration

Migrate from Integra ERP to Dolibarr ERP

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

Integra ERP logo

Integra ERP

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

83%

10 of 12

objects map 1:1 between Integra ERP and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Migrating from Integra ERP to Dolibarr requires a non-API extraction pipeline because Integra ERP publishes no public REST or SOAP endpoint. We extract data through direct database queries against on-premise instances, parse proprietary storage formats, and load into Dolibarr through its CSV-based import module in strict dependency order: Chart of Accounts first, then Customers and Vendors, then Items, then open AP/AR balances, then inventory ledgers, then historical Sales Orders. Integra ERP organizes data by branch or warehouse location; we aggregate stock values by item and map them to Dolibarr warehouse or location codes. Open payable and receivable balances migrate as opening-balance records rather than individual invoices. We preserve journal-entry relationships so the destination trial balance reconciles, and we flag that embedded documents, scanned files, and proprietary attachments cannot be extracted through any documented mechanism. Workflows, automations, and report definitions do not migrate; we deliver a written inventory for the customer's admin to rebuild in Dolibarr's modular configuration.

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

Integra ERP logo

Integra ERP

What's pushing teams away

  • Perpetual license pricing model is rigid and does not accommodate distinct operational requirements, forcing customers with evolving workflows toward more flexible SaaS alternatives.
  • No public API is documented or available, preventing customers from integrating Integra ERP with modern BI, e-commerce, or automation tools, driving migrations to API-first platforms.
  • On-premise deployment requires dedicated Windows infrastructure and IT staff to maintain, creating hidden operational overhead that erodes the cost advantage for growing businesses.
  • Limited transparency in pricing tiers beyond the base ₹500 per-user cost, with no clear feature gating documentation, causing budget surprises during implementation.

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 Integra ERP objects map to Dolibarr ERP

Each row shows how a Integra ERP 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.

Integra ERP

Chart of Accounts

maps to

Dolibarr ERP

Accounting (plan comptable)

lossy
Mapping required

Integra ERP stores account codes and account-type classifications across multiple tables. We extract the full account hierarchy, map each source account code to a Dolibarr accounting account number using a customer-provided account-mapping spreadsheet, and preserve account-type (asset, liability, income, expense). Dolibarr supports PCG (French), SYSCOHADA, and generic international accounting plans; we configure the target plan type during schema design and validate the trial balance after load to confirm debits equal credits.

Integra ERP

Customers

maps to

Dolibarr ERP

Third Parties (type: Customer)

1:1
Fully supported

Integra ERP Customer records (contact details, billing address, GST registration, credit terms) map directly to Dolibarr Third Party records with the Customer type flag set. We preserve the open AR balance as an opening-balance receivable entry in Dolibarr's accounting module. Customer-specific pricing rules in Integra migrate as price-supervisor rules attached to the Third Party in Dolibarr.

Integra ERP

Vendors

maps to

Dolibarr ERP

Third Parties (type: Supplier)

1:1
Fully supported

Vendor master data including payment terms, GST/VAT registration, and address records map to Dolibarr Third Party records with the Supplier type flag. Vendor-specific item pricing (where present in Integra's vendor-price tables) migrates as supplier-price lists in Dolibarr's Product module, linked to the relevant Supplier Third Party.

Integra ERP

Items (Products)

maps to

Dolibarr ERP

Products / Services

1:1
Mapping required

Integra Items carry classification codes, BOM structures (for manufacturers), and branch-specific stock values. We flatten BOM hierarchies into individual product-component relationships in Dolibarr, map Integra's product types (traded goods, raw materials, finished goods) to Dolibarr's product classification, and preserve the original SKU as the ref field. Branch-level stock values aggregate by item and map to Dolibarr warehouse locations.

Integra ERP

Open AP / AR

maps to

Dolibarr ERP

Accountancy: Outstanding Receivables and Payables

1:1
Mapping required

Outstanding payable and receivable balances in Integra ERP must migrate as opening-balance records in Dolibarr rather than individual invoice entries, because Dolibarr's import module handles historical invoices through a separate accounting-import profile. We extract the net outstanding amount per vendor and customer, create corresponding accounting entries with open = 1 flag, and set the due date to migration date for aging-report accuracy.

Integra ERP

Inventory Ledgers

maps to

Dolibarr ERP

Stock (Warehouse module)

1:1
Mapping required

Integra ERP stores stock quantities by branch or warehouse location. We aggregate stock values by item across all branches, resolve the destination warehouse or location code in Dolibarr (using a customer-provided branch-to-warehouse mapping), and preserve serial and batch tracking fields where present in the source. Stock-reconciliation counts are loaded as inventory movements rather than direct stock updates to maintain an audit trail.

Integra ERP

Sales Orders (Open and Historical)

maps to

Dolibarr ERP

Orders

1:1
Fully supported

Integra ERP stores Sales Order headers and line items across linked tables. We extract header-level fields (order number, date, customer reference, order status) and line-level fields (item, quantity, unit price, tax code) as a flattened CSV, then load through Dolibarr's Orders import profile. Order-status values map to Dolibarr workflow states using a status-mapping table agreed upon during scoping. Orders referencing voided customers are flagged and held for customer-admin resolution.

Integra ERP

Employees

maps to

Dolibarr ERP

HR / Users

1:1
Fully supported

Integra ERP's employee management module exports employee master records including department assignment and basic compensation fields. We map these to Dolibarr User records (for system access) and HR module entries (for employee directory). Salary and compensation data migrates as informational records only; payroll processing remains outside standard Dolibarr scope unless the HR module with payroll extension is activated.

Integra ERP

Historical Transactions (Purchase Receipts, Journal Entries)

maps to

Dolibarr ERP

Accountancy: Various / Banking

1:1
Fully supported

Full transaction history in Integra ERP spans multiple linked tables (header, line, tax, payment). We extract header-and-line pairs in dependency order, reconstruct the accounting double-entry using the account-mapping spreadsheet, and load through Dolibarr's accounting-import profile. Complex journal entries referencing multiple line items and tax codes require custom transformation scripts. We flag any transactions with missing account references for manual resolution before load.

Integra ERP

Custom Fields

maps to

Dolibarr ERP

ExtraFields

lossy
Fully supported

Integra ERP instances may carry organization-specific custom fields on Customer, Vendor, Item, or Transaction records. We audit the source schema for non-standard columns, map each to a Dolibarr ExtraFields entry (activated via the CustomFields module or native extrafields), and preserve data types (date, integer, varchar, select) during transformation. Dolibarr's ExtraFields are stored per object and can be managed through the setup interface post-migration.

Integra ERP

Documents (Attachments)

maps to

Dolibarr ERP

Not supported

1:1
Fully supported

Integra ERP stores attachments, scanned documents, and PDFs inside the proprietary on-premise file system without a documented export mechanism. We extract any linked file paths from the database but cannot guarantee file integrity or accessibility. Dolibarr's document management module accepts uploaded files post-migration; the customer should plan a parallel document-archival project if attachment preservation is business-critical.

Integra ERP

Dealer / Branch Management

maps to

Dolibarr ERP

Multi-company or Project

1:1
Fully supported

Integra ERP includes multi-branch dealer management for trading and distribution companies. We extract branch-level data (branch-specific customers, branch-specific inventory, branch-specific sales orders) and map to Dolibarr Projects (for reporting segregation) or multi-company configuration if Dolibarr's Multi-company module is activated. The customer chooses the scoping approach during discovery.

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.

Integra ERP logo

Integra ERP gotchas

High

No public API for automated export

High

On-premise database format is proprietary

Medium

No documented data portability feature

Medium

Perpetual license does not include migration support

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

  • No public API forces direct database extraction from Integra ERP

    Integra ERP does not publish a public REST or SOAP API according to available documentation. We must extract data through direct SQL queries against on-premise instances or through scheduled flat-file report exports. This requires read-only database credentials and pre-export parsing of proprietary Windows-based storage formats before any data can enter the ETL pipeline. On-premise instances also require VPN or direct network access for the migration team, adding pre-migration scoping time. If the customer cannot provide database access, migration scope reduces to flat-file reports only, which excludes historical transactions and open AP/AR detail.

  • Dolibarr's date-format import validation is strict

    Dolibarr's import module enforces a strict date-format rule: ^[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9](-[0-9][0-9]:[0-9][0-9]:[0-9][0-9])?$ which requires YYYY-MM-DD for date fields and YYYY-MM-DD HH:MM:SS for datetime fields. A reported GitHub issue (#24700) confirms that timestamps like 2015-01-01 without the trailing seconds component can be rejected even in valid date contexts. We run all date fields through a normalization transform before Dolibarr import and validate a sample batch against the target Dolibarr instance before committing the full load.

  • Integra branch-level inventory must aggregate to Dolibarr warehouse model

    Integra ERP stores inventory by branch or warehouse location with branch-specific stock quantities tracked independently. Dolibarr's stock module tracks inventory by warehouse or location, but its import profile expects a single stock quantity per product-warehouse pair. We aggregate branch-level stock values by item (using a customer-provided branch-to-warehouse mapping), flatten any branch-specific pricing tiers into Dolibarr's price-supervisor rules, and flag any items with negative or inconsistent branch-level quantities for reconciliation before load.

  • Dolibarr import module is table-by-table with predefined profiles only

    Dolibarr's built-in import wizard accepts CSV flat files and maps them one table at a time using predefined import profiles (Third Parties, Products, Orders, Invoices, etc.). There is no native bulk-import mechanism for custom objects or arbitrary SQL inserts. We respect this constraint by formatting each extracted CSV to match Dolibarr's expected column headers and field order per import profile, running each table's load independently, and managing foreign-key references (Customer ID, Product ID, Account ID) through a lookup-resolution step between loads.

  • Dolibarr post-update database migration can break import paths

    Dolibarr's community forum and GitHub issue tracker document cases where database migration scripts running during version updates alter table structures in ways that invalidate previously working import profiles. We pin the target Dolibarr version during migration scope, avoid running automatic updates during the migration window, and validate import profiles against the specific Dolibarr version before committing records. If the customer applies a Dolibarr update post-migration, we recommend validating the import profiles again before any subsequent data loads.

Migration approach

Six steps for a successful Integra ERP to Dolibarr ERP data migration

  1. Source access and extraction scoping

    We coordinate with the customer's IT team to obtain read-only database credentials (or report-writer access for flat-file-only extraction), establish VPN or direct network connectivity, and map the Integra ERP schema against the active modules in use. We identify every table referenced by each active module (finance, inventory, sales, HR), document foreign-key relationships, and flag any proprietary encoding or encrypted fields that require pre-parsing. If database access is not available, we scope flat-file report exports and document which objects cannot be fully extracted.

  2. Destination schema design and module activation

    We configure Dolibarr based on the customer's active Integra ERP modules, activating only the corresponding Dolibarr modules (Third Parties, Products, Stock, Orders, Invoices, Accounting, HR, Projects). We design the account-mapping spreadsheet in collaboration with the customer's accountant, configure the target accounting plan (PCG, SYSCOHADA, or generic), set up warehouse locations matching the customer's branch structure, and define the Third Party type flags (Customer, Supplier, or both) for each migrated party. ExtraFields are created for any source custom fields identified during schema audit.

  3. Dependency-ordered extraction in ETL pipeline

    We build a custom extraction script that queries Integra ERP in strict dependency order: Chart of Accounts first (no dependencies), then Third Parties (Customers and Vendors), then Products/Items (may reference vendor codes), then open AP/AR balances (reference Third Parties and Accounts), then inventory ledgers (reference Products and warehouse codes), then Sales Orders (reference Third Parties, Products, and Accounts), then historical transactions (reference all prior entities). Each extraction phase outputs a normalized CSV with consistent date formatting (YYYY-MM-DD HH:MM:SS) and type-safe field values validated against Dolibarr's import profile.

  4. Trial-load and reconciliation in staging environment

    We run a trial migration into a staging Dolibarr instance using a representative subset of data (typically 10-20% of total record volume). The customer's accountant and operations lead review reconciled record counts (Accounts in, Third Parties in, Products in, Orders in), spot-check 25-50 random records against the Integra ERP source, and validate that the Dolibarr accounting trial balance nets to zero after opening-balance entries are loaded. Any mapping corrections, date-format issues, or account-reference gaps are resolved in this phase before production migration begins.

  5. Production migration in dependency order with delta capture

    We execute the full production migration into the live Dolibarr instance in the same dependency sequence used in staging. Each phase emits a row-count reconciliation report that we compare against the source record counts before the next phase begins. During the migration window, any records modified in Integra ERP after extraction are captured as a delta load. We do not freeze Integra ERP writes during migration; instead, we schedule a final delta pass at cutover and validate that no records were missed before declaring the migration complete.

  6. Cutover, validation, and automation inventory handoff

    We freeze Integra ERP writes at cutover, run the final delta migration, and validate that Dolibarr is self-consistent (all Third Parties have valid types, all Orders reference valid Third Parties, inventory stock matches expected aggregate). We deliver the full migration report including record counts per object, any records skipped with reason, and the account-mapping spreadsheet used. We also deliver a written inventory of Integra ERP automations (workflow triggers, scheduled tasks, alert rules) and report definitions requiring rebuild in Dolibarr's configuration interface. We support a 72-hour hypercare window for reconciliation issues raised by the customer's team.

Platform deep dives

Context on both ends of the pair

Integra ERP logo

Integra ERP

Source

Strengths

  • One-time perpetual license model with no recurring SaaS fees, reducing long-term subscription cost.
  • Integrated modules covering finance, inventory, supply chain, and CRM without requiring third-party integrations.
  • Purpose-built for Indian SME retail, trading, and manufacturing with GST-compliant accounting.
  • Both cloud-hosted and on-premise deployment options across Windows desktop and mobile.
  • Android mobile apps for field distribution management and executive tracking.

Weaknesses

  • No public API documented—data export relies on database access or flat-file reports with no programmatic interface.
  • Perpetual license model is inflexible for businesses with changing scope or seasonal headcount fluctuations.
  • On-premise deployments demand dedicated Windows infrastructure and in-house IT maintenance capacity.
  • Limited online review presence makes independent quality assessment difficult before purchase.
  • No documented bulk-export or data portability feature, complicating exit planning.
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. 1 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 Integra ERP and Dolibarr ERP.

  • Object compatibility

    B

    1 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

    Integra ERP: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Integra ERP 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 Integra ERP to Dolibarr ERP data migrations

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

Can't find your answer?

Walk through your Integra ERP to Dolibarr ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Migrations under 10,000 customers, 5,000 items, and a single branch without BOM structures land between three and five weeks. Migrations with multi-branch inventory aggregation, BOM hierarchies, historical transaction tables with header-and-line relationships, or multiple open AP/AR ledger entries move to six to ten weeks because of schema mapping, BOM flattening, and trial-balance reconciliation. Timeline also depends on how quickly database access is provisioned and whether a staging environment is available for trial validation.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Integra ERP.
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