ERP migration
Field-level mapping, validation, and rollback between IS Packaging and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
IS Packaging
Source
Dolibarr ERP
Destination
Compatibility
9 of 12
objects map 1:1 between IS Packaging and Dolibarr ERP.
Complexity
BStandard
Timeline
4-6 weeks
Overview
IS Packaging organizes packaging manufacturing data around Items, BOMs, Production Orders, Work Orders, and Finished Goods with lot/serial traceability and revision-controlled recipes. Dolibarr is an open-source PHP/MySQL ERP with a modular architecture that covers products, stock, third parties, projects, and invoicing but lacks a dedicated production scheduling module. The migration challenge is translating IS Packaging's multi-plant production context into Dolibarr's warehouse-and-project model without a documented public API on the source side. We extract IS Packaging data through direct database access, normalize lot identifiers across plants, apply a BOM revision cross-reference table, and map open Production Orders to Dolibarr Projects with custom status fields. We do not migrate workflows, automations, or custom manufacturing scheduling rules as code; we deliver a written inventory of these for the customer's admin to rebuild in Dolibarr's workflow module or via custom PHP development.
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 IS Packaging 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.
IS Packaging
Items
Dolibarr ERP
Product (stockable)
1:1IS Packaging Items (item number, description, uom, category, costing layers) map to Dolibarr Product records with type Stockable. We preserve standard cost from IS Packaging in a custom field and map the uom to Dolibarr's unit-of-measure field. Item categories map to Dolibarr product categories for inventory grouping. Custom properties on Items migrate as extrafields in the Dolibarr product table.
IS Packaging
Bill of Materials (BOMs)
Dolibarr ERP
BOM
1:1IS Packaging BOMs with revision-controlled recipes map to Dolibarr BOM. Each BOM revision in IS Packaging maps to a separate Dolibarr BOM with its own bom.fk_product, bom.lines referencing component products and quantities. Phantom assemblies, routing steps, and work center assignments from IS Packaging's routing table are preserved in custom BOM fields and line comments. We apply a BOM revision cross-reference table built during discovery to match date-effective revisions to Dolibarr BOM versions.
IS Packaging
Production Orders
Dolibarr ERP
Project
1:manyIS Packaging Production Orders (BOM-linked, scheduled quantity, plant, work center, status, completion percentage) map to Dolibarr Project records with custom ProjectTask lines representing work steps. The Production Order status (Quoted, Released, In Process, Complete, Closed) maps to a Dolibarr Project status set we configure before migration. Completion percentages migrate as ProjectTask progress. Plant and work center assignments migrate as project extrafields. Open Production Orders require status validation before migration; we either quiesce them or build a status mapping matrix.
IS Packaging
Work Orders
Dolibarr ERP
ProjectTask
1:1IS Packaging Work Orders tied to Production Orders (scheduling, labor hours, machine time) map to Dolibarr ProjectTask records linked to the parent Project from the Production Order mapping. Task duration and estimated hours migrate from IS Packaging work order labor fields. Status flags vary by plant so we apply destination-status mapping during import using a per-plant status cross-reference built during discovery.
IS Packaging
Finished Goods Locations
Dolibarr ERP
Warehouse + Stock
1:1IS Packaging Finished Goods stored at Locations with lot/serial tracking map to Dolibarr Warehouse records with stock on-hand quantities. Lot numbers and serial numbers migrate as Dolibarr lot/serial batch records linked to the Product and Warehouse. On-hand quantities migrate as Dolibarr Stock movements (stockdesk). Location-specific lot conventions are normalized during extraction using a per-plant lot format normalization table.
IS Packaging
Inventory Transactions
Dolibarr ERP
StockMovement
lossyIS Packaging inventory transaction history (receipts, issues, adjustments) migrates to Dolibarr StockMovement records linked to Product and Warehouse. Due to volume, we use chunked extraction ordered by transaction date to preserve chronological integrity. We only migrate transactional history within the agreed scope window; very large histories may be scoped to the last 12-24 months or archived. Dolibarr's stockmovement table uses positive/negative qty to indicate direction.
IS Packaging
Customer Orders
Dolibarr ERP
Order + Invoice
1:1IS Packaging open Customer Orders map to Dolibarr Order records with line items referencing Products. Pricing rules and exceptions from IS Packaging migrate to order line price and discount fields. If the source orders are invoiced, we map to Dolibarr Facture (Invoice) instead. We flag any pricing exceptions for manual review before import. Third-party references on orders map to the corresponding Dolibarr ThirdParty contact.
IS Packaging
Vendor Records
Dolibarr ERP
ThirdParty (supplier)
1:1IS Packaging Vendor masters (contact info, payment terms, item-supplier cross-references) map to Dolibarr ThirdParty records with the Supplier checkbox enabled. Payment terms migrate from IS Packaging vendor terms to Dolibarr_condreglation terms. Item-supplier cross-references migrate as Product-supplier price rows in Dolibarr. Vendor contact information maps to Dolibarr contact and address records linked to the ThirdParty.
IS Packaging
Chart of Accounts
Dolibarr ERP
Account (accounting module)
1:1IS Packaging account codes map to Dolibarr accounting plan entries if the customer activates the accounting module. We map account segments to Dolibarr's accounting chart structure and flag any intercompany or inactive accounts for reactivation. If IS Packaging uses a non-standard account structure, we flag mismatches and document the mapping for the customer's accountant to validate before import.
IS Packaging
Custom Fields
Dolibarr ERP
Extrafields
1:1Custom fields added to standard IS Packaging objects (Items, BOMs, Production Orders) migrate as Dolibarr extrafields on the equivalent objects. We inventory all custom field names, data types, and values during the discovery phase and create matching extrafield definitions in Dolibarr before import. Multi-select custom fields migrate as Dolibarr checkbox or varchar extrafields depending on structure.
IS Packaging
Lot/Serial Numbers
Dolibarr ERP
Batch
lossyIS Packaging lot numbers use different formats per plant (date-coded, supplier-prefixed, sequence-based). We normalize all lot identifiers into a unified format during extraction using a per-plant lot format rule built during discovery. Normalized lot numbers migrate as Dolibarr Batch records with batch_number, batch_fk_product, batch_fk_warehouse, and expiry date where applicable. All lot transactions re-associate to the normalized batch identifiers to prevent orphaned traceability records.
IS Packaging
MRP Pegging
Dolibarr ERP
ProjectTask (planning)
1:1IS Packaging MRP pegging links customer demand to specific production orders. We migrate pegging relationships as ProjectTask parent-child links within the Dolibarr Project structure. If the customer's production planning requires MRP functionality post-migration, we recommend evaluating Dolibarr's third-party manufacturing addons (available on Dolibarr MarketPlace) as the MRP rebuild path.
| IS Packaging | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Items | Product (stockable)1:1 | Fully supported | |
| Bill of Materials (BOMs) | BOM1:1 | Fully supported | |
| Production Orders | Project1:many | Fully supported | |
| Work Orders | ProjectTask1:1 | Mapping required | |
| Finished Goods Locations | Warehouse + Stock1:1 | Fully supported | |
| Inventory Transactions | StockMovementlossy | Mapping required | |
| Customer Orders | Order + Invoice1:1 | Mapping required | |
| Vendor Records | ThirdParty (supplier)1:1 | Fully supported | |
| Chart of Accounts | Account (accounting module)1:1 | Mapping required | |
| Custom Fields | Extrafields1:1 | Mapping required | |
| Lot/Serial Numbers | Batchlossy | Fully supported | |
| MRP Pegging | ProjectTask (planning)1:1 | 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.
IS Packaging gotchas
BOM revision control must be matched to destination version exactly
Open production orders must be status-mapped or manually closed first
Lot and serial number formats differ between plants in the same instance
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 database access validation
We inventory all IS Packaging objects in scope (Items, BOMs, BOM revisions, Production Orders, Work Orders, Finished Goods, Inventory Balances, Customer Orders, Vendors, Lot/Serial records, Custom Fields) and identify the source database platform and access method. We extract a schema sample to confirm table structures and relationships. We also inventory the target Dolibarr version, activated modules, and existing data. The discovery output is a written scope document with a record count estimate per object and a database access assessment.
BOM revision cross-reference and lot normalization design
We build the BOM revision cross-reference table that maps each IS Packaging BOM revision (effective date, revision number, plant) to a Dolibarr BOM version. We also design the per-plant lot format normalization rules for multi-plant consolidations. These rules are validated against sample data from each plant before extraction begins. This step is critical for BOM and lot data quality in the destination system.
Dolibarr schema provisioning and configuration
We configure the destination Dolibarr instance: create product categories matching IS Packaging item categories, create warehouses per plant or consolidated per the migration plan, enable and configure the BOM module, activate the accounting module if chart of accounts migration is in scope, create extrafield definitions for custom fields from IS Packaging, and configure the project status set to match the IS Packaging production order lifecycle. We deploy into a test environment first.
Extraction, transformation, and validation in staging
We extract IS Packaging data using direct database queries (or VAR-provided export) ordered by dependency: Items first, then BOMs with revision cross-reference applied, then Inventory Balances and Lots, then open and historical Production Orders with status mapping applied, then Work Orders linked to their parent Projects, then Customer Orders and Vendor Records, then Inventory Transactions in date-ordered chunks. Each extraction phase is validated against IS Packaging record counts before transformation begins. We run a full staging migration into a test Dolibarr instance and reconcile record counts, lot associations, and BOM linkages before proceeding.
Production migration in dependency order with delta capture
We run production migration in record-dependency order: Products, BOMs (with revisions), Warehouses, Third Parties, Projects (from Production Orders), ProjectTasks (from Work Orders), Stock and Batch records, Customer Orders, then Inventory Transactions. Each phase emits a row-count reconciliation report. During the migration window, any records modified in IS Packaging are captured as a delta and applied after the initial load. We coordinate a freeze window with the customer's operations team for the final delta cutover.
Cutover, validation, and manufacturing workflow handoff
We freeze IS Packaging writes, run the final delta migration, then enable Dolibarr as the system of record. We validate 25-50 randomly selected records against the IS Packaging source for each object. We deliver a written inventory of any IS Packaging workflows, production scheduling rules, or manufacturing automations that do not migrate, with recommended Dolibarr equivalents and a Dolibarr MarketPlace addon shortlist for manufacturing addons. We support a one-week hypercare window for reconciliation issues. We do not rebuild production scheduling workflows in Dolibarr as part of the standard migration scope.
Platform deep dives
IS Packaging
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 IS Packaging 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
IS Packaging: Not publicly documented — governed by underlying SAP S/4HANA Gateway and OData service limits, which we confirm with the vendor at scoping..
Data volume sensitivity
IS Packaging exposes a bulk API — large-volume migrations stream efficiently.
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 IS Packaging to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your IS Packaging 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 IS Packaging
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.