ERP migration
Field-level mapping, validation, and rollback between IS Packaging and Acumatica. We move data and schema; workflows are rebuilt natively in Acumatica.
IS Packaging
Source
Acumatica
Destination
Compatibility
13 of 13
objects map 1:1 between IS Packaging and Acumatica.
Complexity
BStandard
Timeline
7–10 days
Overview
IS Packaging typically stores operational data across customer management, inventory control, production scheduling, and financial modules—often with custom fields tracking lot numbers, compliance data, or customer-specific pricing. Acumatica organizes data into separate branches for Customers, Vendors, Inventory, Projects, and Financials, using a multi-entity structure that requires careful mapping of source company data to one or more Acumatica tenant configurations. The migration carries all standard objects (contacts, addresses, inventory items, stock items, non-stock items, work orders, purchase orders, sales orders, and AR/AP transactions) into Acumatica's corresponding tables. Non-standard fields—lot tracking codes, compliance flags, or customer-specific discount tiers—migrate as custom fields on the appropriate DAC (Data Access Class) objects. Acumatica's Import by Scenario mechanism handles bulk data loading, but complex transformations (currency conversions, multi-branch splits) require pre-processing. Workflows, approval chains, and notification rules do not migrate and must be rebuilt in Acumatica's Business Events and Generic Inquiry framework. The extraction mechanism uses IS Packaging's export capabilities or API calls, transformed into Acumatica's import format with field-by-field validation before commit.
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 Acumatica, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
IS Packaging
Customer / Contact
Acumatica
Business Account (Customers)
1:1IS Packaging customer records (name, address, phone, email, payment terms) map to Acumatica Business Account with Customer class. Primary contact details map to the primary Contact sub-record. Multiple contacts per account supported via the Contacts tab. Secondary addresses such as ship-to locations map to separate Address records linked to the Business Account, enabling customers with multiple delivery points to maintain all locations under a single account hierarchy.
IS Packaging
Vendor / Supplier
Acumatica
Business Account (Vendors)
1:1IS Packaging vendor records map to Acumatica Business Account with Vendor class. Payment terms, tax ID, and remit-to addresses migrate as vendor-specific attributes. PO defaults and expense categories map to Acumatica's vendor record settings. Remittance addresses and 1099 reporting flags transfer to ensure tax compliance in Acumatica, while multiple payment destinations per vendor are supported through the Remit-to Address feature.
IS Packaging
Inventory Item / Stock Item
Acumatica
Non-Stock Item / Stock Item
1:1IS Packaging inventory items (item code, description, unit of measure, cost, price) map to Acumatica Inventory ID records. Item type (stock vs. non-stock) determines whether Acumatica uses Stock Item or Non-Stock Item DAC. Lot/serial tracking settings map to Acumatica's lot/serial classes.
IS Packaging
Bill of Materials / Recipe
Acumatica
Bill of Materials
1:1IS Packaging BOM records (component items, quantities, operation steps) map to Acumatica BOM records linked to the finished good inventory item. Material issues and overhead rates map to the cost element breakdown in Acumatica's BOM version. Multi-level BOM structures with subassemblies transfer as nested BOM hierarchies, and alternative BOMs for the same finished good are supported through BOM versions with effective date ranges.
IS Packaging
Work Order / Production Order
Acumatica
Production Order
1:1IS Packaging work orders (date, quantity, BOM link, status, labor hours) map to Acumatica Production Order records. Original creation dates preserved as reference dates. Labor and machine time entries migrate as production transaction logs linked to the production order. Material shortage flags and work order priorities transfer as custom fields, and if IS Packaging tracks step-level scheduling, those operations map to production order operations with labor and machine center assignments.
IS Packaging
Sales Order
Acumatica
Sales Order
1:1IS Packaging sales orders (customer, lines, quantities, prices, warehouse, status) map to Acumatica SO301000 screen records. Order dates, promised dates, and customer PO references migrate. Open orders migrate with their current status; completed orders migrate as historical records. Drop-ship and special fulfillment instructions map to the fulfillment settings on each sales order line, and any promotional pricing or volume discounts linked to the order transfer as line-level adjustments.
IS Packaging
Purchase Order
Acumatica
Purchase Order
1:1IS Packaging purchase orders map to Acumatica PO301000 records. Vendor, line items, quantities, costs, and expected delivery dates transfer. Drop-ship and fulfillment settings map where applicable. Open POs retain status; received POs migrate with receipt history. Pre-assigned warehouse and location assignments on PO lines transfer to ensure ordered materials route to the correct receiving departments, and blanket PO release history maps to linked release records under the blanket agreement.
IS Packaging
AR Invoice / AR Credit Memo
Acumatica
AR Invoice / Credit Memo
1:1IS Packaging AR invoices map to Acumatica AR301000 records. Invoice number, date, due date, customer, lines, tax, and amount transfer. Payments applied before migration date are recorded as applied. Open invoices remain open in Acumatica AR. Credit memo applications and overpayment allocations transfer as applied documents, and any finance charges or adjustment reasons linked to invoices migrate as document-level notes for audit trail purposes.
IS Packaging
AP Invoice / AP Credit Memo
Acumatica
AP Invoice / Credit Memo
1:1IS Packaging AP invoices map to Acumatica AP301000 records. Vendor invoice number, date, due date, vendor, lines, and amount transfer. Prepaid and hold statuses map to Acumatica's invoice hold workflow. Open AP balances carry forward. Recurring invoice schedules and approval routing assignments transfer to Acumatica's invoice workflows, and any pre-payment application references map to payment applications against the AP invoice.
IS Packaging
GL Journal Entry
Acumatica
Journal Transaction
1:1IS Packaging journal entries map to Acumatica GL301000 records with account, debit/credit amount, and description. Source module (AR, AP, IN) tags as the batch reference. Period and financial year assignments map to Acumatica's fiscal period structure. Recurring journal templates and reversing batch settings transfer to GL batch headers, and any consolidated journal entry flags for inter-company transactions map to Acumatica's inter-company journal entry handling.
IS Packaging
Custom Fields / User-Defined Data
Acumatica
Custom Fields (DAC Extension)
1:1IS Packaging custom fields (lot compliance codes, customer pricing tiers, material certifications) require Acumatica Customization Project with DAC extensions. Each custom field is defined in the customization project, published to create SQL columns, then populated during migration. Field type mapping (text, number, date, picklist) aligns with Acumatica's PXDBField attribute definitions.
IS Packaging
Payment Terms
Acumatica
Cash Discount / Payment Term
1:1IS Packaging payment terms (Net 30, 2/10 Net 30, etc.) map to Acumatica Payment Terms (AR303010) with Cash Discount codes. Each term's description, due days, and discount days transfer. Custom payment terms require new term creation in Acumatica before mapping.
IS Packaging
Warehouse / Location
Acumatica
Warehouse / Location
1:1IS Packaging warehouse and bin locations map to Acumatica Warehouse (IN204000) and Location records. Address, contact, and default values transfer. Bin structures map to Acumatica's location numbering convention within each warehouse. Default receiving and shipping zones transfer to warehouse setup, and if IS Packaging tracks warehouse-specific inventory valuation methods, those settings map to the cost site assignments in Acumatica's inventory valuation configuration.
| IS Packaging | Acumatica | Compatibility | |
|---|---|---|---|
| Customer / Contact | Business Account (Customers)1:1 | Fully supported | |
| Vendor / Supplier | Business Account (Vendors)1:1 | Fully supported | |
| Inventory Item / Stock Item | Non-Stock Item / Stock Item1:1 | Fully supported | |
| Bill of Materials / Recipe | Bill of Materials1:1 | Fully supported | |
| Work Order / Production Order | Production Order1:1 | Fully supported | |
| Sales Order | Sales Order1:1 | Fully supported | |
| Purchase Order | Purchase Order1:1 | Fully supported | |
| AR Invoice / AR Credit Memo | AR Invoice / Credit Memo1:1 | Fully supported | |
| AP Invoice / AP Credit Memo | AP Invoice / Credit Memo1:1 | Fully supported | |
| GL Journal Entry | Journal Transaction1:1 | Fully supported | |
| Custom Fields / User-Defined Data | Custom Fields (DAC Extension)1:1 | Fully supported | |
| Payment Terms | Cash Discount / Payment Term1:1 | Fully supported | |
| Warehouse / Location | Warehouse / Location1: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
Acumatica gotchas
API user licenses cap concurrent sessions and request throughput
Multi-tenant filtering requires CompanyID awareness
Custom fields require separate discovery before field mapping
Notes and attachments use a separate linked table structure
Implementation timelines frequently run 3–9 months end-to-end
Pair-specific challenges
Migration approach
Assess IS Packaging data model and extraction points
We inventory all IS Packaging tables and export mechanisms available for your version and configuration. This includes identifying custom fields, module coverage (AR/AP/INV/PO/SO), open transaction counts, and historical volume. We profile the export for data quality issues (blanks, duplicates, orphaned references) and produce a cleansing specification. If IS Packaging exposes an API, we document rate limits and endpoints; if export is file-based, we assess format compatibility with Acumatica's Import by Scenario CSV/Excel input requirements. The output is a data assessment report and a sequenced extraction plan.
Configure Acumatica tenant and publish custom fields
Before any data lands, your Acumatica admin (or our team) creates the required setup: chart of accounts aligned with IS Packaging GL segments, customer and vendor classes, inventory item classes, payment terms, and currency/rate tables if multi-currency applies. For IS Packaging custom fields, we deliver a Customization Project package that defines DAC extensions for each custom field, with proper PXDBField type attributes. The Customization Project must be published in Acumatica before the import steps run—this creates the SQL columns that Import by Scenario expects to find. We verify the published schema against the extraction plan field list before proceeding.
Sequence and execute trial migration with field-level diff
We load data in dependency order: first accounts (customers, vendors, inventory items) since they are referenced by transactions; then open purchase orders and sales orders; then AP and AR invoices; then completed transactions and journal entries. For each import group, we run a sample batch (typically 50–200 records) through Import by Scenario and generate a field-level diff between the source export and the Acumatica record. You review the diff to verify field mapping correctness, pick-list value handling, and data formatting. We iterate mapping adjustments until the sample diff passes your sign-off before committing the full batch.
Cut over with delta pickup and parallel running
After full migration validation, you run both systems in parallel for a window we agree on (typically 3–7 days for ERP, longer if open orders and partially-received POs require live coordination). During this window, any new transactions created in IS Packaging are captured by a delta extraction and loaded into Acumatica before final cutover. We monitor import logs for errors during parallel running and apply corrections. Audit logs capture every import batch operation. Once you confirm Acumatica reflects the current state, you designate a cutover date. A final delta run captures the gap between last import and cutover time.
Validate record counts, balances, and rebuild reporting
Post-cutover, we generate a reconciliation report comparing IS Packaging closing balances and record counts against Acumatica. This covers AR/AP aging, inventory quantities by location, open PO/SO backlogs, and GL trial balance by segment. Any discrepancies trigger a targeted re-import of affected records. Once balances reconcile, we hand off a Generic Inquiry rebuild guide documenting each IS Packaging report's equivalent in Acumatica's GI builder, with the original filter logic preserved as reference. This hands your team a self-service path to rebuilding saved views without VAR engagement.
Platform deep dives
IS Packaging
Source
Strengths
Weaknesses
Acumatica
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 2 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 Acumatica.
Object compatibility
2 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 Acumatica migration scoping. Not seeing yours? Book a call.
Walk through your IS Packaging to Acumatica 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 Acumatica
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.