ERP migration

Migrate from COINCAP ERP to Dolibarr ERP

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 logo

COINCAP ERP

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

86%

12 of 14

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

Complexity

BStandard

Timeline

5-8 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

COINCAP ERP logo

COINCAP ERP

What's pushing teams away

  • Companies evaluating modern cloud-first ERPs cite scalability constraints and limited mobile-first access as reasons to move off on-premise or hybrid COINCAP deployments.
  • G2 lists NetSuite, Sage Intacct, and Acumatica as top alternatives, indicating customers are leaving COINCAP for globally-supported platforms with broader ecosystem integrations and API access.
  • On-premise deployment requires internal IT resources for maintenance, backups, and version upgrades—businesses without dedicated IT staff find this ongoing overhead a driver to migrate to managed SaaS alternatives.

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

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

maps to

Dolibarr ERP

Account (Accounting)

1:1
Mapping required

COINCAP 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)

maps to

Dolibarr ERP

Third Party (Customer)

1:1
Fully supported

COINCAP 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)

maps to

Dolibarr ERP

Third Party (Supplier)

1:1
Fully supported

COINCAP 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)

maps to

Dolibarr ERP

Product

1:1
Fully supported

COINCAP 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)

maps to

Dolibarr ERP

Stock (Warehouse Stock)

1:1
Fully supported

COINCAP 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)

maps to

Dolibarr ERP

BOM (Manufacturing Module)

lossy
Fully supported

COINCAP 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)

maps to

Dolibarr ERP

Invoice (Customer) + Direct Accounting Entry

1:1
Fully supported

COINCAP 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)

maps to

Dolibarr ERP

Invoice (Supplier) + Direct Accounting Entry

1:1
Fully supported

COINCAP 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)

maps to

Dolibarr ERP

Invoice (Customer) + Order

1:1
Fully supported

COINCAP 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)

maps to

Dolibarr ERP

Invoice (Supplier) + Order

1:1
Fully supported

COINCAP 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)

maps to

Dolibarr ERP

Accounting Entries (Écritures Comptables)

1:1
Fully supported

COINCAP 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

maps to

Dolibarr ERP

Users and Permissions

1:1
Mapping required

COINCAP 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)

maps to

Dolibarr ERP

Extra Fields

lossy
Fully supported

COINCAP 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

maps to

Dolibarr ERP

None

1:1
Not supported

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

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.

COINCAP ERP logo

COINCAP ERP gotchas

High

No public REST API for self-service data export

High

Vendor-assisted export required due to opaque schema

Medium

On-premise deployments require infrastructure readiness at destination

Medium

No bulk attachment or document export capability

Low

Custom fields per vertical require scoping per deployment

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 REST API forces vendor-assisted data extraction

    COINCAP ERP does not expose a documented public REST API for bulk data extraction. All migration scoping begins with a vendor coordination phase where the customer's account manager at Coincap Systems & Services defines export formats—typically direct database queries or custom export routines built by the COINCAP technical team. We cannot begin the migration pipeline until the export format is agreed and at least one sample export is delivered for schema validation. This step adds two to four weeks of lead time and requires the customer to maintain an active relationship with COINCAP support throughout the extraction phase.

  • Internal schema opaque without direct COINCAP engagement

    COINCAP's database schema is not publicly documented. Custom fields, module-specific extensions, and industry-vertical modifications are invisible without direct engagement with COINCAP technical staff. We conduct a schema audit in collaboration with the COINCAP team, mapping discovered columns to standard ERP object categories. Any columns without a clear mapping are flagged for manual review before the migration window opens. Migrations that skip the schema audit risk importing custom field data into wrong Dolibarr columns, producing silent data corruption.

  • Indian GST compliance must be explicitly configured in Dolibarr

    COINCAP ERP carries Indian GST tax codes (CGST, SGST, IGST) embedded in its chart of accounts and transaction records. Dolibarr's base accounting module is multi-country and requires explicit activation of Indian GST configuration—VAT mode set to Indian GST, tax rates matching current GST slabs (5%, 12%, 18%, 28%), and HSN code alignment on products. We configure the GST tax regime in Dolibarr during module setup before any transaction import. Businesses operating under composition scheme, TDS deductions, or e-invoicing requirements need additional Dolibarr community module configuration beyond standard scope.

  • Documents and attachments cannot be retrieved via any documented API

    COINCAP ERP stores scanned documents and attachments linked to transaction vouchers and master records. There is no documented public API endpoint for bulk attachment retrieval. We identify all COINCAP records with linked documents during discovery and present the customer with three options: manual re-upload post-migration, a separate document-migration workstream requiring custom COINCAP export routines (vendors additional fee), or accepting that attachments will not migrate. Transaction PDFs may exist as printed output files rather than stored documents; the COINCAP team confirms availability during vendor coordination.

  • Custom fields per industry vertical require per-deployment scoping

    COINCAP serves 11 industry verticals, and deployments frequently include module-specific custom fields not present in the base product. These are invisible to customers without direct COINCAP engagement. We cannot define a standard mapping for custom fields without examining the specific customer's live instance. The migration scoping call must include a walkthrough of all active modules to surface custom field variations before we build the Dolibarr extrafields definition and field-mapping matrix.

Migration approach

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

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

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

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

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

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

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

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

Context on both ends of the pair

COINCAP ERP logo

COINCAP ERP

Source

Strengths

  • Nine-module integrated suite covering finance, inventory, purchase, sales, and production within one database.
  • 100% guaranteed implementation commitment marketed as the primary customer assurance differentiator.
  • Domestic Indian vendor with Mumbai-based support and GST-compliant finance modules for Indian regulatory requirements.
  • COINCAP-III version signals active development and periodic product upgrades for existing customers.
  • Long customer retention—references spanning 25+ years suggest stable product-market fit for mid-market industrial companies.

Weaknesses

  • No publicly documented REST API or bulk export interface, making automated migration reliant on vendor-assisted data pulls.
  • On-premise deployment model requires customer-managed infrastructure, backups, and upgrade scheduling.
  • Limited visibility into COINCAP's internal schema outside of direct vendor engagement, complicating pre-migration audit.
  • Pricing and licensing terms are not published publicly, requiring direct sales contact for every evaluation.
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 COINCAP 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

    COINCAP ERP: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Most migrations land between five and eight weeks for accounts under 10,000 party records and 5,000 transaction vouchers with no multi-level BOM complexity. Migrations with large transaction histories (over 100,000 vouchers), multi-level BOM structures, multiple active industry-vertical custom fields, or a need for parallel COINCAP and Dolibarr parallel-run periods move to ten to eighteen weeks. The vendor coordination and export format agreement phase alone typically takes two to four weeks and gates the entire project timeline.

Adjacent paths

Related migrations to explore

Ready when you are

Move from COINCAP 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