ERP migration

Migrate from Fraction ERP to Dolibarr ERP

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

Fraction ERP logo

Fraction ERP

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

92%

11 of 12

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

Complexity

BStandard

Timeline

3-6 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Fraction ERP to Dolibarr is a transition from a purpose-built cloud manufacturing ERP to a modular open-source ERP with a broader SMB focus. We extract Customers, Quotations, Sales Orders, Parts, Bills of Materials, Works Orders, Inventory, and Purchase Orders from Fraction ERP and map each to its corresponding Dolibarr module: Third-Party, Proposal, Order, Product, BOM, Workstation-Order, Stock, and Supplier-Order. Dolibarr charges no per-user license, which eliminates the £36-£50/user/month recurring cost, but requires self-managed hosting and explicit activation of its manufacturing modules. We do not migrate Workflows or automations; we deliver a written inventory of every active rule requiring rebuild in Dolibarr's trigger system. BOM drawings are extracted as file attachments and linked to their Product records in Dolibarr's document management system during migration.

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

Fraction ERP logo

Fraction ERP

What's pushing teams away

  • Customers report that the platform lacks depth in financial management modules, pushing them toward NetSuite or Sage Intacct once their business scales beyond basic job costing.
  • The limited number of reviews and small user community makes it difficult to find implementation partners or peer advice when problems arise during deployment.
  • Manufacturers with highly custom workflows or complex multi-plant operations find the platform's configurability insufficient for their needs over time.
  • Some users mention that the user interface feels less polished than competing ERPs, leading to slower user adoption on the shop floor.

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

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

Fraction ERP

Customer

maps to

Dolibarr ERP

Third-Party (Client)

1:1
Fully supported

Fraction ERP Customers map to Dolibarr Third-Party records with type Client. We extract company name, billing address, delivery address, phone, email, and any custom fields, and populate Dolibarr's address, contact, and bank account tabs. Third-Party is the primary entity in Dolibarr's data model and must be created before any linked Sales Orders or Proposals are imported.

Fraction ERP

Quotation

maps to

Dolibarr ERP

Proposal

1:1
Fully supported

Fraction ERP Quotations map to Dolibarr Proposal records linked to the relevant Third-Party. We transfer quotation number, validity date, line items with descriptions and unit prices, and discount percentages. The status mapping converts Fraction ERP quotation stages (Draft, Sent, Accepted, Lost) to Dolibarr Proposal status values. Note that quote-to-order conversion in Dolibarr requires a manual action in the UI rather than an automated trigger.

Fraction ERP

Sales Order

maps to

Dolibarr ERP

Order

1:1
Fully supported

Fraction ERP Sales Orders map to Dolibarr Customer Order records. The linked Customer maps to the Third-Party on the Dolibarr Order. Line items migrate with product references, quantities, unit prices, and order totals. Fraction ERP's Sales Order status (Pending, In Production, Completed, Cancelled) maps to Dolibarr Order status values, and open Orders are prioritised for import before historical closed records.

Fraction ERP

Part

maps to

Dolibarr ERP

Product

1:1
Fully supported

Fraction ERP Parts map to Dolibarr Product records of type Item. We transfer part number (mapped to ref), description, unit of measure, cost price, and sales price. Fraction ERP's part type (stocked, non-stocked, service) maps to Dolibarr's product_type field. Barcode and custom properties migrate as Dolibarr extra fields.

Fraction ERP

Bill of Materials

maps to

Dolibarr ERP

BOM (Bill of Materials module)

1:1
Fully supported

Fraction ERP BOMs map to Dolibarr BOM records linked to the manufactured Part as Product. We transfer the multi-level component structure, quantities per assembly, unit of measure, and any BOM costing data. Operation routing (work centres, sequence, duration) transfers as BOM lines or notes depending on the Dolibarr BOM module version. Dolibarr BOMs with sub-assemblies require the Product sub-product feature to be enabled in the module configuration.

Fraction ERP

Works Order

maps to

Dolibarr ERP

Workstation-Order (Manufacturing module)

1:1
Fully supported

Fraction ERP Works Orders map to Dolibarr Workstation-Order records. We preserve the linked Sales Order reference, BOM reference, scheduled start and end dates, assigned workstation, operation status, and progress notes. Production output and scrap quantities migrate as Workstation-Order line data. Fraction ERP's shop floor data capture timestamps transfer as time-tracking entries on the Dolibarr Workstation-Order. The Dolibarr manufacturing module must be activated before Works Orders can be created.

Fraction ERP

Inventory

maps to

Dolibarr ERP

Stock (Warehouse module)

1:1
Mapping required

Fraction ERP Inventory transactions and current stock levels map to Dolibarr Stock records per warehouse. We extract part-level stock quantity, warehouse location, minimum stock threshold, and last movement date. Stock valuation methods (FIFO, average cost) from Fraction ERP are recorded as notes in Dolibarr because stock value calculation in Dolibarr depends on the configured warehouse valuation method. Multi-warehouse configurations require explicit warehouse creation in Dolibarr before import.

Fraction ERP

Purchase Order

maps to

Dolibarr ERP

Supplier Order

1:1
Fully supported

Fraction ERP Purchase Orders map to Dolibarr Supplier Order records linked to the vendor as a Third-Party of type Supplier. Line items, expected delivery dates, quantities ordered versus received, and order status transfer. Partial receipts are recorded as Dolibarr reception lines against the Supplier Order. Fraction ERP vendors that do not yet exist as Third-Parties are created during the vendor import phase before Purchase Orders are processed.

Fraction ERP

Non-Conformance Report

maps to

Dolibarr ERP

Intervention (Support module)

1:1
Fully supported

Fraction ERP NCRs map to Dolibarr Intervention records (from the Support/Tickets module) linked to the relevant Product or Workstation-Order. NCR description, severity classification, root cause, and corrective action text transfer as the Intervention description and resolution fields. Dolibarr's ticket and intervention system is less manufacturing-specific than Fraction ERP's NCR workflow; teams requiring formal quality management may need to activate the quality module add-on or document their quality process as a written procedure post-migration.

Fraction ERP

User

maps to

Dolibarr ERP

User

1:1
Fully supported

Fraction ERP User accounts (name, email, role, and permissions) map to Dolibarr User records. We match by email address as the primary key. Inactive Fraction ERP users are created as inactive Dolibarr users to preserve historical assignment on Works Orders and documents. Individual password credentials cannot be transferred and must be reset by each user post-migration. Role mapping from Fraction ERP permission levels to Dolibarr global permission groups requires manual review during the Dolibarr permissions configuration phase.

Fraction ERP

BOM Drawing (file attachment)

maps to

Dolibarr ERP

Document (DMS linked to Product)

1:1
Fully supported

Fraction ERP BOM drawings stored as file attachments do not export through standard grid exports and require a parallel file extraction pass using the platform's document export feature. We retrieve each drawing file, map it to the corresponding migrated Product in Dolibarr, and attach it via Dolibarr's Document Management System (DMS) linked to the Product record. Drawing file format (PDF, DWG, STEP) is preserved. All drawings for a given BOM are associated with the parent manufactured Part, not the sub-components.

Fraction ERP

Currency and Unit of Measure

maps to

Dolibarr ERP

Multi-Currency and UoM (System configuration)

lossy
Fully supported

Fraction ERP's configured currencies and units of measure transfer to Dolibarr's multi-currency and UoM settings via the Dolibarr Setup → Multi-Currency and Setup → Products → Units menus. Currency codes and exchange rate sources migrate as configured references. Fraction ERP Advanced tier multi-currency settings (available at £50/user/month) transfer as Dolibarr currency activation flags, with the customer responsible for setting up live exchange rate feeds in Dolibarr post-migration.

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.

Fraction ERP logo

Fraction ERP gotchas

High

No publicly documented API for bulk exports

Medium

BOM drawings stored as attachments require separate file transfer

Medium

Works Order operation sequencing is BOM-dependent

Low

Tier-gated features affect module availability

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

  • Dolibarr production module requires explicit activation and configuration

    Dolibarr's manufacturing and BOM modules are not active by default; they must be enabled under Home → Setup → Modules and configured with warehouses, workstations, and units of measure before any production records can be created. Fraction ERP's production capabilities are baked into the core application. We activate Dolibarr's BOM and Manufacturing modules during migration setup and configure at least one warehouse and workstation before importing Works Orders. Customers who skip this step will encounter record creation errors that stall the migration at the Works Order phase.

  • Fraction ERP has no publicly documented bulk export API

    Fraction ERP does not publish a public REST API with bulk export endpoints. All data extraction requires either a direct database export coordinated with Fraction ERP's implementation team or manual report generation from within the application. We cannot build fully automated extraction pipelines without Fraction ERP's technical cooperation. We request a data export package from Fraction ERP's team as the first step in every engagement and flag this dependency at scoping so it does not delay the project plan.

  • Works Order operation sequencing is BOM-dependent

    Fraction ERP Works Orders derive their operation routing from the linked Bill of Materials. If BOMs are migrated out of sequence or with a modified structure, existing Works Order history can reference non-existent operations. We enforce BOM-first sequencing in our migration pipeline and validate operation references before closing the Works Order phase. Any orphaned operation references are logged and resolved against the customer's live Fraction ERP instance before cutover.

  • BOM drawings and binary attachments require a separate file transfer pass

    Fraction ERP stores BOM drawing files as attachments linked to BOM records. These binary files do not export through standard grid exports and must be retrieved separately using the platform's document export feature. We schedule a parallel file extraction pass and map each drawing to the corresponding migrated Part in Dolibarr's Document Management System. If the document export is not available at extraction time, we flag this to the customer and hold the file migration as an open action pending access.

  • Fraction ERP tier-gated features require explicit Dolibarr module activation post-migration

    Fraction ERP Advanced tier at £50/user/month includes enhanced capacity planning and advanced scheduling features that have no direct Dolibarr equivalent. We confirm the customer's active tier during scoping and flag any Advanced-tier features in active use. Dolibarr's production module activation and any required third-party add-ons are documented as post-migration configuration steps. The customer is responsible for enabling the relevant Dolibarr modules and configuring capacity planning manually after cutover.

Migration approach

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

  1. Discovery and export package coordination

    We audit Fraction ERP across record counts (Customers, Parts, BOMs, Works Orders, Inventory, Purchase Orders), BOM complexity (levels, operation count, drawing attachments), active user count, and any Advanced-tier features in use. Simultaneously, we request a structured data export package from Fraction ERP's implementation team, as the platform has no public bulk export API. The discovery output is a written scoping document with record counts, export format confirmation, and a migration object list signed off by the customer before extraction begins.

  2. Dolibarr environment assessment and production module activation

    We assess the target Dolibarr instance: version number, activated modules, hosting configuration, and any pre-existing data. We activate the BOM module, Manufacturing module, Stock module, and Third-Party module if not already enabled. We create the initial warehouse structure matching Fraction ERP's location hierarchy and configure units of measure used in manufacturing. This step also includes establishing the data import user with sufficient Dolibarr permissions for bulk data creation.

  3. Migration schema design and field mapping

    We design the migration schema covering every object being transferred: Third-Party fields mapped from Customer, Proposal and Order from Quotations and Sales Orders, Product from Parts, BOM structure from Fraction ERP Bills of Materials, Workstation-Order from Works Orders, Stock from Inventory, Supplier Order from Purchase Orders, and Intervention from NCRs. BOM operation routing, drawing attachment mapping, and UoM configuration are documented as part of the schema. The mapping document is reviewed and signed off before any data is extracted from Fraction ERP.

  4. Data extraction, transformation, and load

    We extract data from Fraction ERP using the agreed export package, clean and transform records to match Dolibarr field types and structures, and load records in dependency order: reference data first (Third-Parties, Products, BOMs), then transactional data (Orders, Stock, Works Orders, Purchase Orders), then secondary records (NCRs, user assignments). We process BOM drawings and file attachments in a parallel pass and link them to their Product records in Dolibarr's DMS. Each phase produces a reconciliation report comparing source record counts to destination inserted counts.

  5. Validation, reconciliation, and sandbox sign-off

    We run reconciliation checks across all migrated objects: record counts, spot-checks on 20-50 random records against the Fraction ERP source, and validation of foreign key relationships (Third-Party on Orders, BOM on Works Orders, Product on Stock records). Any missing or malformed records are flagged in a correction log and re-migrated before the next phase. The customer reviews the reconciliation report and signs off the sandbox migration before production cutover is scheduled.

  6. Production migration, cutover, and handoff

    We migrate all remaining historical records into the production Dolibarr instance with Fraction ERP in read-only mode. A final delta pass captures any records modified during the migration window. We enable Dolibarr as the system of record and decommission Fraction ERP write access. We deliver a written automation inventory document covering every Fraction ERP workflow, alert, or rule that requires rebuild in Dolibarr's trigger system. We support a one-week post-go-live window for reconciliation issues. Post-migration admin configuration, team training, and Dolibarr workflow rebuild are outside standard scope.

Platform deep dives

Context on both ends of the pair

Fraction ERP logo

Fraction ERP

Source

Strengths

  • Integrated production-to-inventory data model designed specifically for manufacturing environments without requiring bolt-on modules.
  • Cloud-hosted accessibility means the system works from any browser, reducing on-premise infrastructure overhead for small manufacturers.
  • Native integrations with Xero, QuickBooks, and Sage provide clean handoff to established accounting platforms without manual re-entry.
  • Shop floor data capture module enables real-time production tracking without requiring separate MES investment.
  • Per-user pricing starting at £36/month makes it accessible for teams of 5–20 operators without enterprise-scale costs.

Weaknesses

  • Limited public API documentation means migration tooling must be reverse-engineered or coordinated through Fraction ERP's implementation team.
  • Small review corpus and limited third-party community make peer validation and troubleshooting support harder to find.
  • Financial management capabilities are intentionally shallow, pushing finance teams toward external accounting tools rather than centralising the ledger.
  • The platform targets SMB manufacturers exclusively and lacks the multi-plant, multi-currency, and advanced analytics features that growing companies eventually require.
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. 2 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 Fraction ERP and Dolibarr ERP.

  • Object compatibility

    B

    2 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

    Fraction ERP: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Fraction ERP to Dolibarr migrations land between three and six weeks for datasets under 1,000 Parts, 500 BOMs, and 2,000 Works Orders. Complex migrations with multi-level BOM structures, large production histories, NCR records, and multiple warehouses move to five to ten weeks because of BOM sequencing, operation routing validation, and file attachment extraction. The export coordination phase with Fraction ERP adds one to two weeks at the start if a custom data package is required.

Adjacent paths

Related migrations to explore

Ready when you are

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