ERP migration

Migrate from iCast to Dolibarr ERP

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

iCast logo

iCast

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

83%

10 of 12

objects map 1:1 between iCast and Dolibarr ERP.

Complexity

CModerate

Timeline

4-6 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from iCast to Dolibarr is a cross-platform ERP migration that requires coordinating data extraction through iCast professional services since no self-service export exists, then building Dolibarr's modular schema before loading records via CSV. iCast uses separate Customer and Vendor objects; Dolibarr consolidates these under Third Parties with a Type field distinguishing customers from suppliers. We map inventory locations to Dolibarr Warehouses, map iCast's hierarchical Chart of Accounts to Dolibarr's accounting module, and preserve journal entry line structure. Multi-location inventory from iCast maps to Dolibarr's multi-warehouse configuration. We do not migrate custom iCast fields, calculated fields, or saved reports as they require manual recreation in Dolibarr's module builder. Workflows and automations built in iCast do not migrate; we deliver a written inventory for the customer's admin to rebuild using Dolibarr's workflow and trigger system.

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

iCast logo

iCast

What's pushing teams away

  • Foundry-specific positioning means iCast does not fit other discrete or process manufacturing verticals — companies diversifying beyond foundry operations may need to layer additional ERP modules.
  • Limited public reviewer presence on G2 and Capterra makes peer validation difficult outside the foundry industry.
  • Implementation typically requires vendor services rather than self-serve setup, increasing time-to-value.
  • Mobile and cloud-native UX lag modern SaaS ERPs.
  • No publicly documented developer API restricts integration into MES, IoT, or BI platforms common in modernized foundries.

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

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

iCast

Customer

maps to

Dolibarr ERP

Third Party (Type = Customer)

1:1
Fully supported

iCast Customer records with payment terms, credit limits, and account managers map to Dolibarr Third Party records with Type set to Customer. The source payment terms map to Dolibarr's fk_payment_termout field. We extract customers first so that the Third Party IDs are available for linking during Sales Order and Invoice import. Duplicate detection uses company name and email as matching criteria.

iCast

Vendor

maps to

Dolibarr ERP

Third Party (Type = Supplier)

1:1
Fully supported

iCast Vendor records map to Dolibarr Third Party with Type = Supplier. The source vendor account number maps to Dolibarr's code_fournisseur field for supplier code tracking. Vendor payment terms map to fk_payment_termout. We load all vendors before Purchase Orders so that the supplier linkage resolves correctly during PO import.

iCast

Inventory Item

maps to

Dolibarr ERP

Product (Article)

1:1
Fully supported

iCast inventory items with SKU, description, unit of measure, cost, and warehouse location map to Dolibarr Product records. The product_type field is set to 1 for stockable items matching iCast's inventory tracking. Unit of measure maps to Dolibarr's unit_of_measure field. Multi-location inventory from iCast (multiple warehouse assignments per item) maps to Dolibarr Warehouse records with inventory tracked per warehouse via the stock module.

iCast

Inventory Location

maps to

Dolibarr ERP

Warehouse

lossy
Fully supported

iCast warehouse location codes map to Dolibarr Warehouse records created in the stock module. Each warehouse gets an address and manager assignment. The product-to-warehouse relationship is established via the和产品_stock table during inventory load, preserving per-location quantity on hand from iCast's last inventory snapshot.

iCast

Sales Order

maps to

Dolibarr ERP

Order

1:1
Fully supported

Open and historical iCast Sales Orders map to Dolibarr Order records with the customer Third Party ID linked via fk_soc. Order status from iCast maps to Dolibarr's fk_statut field (0=Draft, 1=Validated, etc.). Line items, pricing, and quantities map to OrderLines with the Product reference resolved from the inventory mapping. We recommend closing open iCast orders and importing only current-state or recently closed orders to reduce complexity.

iCast

Purchase Order

maps to

Dolibarr ERP

Supplier Order

1:1
Fully supported

iCast Purchase Orders map to Dolibarr Supplier Order records with the vendor Third Party ID linked via fk_soc. Line items reference the Product records imported from iCast inventory. Expected delivery dates map to date_liv_expected. We map vendor-held PO references to the ref_supplier field for cross-system auditing.

iCast

Chart of Accounts

maps to

Dolibarr ERP

Account (Accounting Module)

lossy
Mapping required

iCast's hierarchical chart of accounts with account numbers, types, and parent-child relationships maps to Dolibarr's accounting module account structure. We create the full account hierarchy in Dolibarr's plan_comptable table before journal entry import so that all account references in journal lines resolve correctly. Account type mapping (asset, liability, equity, income, expense) follows Dolibarr's pcg_type field values.

iCast

Journal Entry

maps to

Dolibarr ERP

Accounting Entry (Ecriture)

1:1
Fully supported

iCast general journal entries with date, account references, debit/credit amounts, and memo fields map to Dolibarr accounting entries. We import journal lines with the account ID resolved to the new Dolibarr account codes, debit/credit amounts preserved, and the original iCast memo retained in the label field. Entries referencing accounts not yet created in Dolibarr go to a reconciliation queue for account creation before retry.

iCast

User

maps to

Dolibarr ERP

User

1:1
Fully supported

iCast User accounts with login, roles, and access permissions map to Dolibarr User records. We match by email address. Any iCast user without a corresponding Dolibarr user goes to a reconciliation queue for admin provisioning. Role structures require manual recreation in Dolibarr's Users and Rights management (DOLIBARR_ADMIN_ALL_PERMS flag) since role modeling differs from iCast.

iCast

Sales Order Line Item

maps to

Dolibarr ERP

Order Line

1:1
Fully supported

iCast sales order line items map to Dolibarr OrderLine records linked to the parent Order via fk_commande. Each line references the Product ID resolved from the inventory item mapping. Quantity, unit price, discount percentage, and VAT rate migrate directly. Extended amounts recalculate in Dolibarr on insert.

iCast

Purchase Order Line Item

maps to

Dolibarr ERP

Supplier Order Line

1:1
Fully supported

iCast purchase order line items map to Dolibarr CommandeFournisseurLigne records with fk_commande linked to the parent Supplier Order. Product reference, quantity, cost, and discount migrate. We validate that the source unit cost aligns with the Product's buying price in Dolibarr before insert.

iCast

Product Image / Attachment

maps to

Dolibarr ERP

Document (documents directory)

1:1
Fully supported

iCast attachments on inventory items and orders map to files in Dolibarr's documents directory (or dolibarr_documents root). We extract binary attachments, copy them to the corresponding Dolibarr entity subdirectory (products, orders, etc.), and create the database record in the extension_table referencing the file path. Image thumbnails preserve for product catalog display.

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.

iCast logo

iCast gotchas

High

No self-service data export mechanism

Medium

Custom fields and reports do not migrate automatically

Medium

Historical data volume complicates migration timelines

Low

Limited third-party integrator ecosystem

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

  • iCast has no self-service export; extraction requires professional services coordination

    iCast does not provide a documented API or self-service export for bulk data extraction. Customers migrating away must contact iCast professional services or their implementation partner to obtain database access or a data extract. We initiate this coordination during discovery to avoid timeline surprises. Without proactive engagement with iCast, extraction alone can add two to four weeks to a project. We include the extraction step in the project schedule and budget from day one.

  • Dolibarr consolidates Customers and Vendors into a single Third Party object

    iCast maintains separate Customer and Vendor objects, but Dolibarr uses a single Third Party entity with a Type field (Customer, Supplier, or both) to represent both. During migration, we map iCast Customer records to Third Party with Type = Customer and Vendor records to Third Party with Type = Supplier. If a single entity appears as both a customer and vendor in iCast, we create one Third Party with both types set. The mapping handles duplicate detection by email and company name before insert.

  • Custom fields and calculated fields require manual recreation in Dolibarr

    iCast customers frequently build custom fields, calculated fields, and saved reports tailored to manufacturing or distribution workflows. These have no automatic export path. We inventory every custom field during discovery, document its purpose and calculation logic, and deliver the list to the customer so their admin can recreate it using Dolibarr's Extrafields system or Module Builder. Calculated fields that depended on iCast-specific functions require review for equivalent expression in Dolibarr.

  • Multi-entity iCast configurations require separate Dolibarr instance or multi-company setup

    iCast supports multi-entity and multi-location operations under a unified database. If the iCast migration scope includes multiple legal entities, Dolibarr requires either a separate instance per entity or its multi-company module configuration. We scope the entity structure during discovery and recommend the appropriate approach based on whether entities share a chart of accounts, tax configuration, or require data isolation.

  • Historical data volume affects extraction time and migration cost

    Mid-market iCast customers often carry years of transactional history including open orders, purchase orders, inventory snapshots, and journal entries. We scope the historical window with the customer upfront, balancing the desire for complete history against migration cost and Dolibarr data hygiene. We recommend a cutover inventory count to close the books in iCast before a final extract of current-state data, and optionally load a defined number of historical periods of journal entries rather than full history.

Migration approach

Six steps for a successful iCast to Dolibarr ERP data migration

  1. Discovery and extraction coordination with iCast

    We audit the iCast environment across all modules in scope (Customers, Vendors, Inventory, Sales Orders, Purchase Orders, Chart of Accounts, Journal Entries, Users). We document the historical window, identify custom fields and calculated fields, and assess the multi-entity structure. We initiate coordination with iCast professional services to schedule database extraction or managed export, and include this extraction step in the project timeline with buffer days for iCast response.

  2. Dolibarr schema setup and module configuration

    We configure the Dolibarr instance with the modules required for the migration scope: Third Parties (with customer and supplier types enabled), Products (stock module for inventory), Orders, Supplier Orders, Accounting (if financial history is in scope), and Warehouse management. We create the warehouse records matching the iCast inventory location codes, and we pre-build the chart of accounts in Dolibarr's accounting module before journal entry import. The migration user receives Create/Read/Update permissions on the relevant modules.

  3. Third party and product import

    We import all iCast Customer records as Dolibarr Third Parties with Type = Customer, followed by all Vendor records as Third Parties with Type = Supplier. The import uses Dolibarr's CSV import wizard (enabled via the Tools module) with a custom CSV profile we build during setup that maps iCast field names to Dolibarr column headers. After third parties load, we import iCast inventory items as Dolibarr Products, establishing the product ID mapping required for all downstream order and line item imports. We run duplicate detection (by email for contacts, by name+address for companies) and flag any potential duplicates for manual review.

  4. Sales Orders and Purchase Orders import

    With third parties and products loaded, we import open iCast Sales Orders as Dolibarr Orders and Purchase Orders as Supplier Orders. Line items import with the product reference resolved to the new Dolibarr product ID. We hold orders with a status of Pending or Held for customer review before inserting into the validated state. We preserve the original iCast order number in Dolibarr's ref_customer and ref_supplier fields for cross-reference.

  5. Chart of Accounts and Journal Entry import

    We create the full iCast chart of accounts in Dolibarr's accounting module, mapping account types to Dolibarr's pcg_type values and preserving the parent-child hierarchy. With the account structure confirmed, we import journal entries in date order, inserting debit/credit lines with the resolved account ID. Entries referencing accounts not yet created go to a hold queue; we resolve and retry until all lines insert without referential integrity errors. We validate total debits equal total credits per entry as a checksum.

  6. Cutover, validation, and custom field handoff

    We freeze writes in iCast during cutover, run a final delta migration of any records modified since the last extract, validate record counts against the iCast source totals, and spot-check 25-50 records for field-level accuracy. We deliver the custom field inventory document to the customer's Dolibarr admin with the list of fields to recreate in Extrafields and any calculation logic to implement via Dolibarr's calculated field system or custom PHP hook. We support a five-day hypercare window for reconciliation issues.

Platform deep dives

Context on both ends of the pair

iCast logo

iCast

Source

Strengths

  • Specializes in manufacturing and distribution workflows with job costing and shop floor tracking
  • Provides integrated inventory management and warehouse operations within a single platform
  • Serves multi-entity and multi-location operations under a unified database
  • Offers specialized tools for production planning and supply chain visibility not found in entry-level accounting software
  • Typically positioned at a lower price point than enterprise ERP platforms

Weaknesses

  • Limited customization and reporting flexibility compared to larger ERP systems
  • Constrained scalability with user counts and data storage limits relative to growing organizations
  • Smaller third-party ecosystem and fewer integration options than mainstream ERP vendors
  • Potential concerns about long-term vendor viability and product roadmap direction
  • Support quality and responsiveness reported as inconsistent by some long-term users
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?

Moderate ERP migration. 4 of 8 objects need a mapping; the rest are 1:1.

C

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across iCast and Dolibarr ERP.

  • Object compatibility

    C

    4 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

    iCast: Not publicly documented..

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your iCast 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 third parties, 5,000 inventory items, and a scoped historical window (current year plus one prior) land in four to six weeks. Migrations with multi-location inventory, large journal entry histories (over 50,000 lines), or multiple iCast entities require eight to twelve weeks. The primary variable is the extraction timeline with iCast professional services, which can add two to four weeks if not initiated early in discovery.

Adjacent paths

Related migrations to explore

Ready when you are

Move from iCast.
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