ERP migration

Migrate from IS Packaging to Odoo ERP

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

IS Packaging logo

IS Packaging

Source

Odoo ERP

Destination

Odoo ERP logo

Compatibility

90%

9 of 10

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

Complexity

BStandard

Timeline

4-8 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from IS Packaging to Odoo ERP is a manufacturing data migration with several domain-specific challenges: BOM revision control must map to Odoo's product variants and BOM version scheme, open Production Orders must be quiesced or status-mapped to Odoo's MO state machine, and multi-plant lot numbering conventions must be normalized during import. IS Packaging has no widely documented public REST or bulk export API, so data extraction relies on direct database queries or CSV exports provided by the customer. We sequence the migration by dependency: Items and Locations first (no dependencies), then BOMs (lookup to Items), then Production Orders (lookup to BOMs and Locations), then Customer Orders and Vendor records (independent), then Inventory Transactions last (lookups to all preceding objects). We do not migrate IS Packaging Workflows, automations, or custom reports; we deliver a written inventory of these for the customer's Odoo administrator to rebuild using Odoo Studio or a certified partner.

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

Odoo ERP logo

Odoo ERP

What's pulling them in

  • Modular pay-as-you-grow model with 80+ apps under one database — teams start with CRM and add Accounting, Inventory, or Manufacturing without switching platforms.
  • Free Community edition lets businesses validate Odoo fit before committing to Enterprise licensing costs that scale with user count.
  • Lowest per-user pricing among mid-market ERPs, with a published free tier for one app and Standard plans starting around $24.90 per user per month.
  • Native integration between modules — a confirmed Sales Order automatically updates inventory, invoicing, and accounting without manual re-entry.
  • Strong Odoo Gold Partner ecosystem provides local implementation support, reducing risk for companies without in-house developers.

Object mapping

How IS Packaging objects map to Odoo ERP

Each row shows how a IS Packaging object lands in Odoo 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

Odoo ERP

Product (product.product)

1:1
Fully supported

IS Packaging Items map to Odoo product.product records. Item number becomes default_code (the SKU field), description maps to name, uom maps to Odoo uom_id (with uom_category mapping for unit conversions), and costing layers map to Odoo's standard cost, average cost, or fifo depending on the costing method configured in the destination. Custom fields on Items are inventoried during discovery and created as custom product attributes or ir.property values before import.

IS Packaging

Bill of Materials (BOMs)

maps to

Odoo ERP

Bill of Materials (mrp.bom)

1:1
Fully supported

IS Packaging BOMs map to Odoo mrp.bom records with bom_line entries for each component. Phantom assembly flags from IS Packaging map to Odoo's phantom BoM type on mrp.bom. Routing steps (work center sequences) map to Odoo mrp.workcenter and mrp.routing.WorkcenterLine records. BOM revision cross-referencing is the critical step: IS Packaging BOM revisions are matched to Odoo product variants or Odoo's engineering version field during import. We build a revision cross-reference table during discovery that maps each source BOM revision ID to the destination product variant or bom_line set.

IS Packaging

Production Orders

maps to

Odoo ERP

Manufacturing Order (mrp.production)

1:1
Fully supported

IS Packaging Production Orders map to Odoo mrp.production. The source BOM reference resolves to the destination mrp.bom ID at migration time. Production order status mapping is required: IS Packaging plant-specific statuses (e.g., released, in-progress, partially complete) map to Odoo's confirmed, in_progress, and done states via a status matrix built during discovery. Open Production Orders with partial completion percentages are migrated as mrp.production records with the qty_producing field set to the partial completion value and product_qty adjusted to the remaining quantity.

IS Packaging

Work Orders

maps to

Odoo ERP

Work Order (mrp.workorder)

1:1
Mapping required

IS Packaging Work Orders tied to Production Orders map to Odoo mrp.workorder records linked to the parent mrp.production. Scheduling timestamps, work center assignment, and labor hours migrate to Odoo's duration fields. If IS Packaging uses different work center naming conventions per plant, we normalize work center names across the migration into a unified Odoo mrp.workcenter setup before Work Orders are imported.

IS Packaging

Finished Goods Locations

maps to

Odoo ERP

Stock Location (stock.location)

1:1
Fully supported

IS Packaging Finished Goods Locations map to Odoo stock.location records under the 'Stock' location type. Lot/serial numbers stored at the location level migrate as stock.lot records with product_id linked to the destination product and location_id set to the destination stock.location. On-hand quantities from the location record migrate as stock.quant records at import time.

IS Packaging

Inventory Transactions

maps to

Odoo ERP

Stock Move (stock.move)

1:1
Mapping required

IS Packaging inventory transaction history (receipts, issues, adjustments) maps to Odoo stock.move records. Large transaction volumes require chunked extraction sequenced chronologically to preserve the inventory ledger integrity. We chunk transactions by date range and plant, resolve product_id and location_id references for each batch, and use Odoo's stock.move creation API in batches to avoid timeouts. Adjustment transactions map to stock.valuation record equivalents.

IS Packaging

Customer Orders

maps to

Odoo ERP

Sale Order (sale.order + sale.order.line)

1:1
Mapping required

IS Packaging Customer Orders map to Odoo sale.order with line items on sale.order.line. Order headers carry customer reference, terms, and pricing rules; lines carry item, quantity, and pricing. Any custom pricing rules or exceptions in IS Packaging are flagged for manual review before import. Open orders migrate with their current fulfillment status; historical orders migrate with a state of 'done' or 'sale' to prevent unintended workflow actions.

IS Packaging

Vendor Records

maps to

Odoo ERP

Contact (res.partner with supplier = True)

1:1
Fully supported

IS Packaging Vendor masters map to Odoo res.partner records with the supplier flag set. Contact info, payment terms, and item-supplier cross-references migrate as vendor-related fields on the partner record. Item-supplier cross-references (preferred vendors per item) migrate to product.supplierinfo records linked to the product.product and res.partner vendor.

IS Packaging

Chart of Accounts

maps to

Odoo ERP

Account (account.account)

1:1
Mapping required

IS Packaging Chart of Accounts maps to Odoo account.account. Account codes and names migrate directly. Account type mapping (asset, liability, equity, revenue, expense) follows Odoo's account.account type taxonomy. Any inactive or intercompany accounts from IS Packaging are flagged in the mapping document for the customer's admin to reactivate or consolidate before import. We do not migrate IS Packaging journal entries; only the account structure is migrated, and beginning balances are set manually by the customer's accountant post-migration.

IS Packaging

Custom Fields

maps to

Odoo ERP

Custom Fields / ir.property

lossy
Mapping required

Custom fields added to standard IS Packaging objects (Items, BOMs, Production Orders) are inventoried during discovery with their data types and current values. We pre-create the equivalent Odoo custom fields using Odoo Studio or direct XML data migration before the main import phase. Custom field values are then mapped and imported as part of each object's migration batch. The customer chooses during scoping whether custom fields become native Odoo fields (using Studio) or ir.property override records.

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

Odoo ERP logo

Odoo ERP gotchas

High

No rollback for CSV imports

High

External ID conflicts on re-import

Medium

Many2many field encoding in CSV imports

Medium

Large export timeouts require batching

Medium

Version schema drift between Odoo releases

Pair-specific challenges

  • IS Packaging has no documented public REST or bulk export API

    IS Packaging does not have a widely published REST or bulk export endpoint, which is a structural limitation of the platform rather than a pair-specific feature. Data extraction relies on direct database queries executed by the customer's IS Packaging administrator or VAR, or on CSV exports available within the application. We coordinate with the customer's IT team to produce clean, complete data dumps. We do not build a scraping layer or reverse-engineer undocumented endpoints. The customer must provide export access or VAR support before migration scoping begins.

  • BOM revisions must map to Odoo product variants or BOM versions exactly

    IS Packaging tracks BOM revisions with effective dates. Odoo uses product variants (configurable products with attribute values) and a BOM version field for engineering revision control. If the source implementation uses multiple active BOM revisions simultaneously for different plants or customer specifications, we must map each source BOM revision to a distinct Odoo product variant or mrp.bom engineering revision. We build a revision cross-reference table during discovery and validate it against open Production Orders before import. Mismatched BOM revisions cause material allocation errors on Manufacturing Orders.

  • Open Production Orders require status lifecycle resolution before import

    Active Production Orders in IS Packaging carry partial completion data and plant-specific statuses that do not map directly to Odoo's mrp.production state machine. We either quiesce open orders in IS Packaging before migration (closing or completing them as a pre-migration step) or build a status mapping matrix that translates source statuses to Odoo confirmed or in_progress states with the qty_producing field set to the current completion quantity. Orders imported without this step default to a state that blocks MO operations in Odoo.

  • Lot and serial number formats differ between plants and must be normalized

    Packaging companies running IS Packaging often use different lot-numbering conventions per plant: date-coded, supplier-prefixed, or sequence-based formats coexist within the same company. Odoo uses a single stock.lot model with product_id and name fields. During multi-plant migration, we normalize lot identifiers into a unified format and re-associate all lot transactions to prevent orphaned traceability records. The normalized format is defined during discovery based on the customer's regulatory and customer requirements.

  • Data quality issues discovered during extraction delay migration timelines

    IS Packaging implementations frequently contain duplicate Items, Items without uom assignments, BOMs with invalid component references, and Customer Orders with missing pricing rules. These are not pair-specific gotchas but are encountered in nearly every legacy system migration. We include a data audit phase that identifies quality issues before import begins, allowing the customer to clean records in IS Packaging before migration. Migrations that skip or shorten this phase consistently encounter import rejections and reconciliation rework that extends timelines by two to four weeks.

Migration approach

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

  1. Discovery and data audit

    We work with the customer's IS Packaging administrator and VAR to enumerate all plants, objects, and data volumes. We produce a data inventory covering Items by category, BOM revision counts, open and historical Production Order counts per plant, Finished Goods location counts, inventory transaction volume, Customer Order and Vendor record counts, and custom field definitions. We also assess data quality: duplicate items, orphaned BOM components, missing uom assignments, and open Production Order status. The discovery output is a written migration scope, a data audit report, and a BOM revision cross-reference template for the customer to populate.

  2. BOM revision design and Odoo schema preparation

    We design the Odoo BOM structure to accommodate source BOM revisions. This may involve configuring Odoo product variants with attribute values representing the revision code (e.g., revision date or sequential number), or using Odoo's engineering revision field on mrp.bom if available in the destination version. We also configure stock.locations (one per source plant), work centers (mapped from IS Packaging work centers), and the product.uom category mapping for any non-standard units of measure in use. The Odoo schema is deployed into a staging environment first.

  3. Data extraction and cleaning

    The customer or VAR provides CSV exports or direct database query results from IS Packaging. We validate record counts against the discovery inventory, identify and flag records with quality issues (duplicates, missing foreign keys, invalid uom values), and return a cleaning checklist. The customer's IS Packaging team resolves data quality issues before we proceed to import. We do not import dirty data; uncleaned data causes import failures that require retroactive reconciliation.

  4. Staging migration and reconciliation

    We run a full migration into an Odoo staging environment using production-like data volumes. The customer's operations manager reconciles record counts (Items in vs. products created, BOMs in vs. mrp.bom records, Production Orders in vs. mrp.production records, locations in vs. stock.location records), spot-checks 25-50 records per object against the source data, and validates BOM revision assignments against open Production Orders. Any mapping corrections are documented and validated before production migration begins.

  5. Production migration in dependency order

    We run production migration in this order: (1) Products and UOM categories (no dependencies), (2) Stock Locations (no dependencies), (3) Work Centers (no dependencies), (4) Bill of Materials (lookup to Products), (5) Vendor Contacts and product.supplierinfo (lookup to Vendors and Products), (6) Customer Contacts (no dependencies), (7) Sale Orders (lookup to Customers), (8) Manufacturing Orders with Work Orders (lookup to BOMs, Locations, and Work Centers), (9) Stock Quants and lot/serial records (lookup to Products and Locations), (10) Stock Moves (lookups to Products, Locations, and lots). Each phase emits a row-count reconciliation report before the next begins.

  6. Cutover, lot normalization validation, and BOM rebuild handoff

    We freeze writes in IS Packaging during cutover, run a final delta migration of any records modified during the migration window, then set Odoo ERP as the system of record. Lot/serial normalization is validated against a sample of traceability records. We deliver a written inventory of any IS Packaging custom fields that could not be migrated as native Odoo fields and require Studio configuration or ir.property setup. We do not rebuild IS Packaging automations or custom reports; that inventory is handed to the customer's Odoo administrator or certified Odoo partner. We support a one-week hypercare window for reconciliation issues.

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
Odoo ERP logo

Odoo ERP

Destination

Strengths

  • Modular architecture with 80+ apps sharing one database — add Sales, Accounting, Inventory, and Manufacturing incrementally.
  • Free Community edition for self-hosting with no per-user license cost, backed by an active open-source community.
  • Per-user pricing starting around $24.90/month on Standard, significantly lower than comparable ERPs like NetSuite or SAP.
  • Automatic workflow propagation across modules — a confirmed sales order updates inventory, triggers invoicing, and posts accounting entries without manual steps.
  • Odoo.sh provides a managed cloud hosting environment with CI/CD for custom module deployment and staging databases.

Weaknesses

  • Performance suffers under heavy customization — large implementations with many active modules require dedicated optimization.
  • No single-click migration between Odoo major versions; each release introduces ORM changes, deprecated API calls, and schema revisions requiring manual adaptation.
  • Per-user and per-module licensing costs can escalate unpredictably for growing teams adding multiple apps.
  • Steep learning curve with hundreds of configuration options across dozens of modules creates adoption friction and training requirements.
  • Support tiers on Enterprise have inconsistent response times, pushing some customers toward alternatives with more reliable SLAs.

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 Odoo 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 Odoo 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 Odoo ERP data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Single-plant migrations with clean Items, BOMs, and minimal open Production Orders typically complete in four to eight weeks. Multi-plant migrations with inconsistent lot-numbering conventions, active open Production Orders requiring status mapping, large inventory transaction histories, or extensive custom fields move to twelve to sixteen weeks. The data audit and cleaning phase is the primary timeline variable; organizations that begin data preparation during discovery consistently hit their target go-live dates.

Adjacent paths

Related migrations to explore

Ready when you are

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