ERP migration
Field-level mapping, validation, and rollback between COINCAP ERP and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
COINCAP ERP
Source
Dolibarr ERP
Destination
Compatibility
12 of 14
objects map 1:1 between COINCAP ERP and Dolibarr ERP.
Complexity
BStandard
Timeline
5-8 weeks
Overview
Migrating from COINCAP ERP to Dolibarr is a structural migration from a vendor-assisted, on-premise Indian ERP to a self-hosted or cloud-deployed open-source ERP with a documented REST API and modular architecture. COINCAP ERP does not expose a public REST API or bulk export interface, so all source data extraction requires direct coordination with the COINCAP technical team to define export formats and conduct a schema audit. We map the COINCAP chart of accounts with GST/SGST/CGST tax codes to Dolibarr's accounting module, split COINCAP's combined party master into Dolibarr's separate Third Party records for customers and suppliers, and resolve multi-level BOM hierarchies against Dolibarr's product and stock module. Open AP and AR ledgers migrate as Dolibarr bank accounts and direct accounting entries. Documents and attachments stored in COINCAP cannot be retrieved via any documented API and are flagged as a separate workstream. Workflows, custom reports, and module-specific automation in COINCAP do not migrate as code; we deliver a written inventory for the customer's admin to rebuild in Dolibarr.
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 COINCAP 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.
COINCAP ERP
Chart of Accounts
Dolibarr ERP
Account (Accounting)
1:1COINCAP ERP finance module stores the full account hierarchy—asset, liability, income, and expense accounts—along with Indian GST/SGST/CGST/IGST tax codes embedded in each account record. We extract the complete account structure, resolve the GST tax rate associated with each account, and map it to a Dolibarr Account record with its account_type category and the relevant VAT declaration configuration set in Dolibarr's accounting module. Indian accounting conventions (dual-entry, GST-ledger alignment) are preserved; the destination chart of accounts is validated by the customer's finance team before import.
COINCAP ERP
Party Master (Customer Records)
Dolibarr ERP
Third Party (Customer)
1:1COINCAP ERP maintains a combined party master for customers and vendors within its trading module. We extract customer records with contact details, GST registration number (GSTIN), payment terms, and address blocks. Each COINCAP customer record maps to a Dolibarr Third Party record with the IsACustomer flag set, the GSTIN stored in the dolibarr_extrafields tax_number field, and address blocks mapped to Dolibarr's address model. Multiple address records in COINCAP (billing, shipping) split into separate Dolibarr address records linked to the same Third Party.
COINCAP ERP
Party Master (Vendor Records)
Dolibarr ERP
Third Party (Supplier)
1:1COINCAP vendor records extract from the same combined party master as customers, distinguished by a party_type flag. Vendor records map to Dolibarr Third Party with IsASupplier flag set. GSTIN, PAN number, and payment terms migrate as extra fields. COINCAP vendor-specific fields (TDS deduction category, MSME status) map to Dolibarr's supplierinfo extended fields.
COINCAP ERP
Item Master (Finished Goods, Raw Materials, Semi-Finished)
Dolibarr ERP
Product
1:1COINCAP inventory module stores item masters with item codes, descriptions, UOM (unit of measure), pricing tiers, and item category (raw material, semi-finished, finished goods). We extract the full item master and map each record to a Dolibarr Product. The item category maps to Dolibarr's ptype field (product, service). UOM conversions (pieces to boxes, kg to tonnes) migrate as Dolibarr unit-of-measure definitions.
COINCAP ERP
Item Master (Stock Levels)
Dolibarr ERP
Stock (Warehouse Stock)
1:1COINCAP inventory balances per item per warehouse extract as a separate dataset. Each balance maps to a Dolibarr Stock record linked to the corresponding Product and Warehouse. Multi-warehouse deployments in COINCAP map to multiple Dolibarr Warehouse records created during schema setup. Stock value in COINCAP's base currency aligns with Dolibarr's PMP (weighted average price) calculation.
COINCAP ERP
Bill of Materials (BOM)
Dolibarr ERP
BOM (Manufacturing Module)
lossyCOINCAP production module stores multi-level BOM hierarchies for manufactured items. We extract the BOM structure (parent item, child components, quantities per BOM unit, operation sequence) and map it to Dolibarr's BOM records under the MRP module. Multi-level BOMs require recursive resolution: we flatten the hierarchy during extraction and reconstruct it as nested BOM objects in Dolibarr, with the top-level BOM set as the manufactured product and sub-assemblies as intermediate BOMs. The MRP module in Dolibarr is activated during module setup before BOM import begins.
COINCAP ERP
Open AR Ledger (Outstanding Receivables)
Dolibarr ERP
Invoice (Customer) + Direct Accounting Entry
1:1COINCAP outstanding receivables extract as open invoice records with party reference, invoice number, invoice date, due date, outstanding amount, and currency. Each open receivable maps to a Dolibarr Facture (invoice) in the Non-Billed status with the open amount preserved. A corresponding accounting entry (Écriture Comptable) is created in Dolibarr's accounting module to reflect the open receivable on the customer's account. Aged trial balance data from COINCAP reconciles against Dolibarr's accounting balance report after import.
COINCAP ERP
Open AP Ledger (Outstanding Payables)
Dolibarr ERP
Invoice (Supplier) + Direct Accounting Entry
1:1COINCAP outstanding payables extract as open supplier invoice records with vendor reference, invoice number, invoice date, due date, outstanding amount, and GST component values. Each open payable maps to a Dolibarr Facture (supplier invoice) with open amount preserved and a corresponding accounting entry in the accounts payable ledger. TDS deductions recorded in COINCAP map to withholding tax configuration in Dolibarr's accounting module.
COINCAP ERP
Sales Transactions (Vouchers)
Dolibarr ERP
Invoice (Customer) + Order
1:1COINCAP vouchers—sales invoices, delivery challans, sales returns—extract as transaction records with line items, tax amounts, and party references. Each COINCAP sales voucher maps to a Dolibarr Facture for invoiced records and a Dolibarr Commande for order records. Line items resolve to Dolibarr Product references created during the item master import. GST tax breakdown (CGST, SGST, or IGST) maps to the corresponding VAT collect account in Dolibarr's accounting setup.
COINCAP ERP
Purchase Transactions (Vouchers)
Dolibarr ERP
Invoice (Supplier) + Order
1:1COINCAP purchase vouchers—purchase invoices, GRN records, purchase returns—extract with vendor reference, line items, and tax components. Each purchase voucher maps to a Dolibarr Facture (supplier invoice) or Commande (supplier order). The COINCAP GST input tax credit is mapped to the relevant VAT collect account in Dolibarr. Purchase returns map as credit notes (Avoir) in Dolibarr.
COINCAP ERP
Journal Entries (Vouchers)
Dolibarr ERP
Accounting Entries (Écritures Comptables)
1:1COINCAP journal vouchers—contra entries, adjustments, depreciation postings—extract as journal lines with debit and credit amounts, account references, and narration. Each journal voucher maps to a Dolibarr Écriture Comptable record under the appropriate Journal (Général, Achats, or Ventes). We preserve the original COINCAP voucher number and date as metadata fields. Locked or reconciled entries in COINCAP are flagged as such and migrated with their reconciliation status for the customer's finance team to validate.
COINCAP ERP
Users and Roles
Dolibarr ERP
Users and Permissions
1:1COINCAP user accounts with role-based module access map to Dolibarr User records. The COINCAP role (module-level access gates) maps to a Dolibarr permission set per module—for example, read/write on the accounting module, inventory access, purchasing approval. We extract user login names, display names, email addresses, and role assignments. Passwords and session tokens cannot be exported from COINCAP and are not migrated; users receive an onboarding email from Dolibarr to set new credentials.
COINCAP ERP
Custom Fields (Industry-Vertical Extensions)
Dolibarr ERP
Extra Fields
lossyCOINCAP deployments across 11 industry verticals frequently add custom fields to standard objects—customer-specific cost centres, item-specific HS codes, voucher-level project codes. During the schema audit with COINCAP technical staff, we identify all active custom field definitions, their COINCAP data types, and the objects they attach to. Each custom field maps to a Dolibarr extrafields definition (text, select, date, int, float) created on the corresponding Dolibarr object before data import. Custom fields with picklist values in COINCAP map to Dolibarr select extrafields with the same value list. Industry-vertical custom fields require per-deployment scoping; there is no standard mapping.
COINCAP ERP
Documents and Attachments
Dolibarr ERP
None
1:1COINCAP ERP stores scanned documents and attachments linked to transactions and master records. There is no documented public API endpoint for bulk attachment export. We identify all COINCAP records with linked documents during discovery and present three options: manual re-upload post-migration, a separate document-migration workstream with COINCAP vendor assistance (requiring custom export routines), or accepting that attachments will not migrate. Transaction PDFs and GST invoices may be available as printed output files rather than stored documents; the COINCAP team confirms during the vendor coordination phase.
| COINCAP ERP | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Chart of Accounts | Account (Accounting)1:1 | Mapping required | |
| Party Master (Customer Records) | Third Party (Customer)1:1 | Fully supported | |
| Party Master (Vendor Records) | Third Party (Supplier)1:1 | Fully supported | |
| Item Master (Finished Goods, Raw Materials, Semi-Finished) | Product1:1 | Fully supported | |
| Item Master (Stock Levels) | Stock (Warehouse Stock)1:1 | Fully supported | |
| Bill of Materials (BOM) | BOM (Manufacturing Module)lossy | Fully supported | |
| Open AR Ledger (Outstanding Receivables) | Invoice (Customer) + Direct Accounting Entry1:1 | Fully supported | |
| Open AP Ledger (Outstanding Payables) | Invoice (Supplier) + Direct Accounting Entry1:1 | Fully supported | |
| Sales Transactions (Vouchers) | Invoice (Customer) + Order1:1 | Fully supported | |
| Purchase Transactions (Vouchers) | Invoice (Supplier) + Order1:1 | Fully supported | |
| Journal Entries (Vouchers) | Accounting Entries (Écritures Comptables)1:1 | Fully supported | |
| Users and Roles | Users and Permissions1:1 | Mapping required | |
| Custom Fields (Industry-Vertical Extensions) | Extra Fieldslossy | Fully supported | |
| Documents and Attachments | None1:1 | Not 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.
COINCAP ERP gotchas
No public REST API for self-service data export
Vendor-assisted export required due to opaque schema
On-premise deployments require infrastructure readiness at destination
No bulk attachment or document export capability
Custom fields per vertical require scoping per deployment
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
Vendor coordination and export format agreement
We initiate a vendor coordination phase with the customer's COINCAP account manager to define the data export format. Because COINCAP has no public API, this typically involves direct database queries or custom export routines built by the COINCAP technical team. We request a sample export in CSV or SQL dump format covering the primary objects (chart of accounts, party master, item master, open ledgers) and share it with our team for schema validation. This phase typically takes two to four weeks and gates all subsequent work; the migration timeline is anchored to the export agreement date.
Schema audit and field-mapping matrix build
Using the sample COINCAP export, we conduct a schema audit in collaboration with COINCAP technical staff. We map every COINCAP column to a standard ERP object category, identify custom fields (industry-vertical extensions) with no base-product equivalent, and classify the mapping type for each: 1:1, 1:N split, N:1 merge, or configuration. Custom field definitions are documented as Dolibarr extrafields specifications. The field-mapping matrix is reviewed and signed off by the customer's admin before any data transformation begins.
Dolibarr module setup and accounting configuration
Before any data loads, we configure Dolibarr's active modules based on the scope agreed during discovery. The accounting module is activated with the Indian GST tax regime: CGST/SGST for intrastate, IGST for interstate, and the relevant rate slabs. We create the chart of accounts hierarchy, bank accounts for open AP/AR migration, and warehouse records for inventory stock. The MRP module is activated if multi-level BOM import is in scope. Module activation is validated in a clean Dolibarr install before migration data is introduced.
Data cleaning and transformation
We transform raw COINCAP export data into Dolibarr-compatible CSV and SQL formats according to the signed field-mapping matrix. This includes splitting the combined COINCAP party master into separate customer and supplier Third Parties, resolving COINCAP item codes against the Dolibarr Product records created during import, splitting multi-address blocks into separate Dolibarr address records, and flattening multi-level BOMs into nested Dolibarr BOM structures. Duplicate records, invalid GSTINs, and missing required fields are flagged in a pre-import data quality report for the customer's admin to resolve.
Test migration into staging Dolibarr environment
We run a full migration into a staging Dolibarr instance using production-like data volume. The customer reconciles record counts (accounts, third parties, products, open invoices, transactions) against the COINCAP source, spot-checks 25-50 random records for field-level accuracy, and validates that GST tax amounts on imported invoices match the COINCAP source. BOM structures are verified against COINCAP's production module output. Any mapping corrections are documented, the transformation logic is updated, and the test migration is re-run until reconciliation passes.
Production migration in dependency order
We run production migration in record-dependency order: chart of accounts first (accounting entries depend on account IDs), then third parties (invoices depend on third-party IDs), then products and warehouses (stock depends on product IDs), then BOM structures, then open AP/AR ledgers, then historical transaction records. Documents are not in scope for automated migration; the customer manages re-upload or a separate vendor-assisted document workstream. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation handoff
We freeze COINCAP writes during the cutover window, run a final delta migration of any records modified during the migration window, then hand control to Dolibarr as the system of record. We deliver a written inventory of every COINCAP module-specific workflow, custom report, and automation requiring rebuild in Dolibarr. The customer's admin or a Dolibarr partner rebuilds these post-migration. We provide a one-week hypercare window to resolve reconciliation issues; we do not rebuild COINCAP automations as Dolibarr workflows inside the migration scope.
Platform deep dives
COINCAP ERP
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 1 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 COINCAP ERP and Dolibarr ERP.
Object compatibility
1 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
COINCAP ERP: Not publicly documented.
Data volume sensitivity
COINCAP ERP 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 COINCAP ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your COINCAP ERP 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 COINCAP ERP
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.