ERP migration

Migrate from IS Packaging to Dolibarr ERP

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 logo

IS Packaging

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

75%

9 of 12

objects map 1:1 between IS Packaging and Dolibarr ERP.

Complexity

BStandard

Timeline

4-6 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

IS Packaging logo

IS Packaging

What's pushing teams away

  • As an SAP S/4HANA-based solution, IS Packaging inherits the cost profile and implementation complexity of S/4HANA — smaller converters often migrate to lighter-weight packaging ERPs (Aptean Flex Pack, ePS, SYSPRO) when the SAP TCO outpaces their growth.
  • Pricing is not published — total cost of ownership is sales-led and depends heavily on SAP licensing, infrastructure, and Aicomp implementation scope, which makes budget planning slow versus competitors with published per-user tiers.
  • Cloud-native deployment is limited compared to pure-SaaS packaging ERPs; customers wanting elastic infrastructure and quick provisioning may prefer Advantive or DELMIAworks for similar industry fit.
  • Customisation depth on the SAP layer can become a maintenance liability — converters that over-customise the configurator find S/4HANA upgrades require regression testing of all packaging-specific extensions.
  • Public technical documentation (API references, integration recipes, developer portals) is thin compared to mid-market ERPs, leaving partners and customer IT teams reliant on Aicomp consulting for integration design.

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

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

maps to

Dolibarr ERP

Product (stockable)

1:1
Fully supported

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

maps to

Dolibarr ERP

BOM

1:1
Fully supported

IS 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

maps to

Dolibarr ERP

Project

1:many
Fully supported

IS 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

maps to

Dolibarr ERP

ProjectTask

1:1
Mapping required

IS 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

maps to

Dolibarr ERP

Warehouse + Stock

1:1
Fully supported

IS 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

maps to

Dolibarr ERP

StockMovement

lossy
Mapping required

IS 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

maps to

Dolibarr ERP

Order + Invoice

1:1
Mapping required

IS 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

maps to

Dolibarr ERP

ThirdParty (supplier)

1:1
Fully supported

IS 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

maps to

Dolibarr ERP

Account (accounting module)

1:1
Mapping required

IS 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

maps to

Dolibarr ERP

Extrafields

1:1
Mapping required

Custom 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

maps to

Dolibarr ERP

Batch

lossy
Fully supported

IS 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

maps to

Dolibarr ERP

ProjectTask (planning)

1:1
Fully supported

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

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.

IS Packaging logo

IS Packaging gotchas

High

BOM revision control must be matched to destination version exactly

Medium

Open production orders must be status-mapped or manually closed first

Medium

Lot and serial number formats differ between plants in the same instance

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

  • IS Packaging has no documented public API

    IS Packaging implementations lack a widely published REST or bulk export API. Extraction depends on direct database access, which varies by customer implementation, VAR configuration, and database platform (SQL Server, Progress, or other). During discovery, we must identify the database type, confirm read access, and inventory the schema before designing the extraction approach. Migrations without database access require the customer to engage their VAR for a data export, which adds scope and timeline risk.

  • BOM revision control must match destination versions exactly

    IS Packaging tracks BOM revisions with effective dates. Dolibarr's BOM module has a version field but no built-in date-effective revision lifecycle. We build a revision cross-reference table during discovery that maps each IS Packaging BOM revision to a Dolibarr BOM version identifier. If the destination uses a different revision scheme (date-based vs. sequential vs. alpha-numeric), the cross-reference table prevents incorrect material assignments on imported Production Orders and Work Orders.

  • Dolibarr has no native production scheduling module

    IS Packaging production orders, work centers, and MRP pegging do not have a direct Dolibarr equivalent. Dolibarr's Project module handles task management but lacks work center routing, production queue scheduling, and MRP. We map Production Orders to Projects and Work Orders to Tasks, but customers requiring ongoing production scheduling must source a third-party Dolibarr manufacturing addon (Dolibarr MarketPlace) or plan custom PHP development. This should be disclosed during scoping so the customer can budget for it.

  • Lot number format normalization across multi-plant instances

    Packaging companies using IS Packaging often operate different lot-numbering conventions per plant (date-coded, supplier-prefixed, sequence-based). When consolidating multi-plant data into a single Dolibarr instance, we normalize lot identifiers into a unified format using per-plant normalization rules built during discovery. Without normalization, Dolibarr's batch tracking creates duplicate lot records for the same physical lot, breaking traceability and inventory reconciliation.

  • Open Production Orders require status mapping or manual closure

    Active Production Orders in IS Packaging carry partial completion data and status flags that vary between plants. Dolibarr's Project status set differs from IS Packaging's lifecycle. We either quiesce open orders before migration (recommend) or build a status mapping matrix that maps IS Packaging statuses to Dolibarr Project statuses during import. Orders imported without mapping may default to closed or sit in an invalid state, blocking downstream BOM lookups.

Migration approach

Six steps for a successful IS Packaging to Dolibarr ERP data migration

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

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

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

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

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

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

Context on both ends of the pair

IS Packaging logo

IS Packaging

Source

Strengths

  • Purpose-built for multi-plant packaging operations with BOM and routing support
  • Integrates production scheduling, inventory, and costing in one database
  • Supports revision control for BOMs used in regulated food and pharmaceutical packaging
  • Provides lot/serial traceability from raw materials through finished goods
  • Offers MRP pegging to tie customer demand to specific production orders

Weaknesses

  • Limited documented public API — no widely published REST or bulk export endpoints
  • Customizations and modifications vary significantly between customer implementations
  • Reporting and analytics capabilities are generally considered basic compared to tier-one ERPs
  • Support and documentation quality depends heavily on the specific VAR or internal IT team
  • No self-service cloud option known at time of research — implementations are typically on-premises or hosted
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 IS Packaging 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

    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

    A

    IS Packaging exposes a bulk API — large-volume migrations stream efficiently.

Estimator

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

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

Can't find your answer?

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 consultation

Straightforward migrations under 5,000 Items, 500 BOMs, and a single plant land between four and six weeks. Migrations with multi-plant consolidation (more than three plants), more than 1,000 BOM revisions, or large inventory transaction histories move to ten to fourteen weeks because of lot normalization, BOM revision reconciliation, and data validation. The biggest variable is whether IS Packaging database access is available directly or requires VAR-mediated export.

Adjacent paths

Related migrations to explore

Ready when you are

Move from IS Packaging.
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