ERP migration
Field-level mapping, validation, and rollback between Infor VISUAL and Acumatica. We move data and schema; workflows are rebuilt natively in Acumatica.
Infor VISUAL
Source
Acumatica
Destination
Compatibility
12 of 13
objects map 1:1 between Infor VISUAL and Acumatica.
Complexity
BStandard
Timeline
48–72 hours
Overview
Teams migrate from Infor VISUAL when the platform's on-premise constraints and limited ecosystem begin blocking growth into adjacent business models. VISUAL excels at job-shop work orders with operation-scattered materials and job-costing, but its data model was designed before modern cloud expectations around mobile access, API-first integrations, and consumption-based pricing. Acumatica replaces VISUAL's work-order-centric schema with Production Orders, centralized Bill of Materials, and Work Centers. The migration carries master data (customers, vendors, inventory items), transactional history (purchase orders, sales orders, invoices), and manufacturing artifacts (BOMs, routings, work centers) into Acumatica's module structure. Acumatica distinguishes Stock Items from Non-Stock Items, uses Production Orders for manufacturing, and builds costs through Work Center rates and material issues—each requiring deliberate mapping from VISUAL's job-costing model. We extract via VISUAL's database or ION API, transform for Acumatica's schema conventions, and load through Acumatica's import framework or REST endpoints. Workflows, automations, and EDI transaction logic do not migrate; we document them for rebuild in Acumatica's automation tools and EDI configuration screens.
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 Infor VISUAL 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.
Infor VISUAL
Customer
Acumatica
Customer
1:1VISUAL customer records map 1:1 to Acumatica Customers. Address records in VISUAL (multi-address per customer) require expansion into Acumatica's address locators—primary address as default, additional addresses as alternate location records with address type flags. We preserve all contact roles and communication preferences during the migration to maintain customer relationship continuity.
Infor VISUAL
Vendor
Acumatica
Vendor
1:1VISUAL vendor records map directly to Acumatica Vendors. Payment terms, shipping terms, and buyer assignment carry over as direct fields where the values match Acumatica's configuration. VISUAL vendor contacts become Acumatica Vendor Contacts linked via the VendorID lookup, preserving contact name, phone, email, and role information.
Infor VISUAL
Inventory Item
Acumatica
Stock Item / Non-Stock Item
1:manyVISUAL inventory items split into two Acumatica objects based on tracking configuration. Items marked for lot or serial tracking become Stock Items with warehouse quantities and inventory valuation. Non-tracked items become Non-Stock Items used in purchasing and sales but excluded from inventory valuation. The item class from VISUAL maps to Acumatica Item Class to preserve reporting hierarchies.
Infor VISUAL
Bill of Materials (BOM)
Acumatica
Bill of Materials
1:1VISUAL BOMs with materials assigned per operation require decomposition into Acumatica's flat BOM structure. We extract the material-to-operation assignments and preserve them as a custom MultiText field on the BOM so the operation context is not lost during consolidation. Multi-level BOM hierarchies are flattened and referenced via parent BOM ID where applicable.
Infor VISUAL
Routing
Acumatica
Work Center / Labor Code
1:1VISUAL routing operations map to Work Centers in Acumatica Manufacturing. Each routing step becomes a Work Center operation with machine and labor rates extracted from VISUAL's operation cost layers. Overhead rates require Acumatica overhead code configuration, and we map operation sequences to Work Center priority ordering for scheduling continuity.
Infor VISUAL
Work Order
Acumatica
Production Order
1:1VISUAL work orders map directly to Acumatica Production Orders. The ProductionNbr comes from VISUAL's wor_kit_num. Status values map via value translation table (Released, In Process, Completed, Closed). Original scheduled dates map to Production Order header for reporting continuity. Parent-child work order relationships become linked Production Orders.
Infor VISUAL
Work Order Material
Acumatica
Material List (Production Order)
1:1VISUAL operation-level material assignments become Acumatica Material List lines. We aggregate materials to header-level lines to match Acumatica's BOM usage model, while preserving which VISUAL operation originally consumed each material via a custom MaterialSource__c field. Scrap factors and shrinkage percentages carry over as notes on material lines.
Infor VISUAL
Work Order Labor
Acumatica
Labor Entry (Production Order)
1:1VISUAL labor entries (setup hours, run hours, labor rate per operation) map to Acumatica Labor entries on the Production Order. Labor codes in Acumatica reference Work Centers for rate lookup, matching VISUAL's cost layer model.we migrate both posted and unposted labor entries to preserve production cost history.
Infor VISUAL
Sales Order
Acumatica
Sales Order
1:1VISUAL sales orders migrate to Acumatica Sales Orders with order number, dates, customer reference, line items, and discounts preserved. Open orders migrate with status; invoiced orders migrate as closed records for historical completeness. Shipment history becomes inventory transactions in Acumatica's warehouse management.
Infor VISUAL
Purchase Order
Acumatica
Purchase Order
1:1VISUAL purchase orders map to Acumatica Purchase Orders. Line items, vendor, terms, and shipment details carry over. Receipt history in VISUAL becomes landed cost entries or receipt lines in Acumatica depending on receipt status. Partially received POs retain their receipt balances for continued receiving in Acumatica.
Infor VISUAL
Invoice
Acumatica
AR Invoice / AP Invoice
1:1VISUAL invoices split into Acumatica AR Invoices (customer invoices) and AP Invoices (vendor bills). Payment status and open/closed flags migrate for reconciliation continuity. Historical invoice PDFs stored in VISUAL's document management are re-uploaded to Acumatica File Storage for audit-ready record keeping.
Infor VISUAL
Quote / Estimate
Acumatica
Quote
1:1VISUAL quotes and estimates migrate to Acumatica Quotes with customer link, line items, pricing, and expiration dates. Quote status values map to Acumatica's Quote statuses (Draft, Pending Approval, Accepted). Quotes with expired status migrate for historical reference only, with a flag indicating expiration source system.
Infor VISUAL
Job Cost History
Acumatica
Custom Fields on Production Order
1:1VISUAL's actual cost vs. estimated cost variance per work order requires Acumatica custom fields (EstimatedCost__c, ActualCost__c, Variance__c) because Acumatica's standard cost tracking operates at inventory valuation level, not job-costing level. We surface these for management review and rebuild planning, with drill-down from each Production Order to the underlying cost detail.
| Infor VISUAL | Acumatica | Compatibility | |
|---|---|---|---|
| Customer | Customer1:1 | Fully supported | |
| Vendor | Vendor1:1 | Fully supported | |
| Inventory Item | Stock Item / Non-Stock Item1:many | Fully supported | |
| Bill of Materials (BOM) | Bill of Materials1:1 | Fully supported | |
| Routing | Work Center / Labor Code1:1 | Fully supported | |
| Work Order | Production Order1:1 | Fully supported | |
| Work Order Material | Material List (Production Order)1:1 | Fully supported | |
| Work Order Labor | Labor Entry (Production Order)1:1 | Fully supported | |
| Sales Order | Sales Order1:1 | Fully supported | |
| Purchase Order | Purchase Order1:1 | Fully supported | |
| Invoice | AR Invoice / AP Invoice1:1 | Fully supported | |
| Quote / Estimate | Quote1:1 | Fully supported | |
| Job Cost History | Custom Fields on Production Order1: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.
Infor VISUAL gotchas
Work Order BOM attachment logic breaks if migrated as flat records
Infor OS API rate limits throttle bulk migration throughput
Predefined migration sequences require consultant authorization to modify
EDI trading partner configuration is not in the primary data tables
Maintenance mode required for database-level exports
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 VISUAL schema and extract master data
We connect to VISUAL's database (on-premise) or query via ION API to inventory all master data tables: customers, vendors, inventory items, BOMs, routings, and work centers. We identify custom fields, user-defined tables, and any extended properties. The output is a Source Data Inventory document listing each table, row count, and field count—used to scope the migration plan and identify which tables require transformation rather than direct mapping.
Map VISUAL objects to Acumatica schema
Using the Source Data Inventory, we create an Object Mapping Specification covering every object pair: Customer→Customer, Inventory Item→Stock/Non-Stock, Work Order→Production Order, BOM→BOM, Routing→Work Center, Sales Order→Sales Order, Purchase Order→Purchase Order, and Invoice→AR/AP Invoice. For split mappings and transformed mappings, we document the transformation logic, any custom fields required in Acumatica, and value translation tables for status codes and enumerated fields.
Set up Acumatica schema before data migration
Before any data moves, we create the necessary Acumatica configuration: Item Classes, Warehouse definitions, Work Centers, Labor Codes, Overhead Codes, Terms, Shipping Terms, Customer Classes, Vendor Classes, and BOM Revisions. Custom fields identified in the mapping step are added via Acumatica's Customization Project framework. This ensures all foreign key lookups (TermsID, InventoryCD, WorkCenterID) exist when data loads begin, preventing constraint violations.
Export, clean, and load master data and transactions
Master data (customers, vendors, inventory items, BOMs, routings) loads first in dependency order. We clean duplicates, standardize date formats, resolve foreign key references, and apply value mappings for status codes, terms, and item classes. Transactions (work orders, sales orders, purchase orders, invoices) follow, with open records loaded first for go-live readiness. Each batch is validated against Acumatica's schema constraints before the next batch begins.
Run production test migration and field-level diff
A representative slice (typically 500–2,000 records spanning customers, inventory, work orders, and invoices) migrates first. We generate a field-level comparison report between VISUAL source and Acumatica destination for each record type. You review the diff to confirm BOM decomposition, work order status mapping, and cost field placement before committing the full dataset to migration.
Execute full migration with delta pickup and go-live
The full dataset migrates against Acumatica. A delta-pickup window (24–48 hours) captures any VISUAL records modified during the cutover. After migration, we disable Acumatica's Migration Mode in a controlled step, validate GL trial balance against VISUAL's cost layer, and confirm Production Order quantities match VISUAL work order quantities. An audit log records every record operation, and one-click rollback is available if reconciliation uncovers discrepancies.
Platform deep dives
Infor VISUAL
Source
Strengths
Weaknesses
Acumatica
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 2 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 Infor VISUAL and Acumatica.
Object compatibility
2 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
Infor VISUAL: 250K–6.25M executions/month depending on tier; peak 3,000–15,000 req/min.
Data volume sensitivity
Infor VISUAL 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 Infor VISUAL to Acumatica migration scoping. Not seeing yours? Book a call.
Walk through your Infor VISUAL 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 Infor VISUAL
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.