ERP migration
Field-level mapping, validation, and rollback between Manu Online and Acumatica. We move data and schema; workflows are rebuilt natively in Acumatica.
Manu Online
Source
Acumatica
Destination
Compatibility
12 of 12
objects map 1:1 between Manu Online and Acumatica.
Complexity
BStandard
Timeline
72–120 hours
Overview
Manu Online organizes manufacturing data around products, work orders, customers, and suppliers in a single-company model with Xero as the financial layer. Acumatica restructures that data across multiple entities, with BOMs as separate versioned objects, work orders flowing into production management, and inventory tracked with branch-specific quantities and valuation methods. The migration carries all Manu Online records into Acumatica's import scenario format — mapping stock items to Inventory Items, suppliers to Vendors, customers to Customers, and work orders to Production Orders with their cost layers intact. Manu Online workflows (approval rules, reorder triggers) do not migrate and must be rebuilt in Acumatica's Automation Schedules and notification framework. FlitStack AI sequences the migration so foreign keys resolve in the correct order — companies first, then inventory, then BOMs, then production orders — and runs a delta-pickup window to capture any in-flight work orders during cutover. The Manu Online DataWarehouse extension, if active, is replaced by Acumatica's generic inquiries and report writer.
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 Manu Online 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.
Manu Online
Product (Inventory Item)
Acumatica
Non-Stock Item / Stock Item
1:1Manu Online products (both manufactured and resell) map to Acumatica Non-Stock Items if they have no warehouse presence, or Stock Items if they carry inventory. The mapping preserves the product type flag (make vs. buy) and triggers the creation of the corresponding Acumatica item class before the import scenario runs.
Manu Online
Bill of Materials (BOM)
Acumatica
Bill of Materials (BOM)
1:1Manu Online BOMs with version numbers map to Acumatica BOM versions with revision IDs. Multi-level Manu Online BOMs (sub-assemblies) are flattened to their top-level BOM in Acumatica's Material Management; each level becomes a separate BOM with the child item linked via the Materials tab. Overhead cost categories on the Manu Online BOM are added as overhead codes in Acumatica's Cost Profile.
Manu Online
Work Order
Acumatica
Production Order
1:1Manu Online work orders map to Acumatica Production Orders with production order type determined by the Manu Online work order category (make-to-stock vs. make-to-order). The production order status is translated using the Acumatica production order lifecycle (on hold, planned, in process, completed, closed), and the Manu Online labor hours and material allocations are preserved in the production order's labor and material detail tabs.
Manu Online
Customer
Acumatica
Customer
1:1Manu Online customers map directly to Acumatica Customers. The customer's default location (address) becomes the Acumatica Customer Location record. If Manu Online stores multiple contacts per customer, secondary contacts are added as Contact records linked to the Customer Location. Payment terms and credit limits from Manu Online are written to the Customer's Terms tab and Credit tab respectively.
Manu Online
Supplier / Vendor
Acumatica
Vendor
1:1Manu Online suppliers map to Acumatica Vendors. The vendor's default address becomes the Acumatica Vendor Location. Manu Online's supplier product catalog (vendor-specific pricing per item) is stored as Vendor Prices in Acumatica's Purchasing tab linked to the Vendor ID and Inventory Item ID.
Manu Online
Sales Order
Acumatica
Sales Order
1:1Open Manu Online sales orders map to Acumatica Sales Orders with order type (SO) and the current fulfillment status preserved. Historical (completed) sales orders are imported as Sales Order records with a completed status flag for financial audit trails. Tax calculation settings from Manu Online are mapped to Acumatica Tax Zone rules per customer location.
Manu Online
Purchase Order
Acumatica
Purchase Order
1:1Open Manu Online purchase orders map to Acumatica Purchase Orders. Line items retain the linked inventory item, quantity ordered, and unit cost from Manu Online. Receipts not yet received in Manu Online are reflected as open line quantities in Acumatica awaiting Goods Receipt.
Manu Online
Stock / Inventory Record
Acumatica
Inventory Receipt / Issue
1:1Current stock quantities from Manu Online are imported as Acumatica Inventory Receipt transactions to establish opening balances per branch and warehouse. Lot numbers and FIFO cost layers are preserved as separate lot/serial classes in Acumatica; each receipt creates a cost layer that feeds into Acumatica's cost layer manager for FIFO valuation.
Manu Online
Lot / Serial Number
Acumatica
Lot / Serial Class and Assignment
1:1Manu Online lot numbers and expiration dates map to Acumatica Lot/Serial Classes. Each lot assignment in Manu Online is created as an Inventory Receipt with the lot number populated in the Lot/Serial Nbr field. Expiration dates are carried over as lot expiration dates in Acumatica for shelf-life management.
Manu Online
Custom Product Properties
Acumatica
Usr Custom Fields on Inventory Item
1:1Manu Online custom properties on products (such as finish type, compliance flags, or supplier codes) are mapped to Acumatica Usr-prefixed custom fields on the Inventory Item DAC. These fields must be defined in an Acumatica Customization Project before the inventory import scenario runs; FlitStack delivers the field definition XML as part of the migration package.
Manu Online
Custom Customer Fields
Acumatica
Usr Custom Fields on Customer
1:1Manu Online custom properties on customers (such as preferred delivery days, account tier, or credit references) are mapped to Acumatica Usr-prefixed custom fields on the Customer DAC. Each field is created in the Acumatica Customization Project prior to the customer import.
Manu Online
Attachment / File
Acumatica
Note / File Attachment on Entity
1:1Manu Online file attachments (PDFs, images, documents linked to products, customers, or work orders) are re-uploaded to Acumatica as Note records with the file attached. The note is linked to the corresponding entity (Inventory Item, Customer, or Production Order) using the NoteID reference. File size limits from Acumatica apply (25MB per file).
| Manu Online | Acumatica | Compatibility | |
|---|---|---|---|
| Product (Inventory Item) | Non-Stock Item / Stock Item1:1 | Fully supported | |
| Bill of Materials (BOM) | Bill of Materials (BOM)1:1 | Fully supported | |
| Work Order | Production Order1:1 | Fully supported | |
| Customer | Customer1:1 | Fully supported | |
| Supplier / Vendor | Vendor1:1 | Fully supported | |
| Sales Order | Sales Order1:1 | Fully supported | |
| Purchase Order | Purchase Order1:1 | Fully supported | |
| Stock / Inventory Record | Inventory Receipt / Issue1:1 | Fully supported | |
| Lot / Serial Number | Lot / Serial Class and Assignment1:1 | Fully supported | |
| Custom Product Properties | Usr Custom Fields on Inventory Item1:1 | Fully supported | |
| Custom Customer Fields | Usr Custom Fields on Customer1:1 | Fully supported | |
| Attachment / File | Note / File Attachment on Entity1: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.
Manu Online gotchas
DataWarehouse SQL export is the only bulk data path
Xero integration can duplicate posted invoices
FIFO cost layers do not translate directly to average-cost ERPs
Serial and lot traceability is source-system-gated
Enterprise-tier features may not appear in Mini Enterprise data
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
Inventory source schema and Acumatica custom field deployment
FlitStack extracts the Manu Online data model from the DataWarehouse SQL schema and the API object list. We identify all custom product properties, custom customer properties, lot classes, and FIFO cost layer structures. Before any data moves, your Acumatica admin deploys the custom field XML (Usr-prefixed fields on Inventory Item, Customer, and Vendor DACs) via the Customization Project editor. This step gates all downstream imports — no record type-checks or field-mapping can begin until the schema is in place.
Export and cleanse manufacturing master data
We pull all products (stock and non-stock), BOMs with version history, customers, suppliers, and lot records from Manu Online via the DataWarehouse SQL export and the REST API. Records are deduplicated by external ID, cleaned for character encoding issues, and validated against the target Acumatica schema. Products flagged as manufactured are queued for BOM import first so that top-level finished goods exist before BOM line items reference them. Any circular BOM references (product A uses product B which uses product A) are flagged for your engineering team to resolve before migration.
Sequence the migration: entities and inventory first, then transactions
Acumatica import scenarios require referential integrity — inventory items must exist before purchase order lines reference them, and vendors must exist before PO headers are created. FlitStack sequences the migration in this order: (1) Companies and branches, (2) Customers and vendors with locations and contact details, (3) Inventory items with stock classes and unit of measure conversions, (4) BOM versions with material and overhead components, (5) Opening inventory balances and lot assignments with FIFO cost layers, (6) Open purchase orders, (7) Open sales orders, (8) In-process work orders mapped to production orders. Each phase runs as a separate import scenario so failures are isolated to a single object type.
Run a sample migration with field-level diff on 200–500 records
A representative slice of data — covering at least one manufactured item with a multi-level BOM, one lot-tracked item with FIFO layers, one open work order, one open sales order, and one open purchase order — migrates first into a staging Acumatica tenant. FlitStack generates a field-level diff comparing source values against destination field values, including custom field values, cost layer counts, and BOM component quantities. You verify that Acumatica reports and generic inquiries show the correct inventory valuation, production order costs, and customer balances before the full run commits.
Execute full migration with delta-pickup window
The full migration runs against the production Acumatica tenant, importing all records in sequenced phases. Manu Online remains fully operational throughout — FlitStack uses read-only API access. A delta-pickup window opens at the point of your choosing (typically 24–48 hours before the Acumatica go-live date) to capture any new work orders, purchase receipts, or customer records created in Manu Online during the cutover. FlitStack generates an audit log of every record inserted, updated, or skipped, and one-click rollback is available if reconciliation reveals unexpected discrepancies in inventory quantities or open-order values.
Platform deep dives
Manu Online
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 Manu Online 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
Manu Online: Not publicly documented.
Data volume sensitivity
Manu Online 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 Manu Online to Acumatica migration scoping. Not seeing yours? Book a call.
Walk through your Manu Online 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 Manu Online
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.
