ERP migration
Field-level mapping, validation, and rollback between Icicle ERP and Acumatica. We move data and schema; workflows are rebuilt natively in Acumatica.
Icicle ERP
Source
Acumatica
Destination
Compatibility
12 of 12
objects map 1:1 between Icicle ERP and Acumatica.
Complexity
BStandard
Timeline
48–72 hours
Overview
Icicle ERP structures food manufacturing around recipes, production runs, and lot traceability — with separate modules for quality assurance, supplier management, and inventory that mirror food-safety workflows. Acumatica organizes data around Stock Items, Non-Stock Items, Bill of Materials, and Branch locations, with separate screens for Purchase Orders, Sales Orders, and Production Orders. The migration carries Icicle's product catalog, customer records, vendor records, open orders, and quality test history into Acumatica's corresponding entities. FlitStack sequences the load so foreign keys resolve correctly: vendors first, then customers, then inventory items, then open orders. Acumatica's Usr-prefix custom fields handle any Icicle-specific attributes that don't have native equivalents. Workflows, food-safety rules, and automation logic built in Icicle do not migrate — we export them as documentation for Acumatica configuration. During the migration, FlitStack runs a pre-flight check that creates Acumatica Lot/Serial classes, custom fields (Usr-prefix), and Branch structure before loading any data. The sequence ensures that each foreign key reference exists before it is used, preventing orphaned records. After the initial load, a delta-pickup window captures any new transactions created in Icicle while the cutover window is open, ensuring continuity of orders, production runs, and inventory movements. Once the data is in Acumatica, a field-level diff report allows you to verify that lot numbers, BOM revisions, and quality test results have transferred correctly. Any Icicle-specific attributes without native equivalents are stored in Usr-prefix fields, ready for further configuration.
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 Icicle ERP 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.
Icicle ERP
Product
Acumatica
Stock Item / Non-Stock Item
1:1Icicle products with bill of materials become Acumatica Stock Items. Products without BOM (ingredients sourced but not manufactured) become Non-Stock Items. Icicle's lot class assignment maps to Acumatica's Lot/Serial Class on the Stock Item. We preserve the original product ID as the Acumatica Inventory CD.
Icicle ERP
Recipe / Formula
Acumatica
Bill of Materials
1:1Icicle recipes map to Acumatica BOMs. The recipe's ingredients list becomes BOM lines with material type, quantity per, and unit of measure. Multi-level recipes (sub-assemblies) become nested BOM structures in Acumatica. We preserve the recipe version number as the BOM revision ID.
Icicle ERP
Customer
Acumatica
Customer
1:1Direct 1:1 map. Icicle customer fields (name, address, contact info, tax ID) map to the corresponding Acumatica Customer fields. Icicle's customer-specific pricing rules are preserved as customer price classes in Acumatica. Multi-ship-addresses become separate Customer Locations under one Customer record.
Icicle ERP
Vendor / Supplier
Acumatica
Vendor
1:1Direct map. Icicle vendor records become Acumatica Vendors with address, contact, and payment terms. Icicle's vendor-linked compliance documents (certifications, insurance) migrate as custom fields (UsrVendorCertification, UsrInsuranceExpDate) since Acumatica has no native vendor document attachment on the Vendor screen. These fields appear on the Vendor detail screen, allowing quick review of expiration dates without opening separate attachments.
Icicle ERP
Sales Order
Acumatica
Sales Order
1:1Open Icicle Sales Orders migrate as Acumatica Sales Orders with the same order number preserved in an extension field (UsrSourceOrderNbr). Line items map to SO lines with stock item link and order quantity. Status 'open' in Icicle becomes 'open' in Acumatica; closed orders migrate as completed records for historical continuity.
Icicle ERP
Purchase Order
Acumatica
Purchase Order
1:1Open Icicle Purchase Orders migrate as Acumatica Purchase Orders. Vendor link resolves to the migrated Vendor record. Line items map to PO lines with inventory item and expected receipt quantity. Icicle's per-vendor lead times become Acumatica's Vendor Lead Time records on the vendor.
Icicle ERP
Production Order
Acumatica
Production Order
1:1Open Icicle production runs migrate as Acumatica Production Orders linked to the corresponding BOM. Ingredient consumption from Icicle's production run maps to material allocation lines in Acumatica. Closed production runs with completed lot numbers migrate as history records with lot number preserved in UsrLotNbr.
Icicle ERP
Quality Test
Acumatica
Quality Management → Inspection
1:1Icicle quality tests linked to lots or inbound shipments have no direct Acumatica equivalent. We create an Inspection record tied to the Lot/Serial number. Test result values map to custom result fields (UsrTestResult1, UsrTestResult2) since Acumatica's default Quality Inspection uses pass/fail rather than numeric thresholds.
Icicle ERP
Facility / Location
Acumatica
Branch / Location
1:1Icicle facilities map to Acumatica Branches when they represent separate legal entities, or to Warehouse codes within a single Branch when they are operational locations. We map Icicle's facility-specific inventory splits to Acumatica's Warehouse codes under the appropriate Branch. Each mapping preserves the facility's cost center so that inter-branch transfers reflect the original site’s accounting.
Icicle ERP
Inventory Lot
Acumatica
Lot/Serial Number
1:1Icicle lot numbers with expiration dates map to Acumatica Lot/Serial records linked to the Stock Item. The lot's creation date, supplier lot code, and quarantine status migrate as custom fields on the lot (UsrLotCreationDate, UsrSupplierLot, UsrQuarantineFlag). These fields enable lot traceability in reporting without relying on external spreadsheets.
Icicle ERP
Custom Object: HACCP Plan
Acumatica
Custom Screen / Note
1:1Icicle's HACCP plan documents and critical control point configurations are food-safety process definitions, not transactional data. We export the full HACCP plan as a PDF attachment linked to the relevant Stock Item. The process logic must be rebuilt in Acumatica's workflow tools.
Icicle ERP
User / Employee
Acumatica
Users / Employees
1:1Icicle users with system access migrate as Acumatica Users by email match. Production staff without system login become Employees in Acumatica's HR module (if activated) linked to branch and work shift. Owner-resolved records (created-by, modified-by) map via email lookup to Acumatica Users.
| Icicle ERP | Acumatica | Compatibility | |
|---|---|---|---|
| Product | Stock Item / Non-Stock Item1:1 | Fully supported | |
| Recipe / Formula | Bill of Materials1:1 | Fully supported | |
| Customer | Customer1:1 | Fully supported | |
| Vendor / Supplier | Vendor1:1 | Fully supported | |
| Sales Order | Sales Order1:1 | Fully supported | |
| Purchase Order | Purchase Order1:1 | Fully supported | |
| Production Order | Production Order1:1 | Fully supported | |
| Quality Test | Quality Management → Inspection1:1 | Fully supported | |
| Facility / Location | Branch / Location1:1 | Fully supported | |
| Inventory Lot | Lot/Serial Number1:1 | Fully supported | |
| Custom Object: HACCP Plan | Custom Screen / Note1:1 | Fully supported | |
| User / Employee | Users / Employees1: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.
Icicle ERP gotchas
No publicly documented API for self-serve data export
Pricing is opaque — no published tiers or per-user rates
Lot traceability links are schema-critical and must survive migration
Co-packer contract records use non-standard field structures
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
Build Acumatica schema: Lot/Serial classes, custom fields, Branch structure
Before any data moves, FlitStack creates the Lot/Serial classes required for lot-enabled products, adds Usr-prefix custom fields to the Stock Item, Vendor, Production Order, QMInspection, and other DACs based on Icicle's custom properties. We also map Icicle facilities to Acumatica Branches and flag any that need separate Company creation. The Acumatica admin reviews and publishes the schema changes so the destination is ready before field mapping validation begins.
Migrate vendors and customers first, then products with BOMs
Acumatica requires vendors before Purchase Orders and customers before Sales Orders. We sequence the migration: Vendors → Customers → Stock Items and Non-Stock Items → Bill of Materials with revisions → Production Orders → Sales Orders → Purchase Orders. This ordering ensures foreign key resolution — SOLine.InventoryID must reference an existing Stock Item; PO.VendorID must reference an existing Vendor. Any unresolved references are flagged before the full run.
Migrate production orders with lot numbers linked to BOM revisions
Production Orders in Acumatica reference an active BOM revision. After BOMs are migrated and activated, we load production orders linking to the correct InventoryID and BOMID. The Icicle lot number, ingredient lot consumption, and production run notes migrate as custom fields on the Acumatica Production Order (UsrLotNbr, UsrIngredientLots, UsrRunNotes). Quality test results load as Inspection records linked to the produced lot.
Run a sample migration of 50–100 records and generate a field-level diff
A representative slice migrates first — spanning 10 products with BOMs, 5 customers, 5 vendors, 10 open sales orders, 5 production orders, and 5 quality tests. FlitStack generates a field-level comparison report showing source values against destination fields. You verify lot class assignment, BOM revision mapping, quality result translation, and custom field population. This sample sign-off gates the full run.
Execute full migration with delta-pickup window and audit log
The full migration loads all open and historical records into Acumatica. A delta-pickup window (24–48 hours) captures any new orders, production runs, or inventory adjustments created in Icicle during the cutover window. Every operation is captured in an audit log. If reconciliation reveals record count discrepancies or missing data, one-click rollback reverts the Acumatica environment to its pre-migration state while Icicle remains fully operational throughout.
Platform deep dives
Icicle ERP
Source
Strengths
Weaknesses
Acumatica
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 Icicle ERP and Acumatica.
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
Icicle ERP: Not publicly documented.
Data volume sensitivity
Icicle ERP doesn't expose a bulk API — REST + parallelization used for high-volume runs.
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 Icicle ERP to Acumatica migration scoping. Not seeing yours? Book a call.
Walk through your Icicle ERP 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 Icicle ERP
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.