ERP migration

Migrate from Icicle ERP to Acumatica

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

Icicle ERP logo

Icicle ERP

Source

Acumatica

Destination

Acumatica logo

Compatibility

100%

12 of 12

objects map 1:1 between Icicle ERP and Acumatica.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Icicle ERP logo

Icicle ERP

What's pushing teams away

  • Navigation complexity for new users — Capterra reviewers note the UI has many avenues to access the same function, and the learning curve is steep without formal training and the vendor's help videos.
  • Limited review volume — G2 shows only 28 verified reviews for Icicle ERP, making it difficult for prospective buyers to assess long-term reliability compared to competitors with hundreds of reviews.
  • Pricing opacity — Icicle publishes no public pricing tiers; all quotes go through a sales process, which creates friction for small food businesses evaluating budget constraints.
  • Smaller vendor footprint — with roughly 15 employees, Icicle is a niche Canadian vendor compared to global ERP players, raising concerns about long-term product roadmap stability and support scalability.

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 Icicle ERP objects map to Acumatica

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

maps to

Acumatica

Stock Item / Non-Stock Item

1:1
Fully supported

Icicle 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

maps to

Acumatica

Bill of Materials

1:1
Fully supported

Icicle 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

maps to

Acumatica

Customer

1:1
Fully supported

Direct 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

maps to

Acumatica

Vendor

1:1
Fully supported

Direct 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

maps to

Acumatica

Sales Order

1:1
Fully supported

Open 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

maps to

Acumatica

Purchase Order

1:1
Fully supported

Open 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

maps to

Acumatica

Production Order

1:1
Fully supported

Open 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

maps to

Acumatica

Quality Management → Inspection

1:1
Fully supported

Icicle 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

maps to

Acumatica

Branch / Location

1:1
Fully supported

Icicle 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

maps to

Acumatica

Lot/Serial Number

1:1
Fully supported

Icicle 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

maps to

Acumatica

Custom Screen / Note

1:1
Fully supported

Icicle'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

maps to

Acumatica

Users / Employees

1:1
Fully supported

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

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.

Icicle ERP logo

Icicle ERP gotchas

High

No publicly documented API for self-serve data export

Medium

Pricing is opaque — no published tiers or per-user rates

High

Lot traceability links are schema-critical and must survive migration

Medium

Co-packer contract records use non-standard field structures

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

  • Bill of Materials revision versioning requires BOM activation before production orders can reference them

    Acumatica BOMs exist as drafts until explicitly activated. Icicle recipes have a version number but no separate draft state. When we migrate recipes as BOMs with revision IDs, each BOM must be set to 'Active' status before Production Orders can consume it. If production orders land in Acumatica referencing inactive BOMs, the system throws an error at fulfillment. We run a BOM activation step immediately after the BOM migration and before any production order data is loaded. This sequencing is handled in the migration plan delivered before the full run.

  • Lot/Serial class assignment is required before lot-enabled stock items can receive inventory

    Icicle lot tracking is enabled per product and carries expiration dates and supplier lot codes. Acumatica requires a Lot/Serial class to be defined first (with fields like LotSize, ExpirationDate, SupplierLot) and then assigned to the Stock Item before any lot-tracked inventory can be received. If we load lot-controlled Stock Items before the Lot/Serial class exists, the import fails. We create all required Lot/Serial classes before inventory data moves, using Icicle's lot class names as the Acumatica class IDs for traceability.

  • Quality test results require custom fields — Acumatica defaults to pass/fail inspection codes

    Icicle quality tests capture numeric thresholds (pH, temperature, weight variance) tied to specific test procedures. Acumatica's Quality Management module uses Inspection records with pass/fail disposition codes by default. Numeric threshold values from Icicle have no native landing place in Acumatica's inspection setup. We extend the QMInspection DAC with custom result fields (UsrTestResult1, UsrTestResult2) and surface these in the inspection detail screen. This requires Acumatica schema customization before the quality data migration runs.

  • Multi-facility Icicle setups map to Acumatica Branch structure which may require separate tenant configuration

    Icicle allows multiple facilities within a single instance, each with its own inventory and users. Acumatica maps facilities to Branches under a Company. If the Icicle facilities represent separate legal entities (different tax registrations, separate GLs), they map to separate Companies within one Acumatica tenant. Inter-company transactions require Acumatica's inter-company accounting configuration. We flag any Icicle facility with a distinct tax ID for separate Company creation and surface the configuration requirements in the pre-migration schema plan.

  • HACCP plan and food-safety automation logic do not have Acumatica equivalents and must be rebuilt

    Icicle's HACCP plan definitions, critical control point thresholds, and automated alert rules are food-safety process logic. Acumatica's workflow engine handles approval routing and notification automation but does not natively replicate HACCP monitoring. Any Icicle alerts that fire when a production temperature falls outside a defined range, or that hold a batch pending quality sign-off, need to be rebuilt using Acumatica's screen-level automation or notification templates. We export the full HACCP plan documentation as PDFs and deliver a configuration guide mapping each Icicle rule to its Acumatica workflow equivalent.

Migration approach

Six steps for a successful Icicle ERP to Acumatica data migration

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

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

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

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

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

Context on both ends of the pair

Icicle ERP logo

Icicle ERP

Source

Strengths

  • Purpose-built for food & beverage manufacturing, not a horizontal ERP with a food module bolted on.
  • First-class lot traceability with forward and backward genealogy as a native data concept, not a workaround.
  • Cloud-based with multi-facility support, enabling single-database operations across multiple plants.
  • Integrated food safety and quality modules (HACCP, FSMA) reduce the need for separate compliance tooling.
  • Strong customer service reputation with 5.0/5.0 on Capterra for support quality.

Weaknesses

  • Very small vendor with approximately 15 employees, raising long-term roadmap and support scalability questions.
  • No public pricing published; all licensing requires a direct sales conversation.
  • Small review base (28 verified G2 reviews) limits third-party reliability signals for buyers.
  • Limited publicly documented API or data export tooling, making self-serve data extraction harder for customers.
  • Less suitable for food businesses with complex international operations across multiple regulatory jurisdictions.
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. 1 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 Icicle ERP and Acumatica.

  • Object compatibility

    B

    1 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

    Icicle ERP: Not publicly documented.

  • Data volume sensitivity

    B

    Icicle ERP doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Icicle ERP 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 Icicle ERP to Acumatica data migrations

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

Can't find your answer?

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 consultation

Most Icicle-to-Acumtica migrations complete in 48–72 hours for setups with fewer than 25,000 records and a single facility. Multi-facility migrations with separate legal entities, more than 200 stock items with multi-level BOMs, or extensive quality test history extend to 5–10 days. The longest planning step is mapping Icicle recipes to Acumatica BOM revisions and configuring Lot/Serial classes before inventory data can land.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Icicle ERP.
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