ERP migration
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
Source
Odoo ERP
Destination
Compatibility
9 of 10
objects map 1:1 between IS Packaging and Odoo ERP.
Complexity
BStandard
Timeline
4-8 weeks
Overview
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.
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 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
Odoo ERP
Product (product.product)
1:1IS 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)
Odoo ERP
Bill of Materials (mrp.bom)
1:1IS 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
Odoo ERP
Manufacturing Order (mrp.production)
1:1IS 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
Odoo ERP
Work Order (mrp.workorder)
1:1IS 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
Odoo ERP
Stock Location (stock.location)
1:1IS 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
Odoo ERP
Stock Move (stock.move)
1:1IS 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
Odoo ERP
Sale Order (sale.order + sale.order.line)
1:1IS 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
Odoo ERP
Contact (res.partner with supplier = True)
1:1IS 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
Odoo ERP
Account (account.account)
1:1IS 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
Odoo ERP
Custom Fields / ir.property
lossyCustom 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.
| IS Packaging | Odoo ERP | Compatibility | |
|---|---|---|---|
| Items | Product (product.product)1:1 | Fully supported | |
| Bill of Materials (BOMs) | Bill of Materials (mrp.bom)1:1 | Fully supported | |
| Production Orders | Manufacturing Order (mrp.production)1:1 | Fully supported | |
| Work Orders | Work Order (mrp.workorder)1:1 | Mapping required | |
| Finished Goods Locations | Stock Location (stock.location)1:1 | Fully supported | |
| Inventory Transactions | Stock Move (stock.move)1:1 | Mapping required | |
| Customer Orders | Sale Order (sale.order + sale.order.line)1:1 | Mapping required | |
| Vendor Records | Contact (res.partner with supplier = True)1:1 | Fully supported | |
| Chart of Accounts | Account (account.account)1:1 | Mapping required | |
| Custom Fields | Custom Fields / ir.propertylossy | Mapping required |
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
Odoo ERP gotchas
No rollback for CSV imports
External ID conflicts on re-import
Many2many field encoding in CSV imports
Large export timeouts require batching
Version schema drift between Odoo releases
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
IS Packaging
Source
Strengths
Weaknesses
Odoo 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 Odoo 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 Odoo ERP migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave IS Packaging
Other ways to arrive at Odoo 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.