ERP migration

Migrate from Herbst Insight ERP to Acumatica

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

Herbst Insight ERP logo

Herbst Insight ERP

Source

Acumatica

Destination

Acumatica logo

Compatibility

100%

14 of 14

objects map 1:1 between Herbst Insight ERP and Acumatica.

Complexity

BStandard

Timeline

5–10 business days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Herbst Insight ERP organizes business data around a modular schema: accounts and nominal ledgers, contact and company management, stock and inventory records, sales orders, purchase orders, and job-costing entries. The system stores entities in a traditional relational structure with user-defined fields at the database level. Acumatica Cloud ERP uses a data access class (DAC) framework built on PX objects, where every entity (Customer, Vendor, InventoryItem, SOOrder, APInvoice) has a corresponding C# class, and custom fields follow a Usr prefix convention added via the Customization Project Editor. Acumatica enforces a segment-based chart of accounts, multi-branch warehouse assignments, and API rate limits tied to license tier (concurrent requests capped at 3–10 depending on tier). FlitStack AI sequences the migration by exporting Herbst data via the system's export utilities into a staging format, then ingesting into Acumatica through its REST and SOAP APIs — respecting rate limits, mapping nominal codes to GL accounts, and creating Usr-prefixed custom fields for any Herbst user-defined properties. Workflow automations, approval routines, and custom business logic do not migrate and must be rebuilt in Acumatica's automation framework.

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

Herbst Insight ERP logo

Herbst Insight ERP

What's pushing teams away

  • No public pricing — quotes are sales-led through Herbst Software or its reseller network.
  • Ireland-centric — multinational SMEs operating outside Ireland may find international support and localisation thinner than NetSuite or Sage Intacct.
  • Limited public API documentation — extraction requires reseller or vendor engagement.
  • Smaller third-party developer/integrator ecosystem compared to mainstream cloud ERPs.
  • Companies scaling beyond mid-market complexity (multi-entity consolidation, IFRS reporting at scale) typically migrate to NetSuite, Microsoft Dynamics 365, or SAP.

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

Each row shows how a Herbst Insight 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.

Herbst Insight ERP

Account / Nominal Ledger

maps to

Acumatica

GL Account (Account)

1:1
Fully supported

Herbst nominal codes map to Acumatica GL accounts. The mapping extracts the account segment values from Herbst's freeform code and assigns them to the corresponding Acumatica segment structure defined in GL204000. Sub-account levels in Herbst become separate segment values or sub-account masks in Acumatica's segment editor.

Herbst Insight ERP

Company / Customer

maps to

Acumatica

Customer (CR303000)

1:1
Fully supported

Herbst company records with customer type map directly to Acumatica Customer. Primary address, contact details, and credit terms transfer as Customer attributes. Herbst's customer price group maps to Acumatica's Customer Class (AR204000), which drives default terms and tax settings. The migration also aligns payment hold flags and credit limits with the corresponding Customer Class defaults.

Herbst Insight ERP

Supplier / Creditor

maps to

Acumatica

Vendor (AP303000)

1:1
Fully supported

Herbst supplier records migrate to Acumatica Vendor. Payment terms, tax ID, and remittance address fields transfer directly. Herbst's supplier category codes map to Acumatica Vendor Class, which controls default accounts payable accounts and approval workflow settings. Additionally, vendor-specific discount tiers and preferred carrier information are matched to the Vendor Class defaults for consistent purchasing workflow.

Herbst Insight ERP

Product / Stock Item

maps to

Acumatica

Inventory Item (IN202500)

1:1
Fully supported

Herbst stock items map to Acumatica Inventory Item. Item class (defined in IN201000) determines the default valuation method, posting accounts, and MO recalculation settings. Herbst's product category hierarchy becomes the Acumatica item class tree structure, which controls inventory posting at the class level.

Herbst Insight ERP

Sales Order

maps to

Acumatica

SO Order (SO301000)

1:1
Fully supported

Open Herbst sales orders migrate to Acumatica SO Order with status Open or Pending. Order lines map to SO Order lines with warehouse and lot/serial assignments. Herbst's order discount matrix maps to Acumatica's volume discount rules or Customer Price Class overrides on the Sales Prices screen (AP202000 equivalent).

Herbst Insight ERP

Purchase Order

maps to

Acumatica

PO Order (PO301000)

1:1
Fully supported

Open purchase orders migrate to Acumatica PO Order. Vendor assignment, line items, and expected delivery dates transfer directly. Herbst's buyer assignment maps to Acumatica's default purchaser on the Vendor record or PO Preferences (PO101000) defaults. If a Herbst purchase order includes project or cost code references, these are stored in custom fields on the PO Line for downstream job-cost reporting in Acumatica.

Herbst Insight ERP

Sales Invoice / AR Invoice

maps to

Acumatica

AR Invoice (AR301000)

1:1
Fully supported

Herbst AR invoices migrate to Acumatica AR Invoice with original invoice number preserved in the Reference Nbr. field. The invoice's original date is stored in a custom field (UsrOriginalDocDate) since Acumatica's document date reflects the migration date. Line items map to ARTran records with inventory ID, quantity, and amount.

Herbst Insight ERP

Purchase Invoice / AP Invoice

maps to

Acumatica

AP Invoice (AP301000)

1:1
Fully supported

Herbst AP invoices migrate to Acumatica AP Invoice. Vendor reference number maps to the Invoice Nbr. field. Prepayments and credit memos migrate as separate document types with appropriate GL postings. Tax amounts from Herbst map to APTran tax codes for reporting continuity.

Herbst Insight ERP

Stock Movement / GRN

maps to

Acumatica

IN Release (IN302000)

1:1
Fully supported

Herbst goods received notes and stock movements are represented as IN Adjustment entries in Acumatica. Each movement is posted as a separate IN Register record with Issue or Receipt type. Lot and serial numbers from Herbst transfer to Acumatica's lot/serial tracking (requires the Lot/Serial class enabled on the Inventory Item).

Herbst Insight ERP

Contact

maps to

Acumatica

Contact (CR302000)

1:1
Fully supported

Herbst contact records (associated with companies or standalone) map to Acumatica Contact. Email, phone, job title, and address fields transfer directly. Herbst contact classification tags (e.g., decision-maker labels) map to Acumatica's contact class or a custom contact attribute field created as a Usr-prefixed field.

Herbst Insight ERP

User-Defined Fields (Custom Properties)

maps to

Acumatica

Custom DAC Fields (Usr-prefixed)

1:1
Fully supported

Any Herbst user-defined columns on standard tables require Acumatica DAC extensions. FlitStack creates a Customization Project with Usr-prefixed fields on the corresponding DAC (e.g., UsrOriginalRefNbr on SOOrder). The customization is published to the Acumatica instance before data loads, and the project file is included in the migration package.

Herbst Insight ERP

Historical Transactions (Closed Documents)

maps to

Acumatica

GL Batch (GL301000) or Archived Records

1:1
Fully supported

Closed Herbst invoices, completed purchase orders, and historic job cost records are migrated as GL Journal batches in Acumatica if the closed documents need to appear in historical reporting. Alternatively, they are preserved in a read-only reference archive accessible from a custom screen. Active reconciliation depends on the reporting scope agreed with the customer before migration.

Herbst Insight ERP

Branch / Company Entity

maps to

Acumatica

Branch (CS205000)

1:1
Fully supported

Herbst company entities or branch identifiers map to Acumatica Branch records. Each Herbst legal entity or operating unit becomes a Branch record in Acumatica with its own address, attributes, and default warehouse. Branch-level security is configured in Acumatica's access rights screens after migration.

Herbst Insight ERP

Warehouse / Location

maps to

Acumatica

Warehouse (WH204000)

1:1
Fully supported

Herbst warehouse or location codes map to Acumatica Warehouse. Address, lead time, default bins, and cross-dock settings transfer. If Herbst uses bin locations, Acumatica's Warehouse Management preferences (IN204000) must be enabled before bin data loads, or bins are created as part of the initial setup.

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.

Herbst Insight ERP logo

Herbst Insight ERP gotchas

High

Herbst does not publish public API documentation or rate limits

Medium

Herbst Web Portal exports are module-scoped, not transactional graphs

Medium

SaaS hosting means migration windows depend on vendor co-operation

Low

Payroll module migration requires jurisdiction-specific sign-off

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

  • Herbst file-based export vs Acumatica API ingestion creates a staging-layer requirement

    Herbst Insight ERP lacks a well-documented public REST or SOAP API; the primary export path is file-based (CSV, Excel, or ODBC query). Acumatica's data ingestion relies on REST endpoints (for records) or import scenarios (for mass loads). FlitStack AI builds a staging layer that transforms Herbst file exports into Acumatica-compatible payloads, validates referential integrity before API calls, and handles Acumatica's license-based concurrent request limits (visible on the License Monitoring Console SM604000). Without this staging step, direct API calls fail on Herbst's side and exceed Acumatica's rate caps on the destination side.

  • Acumatica's segment-based chart of accounts requires upfront design before any GL migration

    Acumatica enforces a structured segment model for GL accounts — up to 7 segments defined in GL204000. Each segment has a length, type (numeric or string), and masks. Herbst's nominal ledger uses a more flexible freeform account code structure that often encodes entity, department, and account in a single string (e.g., 4-100-0010). Before any GL data loads, the migration team must agree on the segment breakdown with the customer's Acumatica consultant. The account mapping plan must be finalized and the Acumatica chart of accounts created before the first journal entry or invoice posts, or all GL records will fail validation.

  • Custom fields in Herbst require Acumatica Customization Project creation before data loads

    Herbst stores user-defined fields as raw database columns on standard tables. Acumatica has no equivalent freeform column addition — custom fields must be declared in a Customization Project using the Customization Project Editor (CstEditor), which generates Usr-prefixed fields on the corresponding Data Access Class (DAC). If Herbst has 20+ custom fields across customers, vendors, and inventory items, the Acumatica customization project must be built, published, and tested before any data migration runs. FlitStack delivers the Customization Project as part of the schema setup phase, but the customer or their Acumatica partner must publish it to the target tenant.

  • Acumatica API rate limits are tied to license tier and can throttle bulk imports

    Acumatica's license sets a maximum number of concurrent API requests (typically 3 for standard tiers, up to 10 for higher tiers) and a requests-per-minute cap. These are visible on the License Monitoring Console (SM604000) under the Maximum Number of Concurrent Web Services API Requests setting. When FlitStack runs a bulk migration with thousands of records, API calls are queued and batched to respect these limits. For large inventories (50,000+ SKUs) or high-volume transactional histories, the migration clock time extends proportionally. Customers upgrading their Acumatica license tier before migration reduces this constraint.

  • Herbst closed transaction history may need manual reconciliation or archival treatment

    Herbst stores all historical invoices, credit notes, and closed orders in the same database as open records. Acumatica distinguishes between open documents (SOOrder, ARInvoice) and historical batches posted to the GL. Migrating every closed Herbst document as an open Acumatica document creates incorrect aging reports and duplicative posting. FlitStack maps closed Herbst documents to GL Journal batches or a custom archive screen, depending on whether the customer requires live aging reports against historical records. This decision must be made before migration planning, as it changes the record count and per-record mapping logic significantly.

Migration approach

Six steps for a successful Herbst Insight ERP to Acumatica data migration

  1. Audit Herbst data model and export path

    FlitStack AI connects to the Herbst database via read-only ODBC access or file export utilities to enumerate the full schema: table list, column names, user-defined columns, and foreign key relationships. We document the chart of accounts structure, customer/vendor categories, item classes, and any custom tables added by the Herbst consultant. This audit produces a Data Map Specification document that drives the Acumatica schema setup and the field mapping plan.

  2. Design Acumatica schema and create customization project

    Working from the Data Map Specification, we design the Acumatica chart of accounts with segment definitions, create the branch structure, configure inventory item classes and warehouse records, and define numbering sequences. Any Herbst user-defined fields are added as Usr-prefixed fields in a Customization Project. The customization project is packaged and delivered to the customer's Acumatica admin for publication to the target tenant before data ingestion begins.

  3. Build staging layer and run trial migration

    We build a transformation pipeline that reads Herbst export files or ODBC extracts, applies field-level mappings, resolves foreign key lookups (customer names to Acumatica CustomerIDs, stock codes to InventoryCDs), and generates Acumatica REST payloads or import files. A trial migration runs against the Acumatica sandbox or test tenant using a representative slice of 500–1,000 records. A field-level diff report is generated showing source vs. destination values for every mapped field, with any validation errors flagged for resolution before the full run.

  4. Execute full migration with delta-pickup window

    The full migration runs against the production Acumatica tenant, loading master data (customers, vendors, inventory) first, then transactional documents in date order. A delta-pickup window opens at the agreed cutover time — typically 24–48 hours — capturing any new Herbst orders, invoices, or stock movements created during the transition. All operations are logged in the FlitStack audit trail. The customer can roll back to the pre-migration state within one click if reconciliation fails.

  5. Reconcile and sign off

    FlitStack generates a reconciliation report comparing record counts, account totals, and aging balances between Herbst and Acumatica. The customer finance team reviews and signs off on the migration. Any remaining discrepancies are corrected in Acumatica before the Herbst account is set to read-only or decommissioned. Workflow definitions, approval routines, and custom business logic from Herbst are exported as process documentation for rebuilding in Acumatica's automation framework.

Platform deep dives

Context on both ends of the pair

Herbst Insight ERP logo

Herbst Insight ERP

Source

Strengths

  • SaaS delivery eliminates on-premise hardware, patching, and IT overhead for SMEs.
  • Modular design lets businesses configure only the modules they need — accounting, CRM, HR, payroll, distribution.
  • Irish-headquartered with direct vendor support and local reseller network.
  • Integrated web portal gives customers self-service access to orders, invoices, and statements.
  • Real-time ROM reports provide immediate visibility into accounts data across modules.

Weaknesses

  • Very limited public API documentation — export relies on direct database access or partner tooling.
  • Small market footprint compared to Tier-1 ERPs means fewer third-party integration templates exist.
  • Pricing tiers and feature gates are not publicly published, requiring direct sales engagement.
  • G2 review volume is extremely low (1 verified review), limiting independent quality signals.
  • Hosting is vendor-managed SaaS, giving customers limited control over infrastructure-level customisation.
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 Herbst Insight 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

    Herbst Insight ERP: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your Herbst Insight ERP to Acumatica migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Herbst-to-Acuminica migrations complete within 5–10 business days for datasets under 100,000 transactional records. Large datasets exceeding 500,000 records, complex multi-branch structures, or extensive user-defined field sets extend the timeline to 3–5 weeks. The longest planning step is designing the Acumatica segment-based chart of accounts and publishing the custom field customization project before data ingestion begins. We also schedule a 24‑48 hour delta‑pickup window after the primary load to capture any final changes.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Herbst Insight 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