ERP migration
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
Source
Dolibarr ERP
Destination
Compatibility
12 of 12
objects map 1:1 between ORCA Financial and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
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 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
Dolibarr ERP
Account (Accounting)
1:1ORCA 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
Dolibarr ERP
Third-Party (type = Customer)
1:1ORCA 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
Dolibarr ERP
Third-Party (type = Supplier)
1:1ORCA 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
Dolibarr ERP
Product (type = Stock)
1:1ORCA 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
Dolibarr ERP
Supplier Invoice (status = Open/Draft)
1:1Open 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
Dolibarr ERP
Customer Invoice (status = Open/Draft)
1:1Open 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
Dolibarr ERP
Warehouse
1:1ORCA 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
Dolibarr ERP
User
1:1ORCA 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
Dolibarr ERP
N/A
1:1ORCA 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
Dolibarr ERP
Payment Term (cond_reglement)
1:1ORCA 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
Dolibarr ERP
Shipping Method (mode)
1:1ORCA 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
Dolibarr ERP
Category (type = Product)
1:1ORCA 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.
| ORCA Financial | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Chart of Accounts | Account (Accounting)1:1 | Mapping required | |
| Customers | Third-Party (type = Customer)1:1 | Mapping required | |
| Vendors | Third-Party (type = Supplier)1:1 | Mapping required | |
| Items / Inventory | Product (type = Stock)1:1 | Mapping required | |
| Open Accounts Payable | Supplier Invoice (status = Open/Draft)1:1 | Mapping required | |
| Open Accounts Receivable | Customer Invoice (status = Open/Draft)1:1 | Mapping required | |
| Warehouse / Locations | Warehouse1:1 | Mapping required | |
| Users | User1:1 | Mapping required | |
| Documents / Attachments | N/A1:1 | Not supported | |
| Payment Terms | Payment Term (cond_reglement)1:1 | Fully supported | |
| Shipping Methods / Carriers | Shipping Method (mode)1:1 | Fully supported | |
| Product Categories | Category (type = Product)1:1 | 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.
ORCA Financial gotchas
No documented public API for bulk data export
Platform name collision complicates research and vendor contact
Single-review review profile limits confidence
Pricing is vendor-contact only
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 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.
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.
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.
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.
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.
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
ORCA Financial
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 3 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 ORCA Financial and Dolibarr ERP.
Object compatibility
3 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
ORCA Financial: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.
Data volume sensitivity
ORCA Financial exposes a bulk API — large-volume migrations stream efficiently.
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 ORCA Financial to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave ORCA Financial
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.