ERP migration

Migrate from ORCA Financial to Dolibarr ERP

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

ORCA Financial logo

ORCA Financial

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

100%

12 of 12

objects map 1:1 between ORCA Financial and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from ORCA Financial to Dolibarr is a manual-extraction-first migration because ORCA Financial does not publish a documented REST or bulk API. We coordinate CSV and in-app exports with the customer administrator, build transformation scripts to match Dolibarr's entity model, and import through Dolibarr's native CSV loader, REST API, or a combination depending on data volume. Dolibarr's modular architecture means you activate only the modules your migrated data uses — accounting, third-party, inventory, or project — which we confirm during scoping. We do not migrate binary attachments; we deliver a manifest of attachment filenames and record associations for post-migration re-upload. Workflows, automations, and report definitions do not migrate as code; we deliver a written inventory of any configured rules for your Dolibarr administrator to rebuild.

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

ORCA Financial logo

ORCA Financial

What's pushing teams away

  • The platform has only one verified Capterra review (3.0 stars), which is significantly below the category average and suggests limited adoption or satisfaction compared to competitors.
  • Gartner Peer Insights and G2 searches returned no results for ORCA Financial, indicating the platform has not achieved measurable enterprise traction or review volume.
  • Customers report that competitor products like Orca Security and other Orca-named products on G2 are frequently confused with ORCA Financial due to shared naming, making it difficult to distinguish the ERP product.

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

Each row shows how a ORCA Financial 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.

ORCA Financial

Chart of Accounts

maps to

Dolibarr ERP

Account (Accounting)

1:1
Mapping required

ORCA Financial stores a flat or hierarchical COA with account codes, types, and optional cost-center segments. We extract account code, account name, account type (asset, liability, equity, revenue, expense), and any custom segments. Dolibarr's accounting module uses a PCG (Plan Comptable Général) structure by default; for non-French deployments we configure a custom account plan or use the generic accounting module. Account codes with department or cost-center splits are flagged as requiring a manual post-migration account-segments configuration in Dolibarr's accounting setup.

ORCA Financial

Customers

maps to

Dolibarr ERP

Third-Party (type = Customer)

1:1
Mapping required

ORCA Financial customer records include name, billing address, payment terms, and contact information. We map these to Dolibarr Third-Party records with the Customer check-box enabled. Address fields map to Dolibarr's address, zip, town, and country fields. Payment terms from ORCA Financial map to Dolibarr's cond_reglement code. Custom fields on ORCA Financial customers migrate as extra attributes on the Dolibarr thirdparty object using Dolibarr's Module CustomFields structure. Multi-site customer records (multiple ship-to addresses) are flagged as requiring manual address-line creation in Dolibarr post-migration.

ORCA Financial

Vendors

maps to

Dolibarr ERP

Third-Party (type = Supplier)

1:1
Mapping required

ORCA Financial vendor records mirror customer records in structure: name, address, AP terms, and contact info. We map these to Dolibarr Third-Party records with the Supplier check-box enabled. Remittance addresses and multi-site vendor records are flagged as requiring manual review post-import because Dolibarr stores a single primary address per third-party with additional addresses as separate contact records.

ORCA Financial

Items / Inventory

maps to

Dolibarr ERP

Product (type = Stock)

1:1
Mapping required

ORCA Financial tracks items with SKU, description, unit cost, and warehouse location. We map SKU to ref, description to label, unit cost to cost_price, and the ORCA Financial warehouse assignment to a Dolibarr warehouse location. Dolibarr requires the Stock module to be activated for inventory tracking; we confirm this during scoping and map the ORCA Financial inventory valuation method (FIFO, weighted average) to Dolibarr's pmp (prix moyen pondéré) or FIFO setting per product.

ORCA Financial

Open Accounts Payable

maps to

Dolibarr ERP

Supplier Invoice (status = Open/Draft)

1:1
Mapping required

Open AP records include vendor name, invoice number, amount, and due date. We export these as a reconciliation-ready table delivered separately from the production import run. Dolibarr supplier invoices are created as draft records with status Open so that the AP team can verify amounts and due dates before validating. Historical paid invoices are migrated as closed records and are not re-opened in Dolibarr; we deliver them as a closed-invoice archive table for audit purposes.

ORCA Financial

Open Accounts Receivable

maps to

Dolibarr ERP

Customer Invoice (status = Open/Draft)

1:1
Mapping required

Open AR records include customer name, invoice number, amount, and due date. We export these separately for AR teams to verify post-migration. Unapplied payments and credit memos are migrated as linked records referencing the original invoice. Dolibarr invoice status is set to Draft on import so the AR team can validate before changing status to Open or Validated. Invoice PDF attachments from ORCA Financial are flagged as requiring manual re-upload because binary attachment migration is not in scope.

ORCA Financial

Warehouse / Locations

maps to

Dolibarr ERP

Warehouse

1:1
Mapping required

ORCA Financial warehouse location records define where inventory is stored. We migrate location codes, names, and addresses to Dolibarr Warehouse records. Bin-level location assignments inside warehouses are flagged as a manual post-migration step because Dolibarr's standard Stock module supports warehouse-level tracking but bin-level slot management requires either a custom field configuration or a third-party warehouse management addon.

ORCA Financial

Users

maps to

Dolibarr ERP

User

1:1
Mapping required

ORCA Financial user accounts include name, email, and role. We export a user roster and map role names to Dolibarr permission groups. Dolibarr's RBAC model uses predefined permission sets (Read, Write, Delete, Export, Print) per module; ORCA Financial role names are mapped to the closest Dolibarr permission equivalent and flagged where the mapping requires manual confirmation. Active versus inactive user status is preserved; inactive users are imported as inactive Dolibarr users.

ORCA Financial

Documents / Attachments

maps to

Dolibarr ERP

N/A

1:1
Not supported

ORCA Financial stores attachments against transactions and master records. We do not migrate binary attachments due to inconsistent storage formats and file-size constraints. We export a manifest of document filenames, the record type they were attached to (customer, vendor, invoice, item), and the record identifier in ORCA Financial. The customer's administrator uses this manifest to re-upload documents to Dolibarr post-migration through the Dolibarr document management interface.

ORCA Financial

Payment Terms

maps to

Dolibarr ERP

Payment Term (cond_reglement)

1:1
Fully supported

ORCA Financial payment terms (e.g., Net 30, 2/10 Net 30) map to Dolibarr Payment Term records with due date configuration (fixed number of days after invoice date, or a specific day of month). We extract distinct payment term values from ORCA Financial customer and vendor records, create matching Dolibarr payment term entries, and map the ORCA Financial term label to the Dolibarr cond_reglement code during third-party import.

ORCA Financial

Shipping Methods / Carriers

maps to

Dolibarr ERP

Shipping Method (mode)

1:1
Fully supported

ORCA Financial shipping method assignments on sales orders and purchase orders map to Dolibarr Shipping Method records. We extract distinct carrier and shipping method values from ORCA Financial order records, create matching Dolibarr mode entries, and map them by label during invoice and order import. Custom or one-off shipping methods are flagged for manual creation in Dolibarr.

ORCA Financial

Product Categories

maps to

Dolibarr ERP

Category (type = Product)

1:1
Fully supported

ORCA Financial item category assignments (e.g., Raw Materials, Finished Goods, Services) map to Dolibarr Category records of type Product. We extract distinct category names from ORCA Financial item records, create matching Dolibarr categories, and assign the category ID to each product during item import. Multi-category assignments per item are mapped to multiple Dolibarr CategoryProduct records.

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.

ORCA Financial logo

ORCA Financial gotchas

High

No documented public API for bulk data export

Medium

Platform name collision complicates research and vendor contact

Medium

Single-review review profile limits confidence

Low

Pricing is vendor-contact only

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 manual export coordination with ORCA Financial administrator

    ORCA Financial does not publish a REST or bulk API endpoint for automated data extraction. We cannot initiate programmatic read requests against the platform. All extraction relies on CSV or in-app exports run inside the customer's authenticated ORCA Financial session, coordinated with their administrator. This adds discovery time and creates a dependency on the customer's availability. We build extraction scripts that can be run inside the session but cannot automate the initial authentication step. Timeline estimates assume the ORCA Financial administrator can provide export access within two business days of discovery.

  • Single-review ORCA Financial profile means limited migration signal

    ORCA Financial has one verified Capterra review at 3.0 stars and no G2 or Gartner Peer Insights presence. Almost no signal exists about common migration-relevant pain points such as data portability, custom field definitions, or support responsiveness. We treat ORCA Financial as a lower-confidence source and build additional data-validation checkpoints into every migration run. Reconciliation counts are validated against the ORCA Financial export totals before each Dolibarr import phase, and any discrepancies trigger a manual review before proceeding.

  • Dolibarr module activation must precede data import

    Dolibarr's modular architecture requires specific modules to be activated before the corresponding data can be imported or displayed. The accounting module, third-party module, stock module, and hr module must each be enabled in Dolibarr's module configuration before import begins. If a module is not activated, records of that type will import but will not appear in the Dolibarr UI. We confirm the full list of required modules during scoping and include module activation in the pre-import checklist, but if the customer activates modules after import, records may require re-indexing via Dolibarr's repair tool (/install/repair.php).

  • Dolibarr attachment storage requires manual post-migration re-upload

    ORCA Financial stores attachments against transactions and master records in a format we cannot reliably parse and reconstruct in Dolibarr's document storage structure. We deliver a manifest of all attachment filenames, record types, and ORCA Financial record identifiers. The customer's administrator re-uploads documents manually through Dolibarr's document management interface or API. This is not a data loss issue; it is a workflow step that requires administrator time post-migration. Large volumes of attachments should be scoped as a separate document migration workstream.

  • Dolibarr custom fields use extra attributes not visible in standard CSV imports

    Dolibarr's custom field model uses extra attributes per object (Module CustomFields) rather than adding columns to the standard CSV import template. ORCA Financial custom fields on customers, vendors, or items must be pre-created as Dolibarr extra attributes before the CSV import runs, and the import CSV must include a column matching the extra attribute code. We document the custom field list during discovery, pre-create extra attributes in Dolibarr during the schema design phase, and extend the import CSV with the additional columns before each import phase.

Migration approach

Six steps for a successful ORCA Financial to Dolibarr ERP data migration

  1. Discovery and extraction planning

    We audit the ORCA Financial portal in coordination with the customer's administrator, documenting the chart of accounts structure, customer and vendor record counts, item and inventory record counts, open AP and AR totals, warehouse location count, and user roster. We confirm Dolibarr module requirements (accounting, third-party, stock, hr) based on the migrated data types. We build extraction scripts and export templates scoped to the ORCA Financial session and schedule export runs with the administrator. We also collect the ORCA Financial plan name and seat count to confirm edition scope.

  2. Schema design and module activation checklist

    We design the destination schema in Dolibarr. This includes activating the required Dolibarr modules, creating the account plan (customizing the default PCG or building a generic chart of accounts), creating payment term records matching ORCA Financial terms, creating warehouse records matching ORCA Financial locations, and pre-creating any extra attributes for ORCA Financial custom fields. We deliver a module activation checklist to the customer's Dolibarr administrator with instructions for enabling each module before import begins.

  3. Data extraction and transformation

    The customer's ORCA Financial administrator runs the coordinated export. We transform each export into Dolibarr-compatible CSV format, applying the account code mapping, third-party type (customer vs supplier), payment term references, warehouse references, and extra attribute columns. Open AP and AR are delivered as separate reconciliation tables with invoice number, vendor/customer name, amount, due date, and status. We validate row counts against the ORCA Financial export totals before each import phase.

  4. Sandbox import and reconciliation

    We run a full import into a Dolibarr sandbox environment using production-equivalent data volume. The customer's administrator verifies record counts in Dolibarr (third-parties in, products in, invoices in), spot-checks 20-30 random records against the ORCA Financial source, and confirms the chart of accounts mapping is correct. Any mapping corrections, extra attribute additions, or module activation gaps are resolved in the sandbox before production migration begins.

  5. Production migration in dependency order

    We run production migration in record-dependency order: payment terms and warehouses first (no dependencies), then third-parties (customers and vendors), then products and stock entries, then accounting chart of accounts entries, then open AP and AR as draft invoices, then users. Each phase emits a row-count reconciliation report before the next phase begins. The Dolibarr /install/repair.php tool is run between phases if any records appear missing from the Dolibarr UI.

  6. Cutover, validation, and attachment manifest handoff

    We freeze ORCA Financial write access during cutover, run a final delta export of any records modified during the migration window, and import the delta into Dolibarr. We deliver the attachment manifest to the administrator with filenames, record types, and ORCA Financial identifiers. We deliver a written inventory of any ORCA Financial workflows or configured rules for the Dolibarr administrator to rebuild. We support a three-day hypercare window for reconciliation issues. We do not rebuild automations or reports as code; those are documented for manual rebuild.

Platform deep dives

Context on both ends of the pair

ORCA Financial logo

ORCA Financial

Source

Strengths

  • Consolidates accounting, CRM, and inventory in a single platform for small to mid-market teams.
  • Supports distribution management including warehouse and purchasing workflows.
  • Offers a free trial and free version tier for initial evaluation.
  • Built-in billing and invoicing module.
  • Targets small and medium businesses rather than large enterprises, matching the complexity level of most migrations.

Weaknesses

  • Extremely limited public review data — only one verified Capterra review — making it difficult to assess real-world reliability.
  • No publicly documented API for automated data extraction, requiring manual exports or custom integration work.
  • Market visibility is low compared to named competitors (Odoo, MRPeasy, Acumatica), suggesting limited sales and support infrastructure.
  • Pricing is not published on the product page, requiring direct contact with the vendor to obtain a quote.
  • The ORCA Financial brand name is shared with unrelated products (Orca Security, Orca fund management, Orca neobank), creating brand confusion and search retrieval issues.
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. 3 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 ORCA Financial and Dolibarr ERP.

  • Object compatibility

    B

    3 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

    ORCA Financial: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.

  • Data volume sensitivity

    A

    ORCA Financial exposes a bulk API — large-volume migrations stream efficiently.

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most migrations land between three and five weeks for accounts under 5,000 customer records, 2,000 vendor records, and 3,000 inventory items with a single warehouse and no multi-currency setup. Migrations with multiple warehouse locations, open AP/AR in active reconciliation status, custom accounting segments, or delta-capture windows extending more than one week move to six to ten weeks because of extraction-script coordination time, manual export dependency, and AP/AR reconciliation-table preparation.

Adjacent paths

Related migrations to explore

Ready when you are

Move from ORCA Financial.
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