ERP migration

Migrate from IS Packaging to Acumatica

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

IS Packaging logo

IS Packaging

Source

Acumatica

Destination

Acumatica logo

Compatibility

100%

13 of 13

objects map 1:1 between IS Packaging and Acumatica.

Complexity

BStandard

Timeline

7–10 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Acumatica logo

Acumatica

What's pulling them in

  • Unlimited user licensing lets companies add staff without per-seat billing shocks, making Acumatica cost-predictable at scale.
  • Flexibility and scalability earn consistent praise — users value a platform that adapts to vertical workflows without forcing a redesign.
  • Real-time visibility across financials, inventory, and projects gives mid-market businesses a consolidated operational view previously available only in enterprise-tier ERPs.
  • Cloud-native architecture with automatic updates removes infrastructure management burden from in-house IT teams.
  • Modular licensing lets companies start with one or two suites (Financials, Distribution) and expand into Manufacturing or CRM incrementally.

Object mapping

How IS Packaging objects map to Acumatica

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

maps to

Acumatica

Business Account (Customers)

1:1
Fully supported

IS 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

maps to

Acumatica

Business Account (Vendors)

1:1
Fully supported

IS 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

maps to

Acumatica

Non-Stock Item / Stock Item

1:1
Fully supported

IS 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

maps to

Acumatica

Bill of Materials

1:1
Fully supported

IS 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

maps to

Acumatica

Production Order

1:1
Fully supported

IS 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

maps to

Acumatica

Sales Order

1:1
Fully supported

IS 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

maps to

Acumatica

Purchase Order

1:1
Fully supported

IS 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

maps to

Acumatica

AR Invoice / Credit Memo

1:1
Fully supported

IS 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

maps to

Acumatica

AP Invoice / Credit Memo

1:1
Fully supported

IS 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

maps to

Acumatica

Journal Transaction

1:1
Fully supported

IS 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

maps to

Acumatica

Custom Fields (DAC Extension)

1:1
Fully supported

IS 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

maps to

Acumatica

Cash Discount / Payment Term

1:1
Fully supported

IS 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

maps to

Acumatica

Warehouse / Location

1:1
Fully supported

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

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

Acumatica logo

Acumatica gotchas

High

API user licenses cap concurrent sessions and request throughput

High

Multi-tenant filtering requires CompanyID awareness

Medium

Custom fields require separate discovery before field mapping

Medium

Notes and attachments use a separate linked table structure

Low

Implementation timelines frequently run 3–9 months end-to-end

Pair-specific challenges

  • Acumatica Customization Project lifecycle requires careful sequencing

    Acumatica custom fields live inside a Customization Project. When you publish a field for the first time, Acumatica adds it to the DAC and creates the SQL column simultaneously. If you unpublish a field later, it disappears from the UI but the SQL column remains with its data intact. Migrating IS Packaging custom fields (lot compliance codes, material certifications, customer-specific pricing tiers) requires creating and publishing the Customization Project in Acumatica before data loads begin—otherwise import validation fails on unknown field names. We deliver the Customization Project XML package for your Acumatica admin to publish before migration runs.

  • Import by Scenario enforces rigid validation—source data must be pre-cleaned

    Acumatica's Import by Scenario (SM156025) validates incoming data against required fields, pick-list values, and foreign key relationships at import time. IS Packaging records with missing required fields, invalid date formats, or orphaned foreign keys (customer IDs that don't exist yet) will reject during import. The migration plan must sequence imports so parent records (customers, vendors, inventory) load before child records (orders, invoices), and we run data profiling on the IS Packaging export to surface blanks, duplicates, and invalid codes before any Acumatica import executes. Without pre-cleaning, Import by Scenario halts on the first error batch.

  • Multi-currency setup must exist before AP/AR import if source uses foreign currencies

    If IS Packaging stores AP or AR balances in currencies other than the base currency, Acumatica requires the Currency (CM202010) and Exchange Rate (CM301000) records to exist before invoice import. Acumatica's multi-currency module processes each document with the exchange rate effective on the document date—if no rate exists, the import fails validation. Historical rates from IS Packaging must be entered into Acumatica's rate table (CM202010) before AP/AR migration batches run. The migration plan includes a rate-backfill step using the IS Packaging currency and date combination.

  • Generic Inquiries replace standard IS Packaging list views—reporting rebuild required

    IS Packaging list views and standard reports have no direct Acumatica equivalent. Acumatica ships with standard reports for Financials, Distribution, and Inventory, but any custom IS Packaging reports built by users require Generic Inquiry (GI) construction in Acumatica—a SQL-like query builder against the DAC layer. The data itself migrates correctly, but the saved views and filters your team has built in IS Packaging do not. We document each IS Packaging report's filter criteria and field selection so your Acumatica admin can rebuild them as GIs. This typically takes 1–3 hours per report depending on complexity.

  • Support escalates through VAR—VAR rates apply from ticket submission

    Acumatica does not offer direct end-user support tickets. All support requests route through your Value-Added Reseller (VAR), and VAR engagement time—including the time spent submitting and discussing a ticket—typically starts billing immediately at contracted rates ($150–$300/hour). This differs from IS Packaging's support model where initial triage may be included. We document all migration validation issues in a self-service report format to minimize VAR engagement hours, but post-migration configuration questions that require Acumatica-specific knowledge will incur VAR time. Budget accordingly for the first 30–60 days post-migration.

Migration approach

Six steps for a successful IS Packaging to Acumatica data migration

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

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

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

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

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

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
Acumatica logo

Acumatica

Destination

Strengths

  • Unlimited named-user licensing eliminates per-seat cost scaling as teams grow.
  • Modular architecture lets companies deploy Financials first and add Distribution, Manufacturing, or CRM incrementally.
  • Cloud-native with automatic updates removes infrastructure patching and version management from IT responsibilities.
  • Flexible customization framework (UDFs, extensions) supports vertical-specific workflows without forking core code.
  • Multi-tenant architecture with CompanyID isolation enables safe data segregation across subsidiaries.

Weaknesses

  • Steep learning curve and complex initial setup create significant onboarding friction.
  • Report Designer is widely cited as unintuitive and difficult to use for non-developers.
  • Feature gaps require customizations or third-party add-ons, adding implementation cost and complexity.
  • Implementation timelines frequently exceed initial estimates, especially for multi-module deployments.
  • API rate limits and concurrent session caps are tied to license tier, creating throughput constraints for bulk data operations.

Complexity grading

How hard is this migration?

Standard ERP migration. 2 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 Acumatica.

  • Object compatibility

    B

    2 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 Acumatica 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 Acumatica data migrations

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

Can't find your answer?

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 consultation

Most IS Packaging to Acumatica migrations complete in 7–10 business days of active migration work for standard datasets under 25,000 records. Larger setups with over 100,000 records, multi-entity configurations, or significant custom field coverage extend to 3–5 weeks. The longest phase is typically the Acumatica setup and Customization Project publishing before data loading begins—Acumatica requires its schema to be in place before Import by Scenario validation runs. Data cleansing time, driven by the quality of IS Packaging exports, also factors significantly into the timeline.

Adjacent paths

Related migrations to explore

Ready when you are

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