Migrate your IS Packaging data
Enterprise resource planning for packaging manufacturers and converters — managing materials, production orders, and inventory across multi-plant operations.
In its favor
Why people choose IS Packaging
The signal that keeps IS Packaging on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
IS Packaging is built on SAP S/4HANA as the core ERP foundation, giving flexible-packaging manufacturers an industry-preconfigured solution without standing up a bare S/4HANA implementation from scratch.
Aicomp's preconfigured product configurator handles film, tube, composite, bag, stand-up pouch, and bottom-fold variants with feasibility checks built into the input masks, reducing the manual product-master setup typical of generic ERPs.
Variant costing accounts for parameters like colour, adhesive, varnish, zipper, sealing, plus production services (printing, laminating, embossing, sterilising, perforating, folding) so quote-to-order pricing matches actual production cost.
Recipe management with compound tracking across extrusion, lamination, printing, and converting steps suits regulated food and pharmaceutical packaging workflows where revision history and traceability are mandatory.
Aicomp Connect provides standardised interfaces back into the SAP ecosystem, so customers running other SAP modules (FI/CO, MM, PP) inherit native integration rather than building point connectors.
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.
Reasons to switch
Why people leave IS Packaging
The recurring reasons buyers give for replacing IS Packaging. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where IS Packaging fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
IS Packaging pricing overview
IS Packaging by Aicomp does not publish pricing publicly. Total cost depends on SAP S/4HANA licensing, the deployment model (on-premises, private cloud, or SAP RISE), the number of users and plants, and the scope of Aicomp implementation services. Prospective customers contact Aicomp directly (US +1 888 878 8575 or EU +49 7128 304050) for a tailored quote. No free trial or self-service tier is offered.
Custom (sales-led)
Tier 1 of 1
Custom — quote-based on SAP licensing, plants, users, and implementation scope
What's included
Need help selecting your ERP?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on IS Packaging's schedule — see our quote-based pricing →
What gets migrated
IS Packaging object support
Object-by-object support for IS Packaging migrations. Per-pair details surface during scoping.
Items
Fully supportedItems are the core product masters in IS Packaging, holding item numbers, descriptions, uom, category, and costing layers. We extract all standard fields and custom properties at migration time.
Bill of Materials (BOMs)
Fully supportedBOMs are revision-controlled recipes linking parent Items to component Items with quantities. We preserve every BOM revision, routing steps, and phantom assembly flag.
Production Orders
Fully supportedProduction Orders link BOMs to scheduled quantities, plant, and work center. We migrate open and history Production Orders and preserve their status and completion percentages.
Work Orders
Mapping requiredWork Orders are tied to Production Orders and carry scheduling, labor, and machine time. Status flags vary between plants so we apply destination-status mapping during import.
Finished Goods Locations
Fully supportedFinished Goods are stored at Location records tied to Items with lot/serial tracking. We preserve location assignments and on-hand quantities across source and destination.
Inventory Transactions
Mapping requiredTransaction history includes receipts, issues, and adjustments. Large transaction volumes require chunked extraction and sequencing to preserve chronological integrity.
Customer Orders
Mapping requiredOpen Customer Orders reference Items and pricing rules. We map order headers and line items, flagging any pricing exceptions for manual review before import.
Vendor Records
Fully supportedVendor masters include contact info, terms, and item-supplier cross-references. We extract and reassociate vendor-to-item links at migration time.
Custom Fields
Mapping requiredCustom fields added to standard objects require field-level mapping. We inventory all custom field names, types, and values during the discovery phase before import.
Chart of Accounts
Mapping requiredThe accounting structure may differ between IS Packaging instances. We map account codes to destination segments and flag any inactive or intercompany accounts that need reactivation.
| Object | Support | Notes |
|---|---|---|
| Items | Fully supported | Items are the core product masters in IS Packaging, holding item numbers, descriptions, uom, category, and costing layers. We extract all standard fields and custom properties at migration time. |
| Bill of Materials (BOMs) | Fully supported | BOMs are revision-controlled recipes linking parent Items to component Items with quantities. We preserve every BOM revision, routing steps, and phantom assembly flag. |
| Production Orders | Fully supported | Production Orders link BOMs to scheduled quantities, plant, and work center. We migrate open and history Production Orders and preserve their status and completion percentages. |
| Work Orders | Mapping required | Work Orders are tied to Production Orders and carry scheduling, labor, and machine time. Status flags vary between plants so we apply destination-status mapping during import. |
| Finished Goods Locations | Fully supported | Finished Goods are stored at Location records tied to Items with lot/serial tracking. We preserve location assignments and on-hand quantities across source and destination. |
| Inventory Transactions | Mapping required | Transaction history includes receipts, issues, and adjustments. Large transaction volumes require chunked extraction and sequencing to preserve chronological integrity. |
| Customer Orders | Mapping required | Open Customer Orders reference Items and pricing rules. We map order headers and line items, flagging any pricing exceptions for manual review before import. |
| Vendor Records | Fully supported | Vendor masters include contact info, terms, and item-supplier cross-references. We extract and reassociate vendor-to-item links at migration time. |
| Custom Fields | Mapping required | Custom fields added to standard objects require field-level mapping. We inventory all custom field names, types, and values during the discovery phase before import. |
| Chart of Accounts | Mapping required | The accounting structure may differ between IS Packaging instances. We map account codes to destination segments and flag any inactive or intercompany accounts that need reactivation. |
Gotchas
What to watch for in IS Packaging migrations
Issues we've hit on past IS Packaging migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
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
| Severity | Issue |
|---|---|
| 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 |
Leaving IS Packaging?
Where IS Packaging customers move next
6 destinations IS Packaging can migrate to.
How a IS Packaging migration works
Four steps, IS Packaging-specific
Connect
Not publicly documented — typically inherits SAP S/4HANA authentication (OAuth 2.0, SAML, or SAP-issued credentials) via Aicomp Connect. into IS Packaging. Scopes limited to read-only on the data we move.
Map
We translate IS Packaging-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate IS Packaging quirks before production.
Migrate
Full migration with IS Packaging rate-limit handling. Rollback available throughout.
FAQ
IS Packaging migration FAQ
Answers to the questions buyers ask most during IS Packaging migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your IS Packaging migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate IS Packaging.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your IS Packaging setup and destination — written quote back within a business day.