ERP migration
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
Source
Dolibarr ERP
Destination
Compatibility
11 of 12
objects map 1:1 between Fraction ERP and Dolibarr ERP.
Complexity
BStandard
Timeline
3-6 weeks
Overview
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.
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 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
Dolibarr ERP
Third-Party (Client)
1:1Fraction 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
Dolibarr ERP
Proposal
1:1Fraction 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
Dolibarr ERP
Order
1:1Fraction 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
Dolibarr ERP
Product
1:1Fraction 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
Dolibarr ERP
BOM (Bill of Materials module)
1:1Fraction 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
Dolibarr ERP
Workstation-Order (Manufacturing module)
1:1Fraction 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
Dolibarr ERP
Stock (Warehouse module)
1:1Fraction 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
Dolibarr ERP
Supplier Order
1:1Fraction 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
Dolibarr ERP
Intervention (Support module)
1:1Fraction 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
Dolibarr ERP
User
1:1Fraction 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)
Dolibarr ERP
Document (DMS linked to Product)
1:1Fraction 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
Dolibarr ERP
Multi-Currency and UoM (System configuration)
lossyFraction 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.
| Fraction ERP | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Customer | Third-Party (Client)1:1 | Fully supported | |
| Quotation | Proposal1:1 | Fully supported | |
| Sales Order | Order1:1 | Fully supported | |
| Part | Product1:1 | Fully supported | |
| Bill of Materials | BOM (Bill of Materials module)1:1 | Fully supported | |
| Works Order | Workstation-Order (Manufacturing module)1:1 | Fully supported | |
| Inventory | Stock (Warehouse module)1:1 | Mapping required | |
| Purchase Order | Supplier Order1:1 | Fully supported | |
| Non-Conformance Report | Intervention (Support module)1:1 | Fully supported | |
| User | User1:1 | Fully supported | |
| BOM Drawing (file attachment) | Document (DMS linked to Product)1:1 | Fully supported | |
| Currency and Unit of Measure | Multi-Currency and UoM (System configuration)lossy | 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.
Fraction ERP gotchas
No publicly documented API for bulk exports
BOM drawings stored as attachments require separate file transfer
Works Order operation sequencing is BOM-dependent
Tier-gated features affect module availability
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 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.
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.
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.
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.
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.
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
Fraction ERP
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 2 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 Fraction ERP and Dolibarr ERP.
Object compatibility
2 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
Fraction ERP: Not publicly documented.
Data volume sensitivity
Fraction 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 Fraction ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Fraction 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.