ERP migration
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
Source
Acumatica
Destination
Compatibility
14 of 14
objects map 1:1 between Herbst Insight ERP and Acumatica.
Complexity
BStandard
Timeline
5–10 business days
Overview
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.
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 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
Acumatica
GL Account (Account)
1:1Herbst 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
Acumatica
Customer (CR303000)
1:1Herbst 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
Acumatica
Vendor (AP303000)
1:1Herbst 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
Acumatica
Inventory Item (IN202500)
1:1Herbst 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
Acumatica
SO Order (SO301000)
1:1Open 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
Acumatica
PO Order (PO301000)
1:1Open 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
Acumatica
AR Invoice (AR301000)
1:1Herbst 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
Acumatica
AP Invoice (AP301000)
1:1Herbst 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
Acumatica
IN Release (IN302000)
1:1Herbst 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
Acumatica
Contact (CR302000)
1:1Herbst 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)
Acumatica
Custom DAC Fields (Usr-prefixed)
1:1Any 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)
Acumatica
GL Batch (GL301000) or Archived Records
1:1Closed 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
Acumatica
Branch (CS205000)
1:1Herbst 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
Acumatica
Warehouse (WH204000)
1:1Herbst 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.
| Herbst Insight ERP | Acumatica | Compatibility | |
|---|---|---|---|
| Account / Nominal Ledger | GL Account (Account)1:1 | Fully supported | |
| Company / Customer | Customer (CR303000)1:1 | Fully supported | |
| Supplier / Creditor | Vendor (AP303000)1:1 | Fully supported | |
| Product / Stock Item | Inventory Item (IN202500)1:1 | Fully supported | |
| Sales Order | SO Order (SO301000)1:1 | Fully supported | |
| Purchase Order | PO Order (PO301000)1:1 | Fully supported | |
| Sales Invoice / AR Invoice | AR Invoice (AR301000)1:1 | Fully supported | |
| Purchase Invoice / AP Invoice | AP Invoice (AP301000)1:1 | Fully supported | |
| Stock Movement / GRN | IN Release (IN302000)1:1 | Fully supported | |
| Contact | Contact (CR302000)1:1 | Fully supported | |
| User-Defined Fields (Custom Properties) | Custom DAC Fields (Usr-prefixed)1:1 | Fully supported | |
| Historical Transactions (Closed Documents) | GL Batch (GL301000) or Archived Records1:1 | Fully supported | |
| Branch / Company Entity | Branch (CS205000)1:1 | Fully supported | |
| Warehouse / Location | Warehouse (WH204000)1: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.
Herbst Insight ERP gotchas
Herbst does not publish public API documentation or rate limits
Herbst Web Portal exports are module-scoped, not transactional graphs
SaaS hosting means migration windows depend on vendor co-operation
Payroll module migration requires jurisdiction-specific sign-off
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
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.
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.
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.
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.
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
Herbst Insight 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 Herbst Insight 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
Herbst Insight ERP: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.
Data volume sensitivity
Herbst Insight 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 Herbst Insight ERP to Acumatica migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Herbst Insight 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.