ERP migration

Migrate from Infor VISUAL to Acumatica

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

Infor VISUAL logo

Infor VISUAL

Source

Acumatica

Destination

Acumatica logo

Compatibility

92%

12 of 13

objects map 1:1 between Infor VISUAL and Acumatica.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Infor VISUAL logo

Infor VISUAL

What's pushing teams away

  • Long implementation timelines (averaging 4 months per G2) and the need for qualified consultants create sticker shock and project fatigue for mid-market buyers.
  • Performance degrades under high transaction volume or complex multi-level BOMs, requiring ongoing tuning that smaller IT teams cannot sustain independently.
  • Pricing opacity — no public list price — forces buyers into a sales-driven negotiation where upsell add-ons are revealed post-contract.
  • When companies outgrow make-to-order workflows and need configure-to-order or engineer-to-order capabilities, VISUAL's feature set becomes a ceiling rather than a foundation.

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 Infor VISUAL objects map to Acumatica

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

maps to

Acumatica

Customer

1:1
Fully supported

VISUAL 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

maps to

Acumatica

Vendor

1:1
Fully supported

VISUAL 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

maps to

Acumatica

Stock Item / Non-Stock Item

1:many
Fully supported

VISUAL 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)

maps to

Acumatica

Bill of Materials

1:1
Fully supported

VISUAL 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

maps to

Acumatica

Work Center / Labor Code

1:1
Fully supported

VISUAL 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

maps to

Acumatica

Production Order

1:1
Fully supported

VISUAL 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

maps to

Acumatica

Material List (Production Order)

1:1
Fully supported

VISUAL 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

maps to

Acumatica

Labor Entry (Production Order)

1:1
Fully supported

VISUAL 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

maps to

Acumatica

Sales Order

1:1
Fully supported

VISUAL 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

maps to

Acumatica

Purchase Order

1:1
Fully supported

VISUAL 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

maps to

Acumatica

AR Invoice / AP Invoice

1:1
Fully supported

VISUAL 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

maps to

Acumatica

Quote

1:1
Fully supported

VISUAL 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

maps to

Acumatica

Custom Fields on Production Order

1:1
Fully supported

VISUAL'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.

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.

Infor VISUAL logo

Infor VISUAL gotchas

High

Work Order BOM attachment logic breaks if migrated as flat records

High

Infor OS API rate limits throttle bulk migration throughput

Medium

Predefined migration sequences require consultant authorization to modify

Medium

EDI trading partner configuration is not in the primary data tables

Low

Maintenance mode required for database-level exports

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

  • VISUAL BOMs with operation-scattered materials require decomposition

    Infor VISUAL assigns materials to the specific operation that consumes them—a material appears on the BOM record linked to an operation sequence number. Acumatica's Material List on a Production Order is not operation-scoped; materials are line items attached to the Production Order without inherent routing context. We handle this by extracting the operation-material mapping from VISUAL and creating a custom SourceOperation__c field on each Acumatica Material List line so the operation affinity is not lost. Acumatica's BOM revision model also requires pre-creation of BOMID and RevisionID before Production Orders can reference them.

  • VISUAL lacks a modern REST API for large-volume bulk export

    Infor VISUAL's primary data access path is through ION API Gateway with per-tier execution limits (250K/day on Essentials, 6.25M/day on Enterprise). For large manufacturing datasets—particularly transactional history spanning years—these limits may throttle extraction. We work around this by using VISUAL's database export capability where available (on-premise deployments) or by queuing bulk exports against ION API with retry-backoff. Acumatica's import framework can accept bulk CSV loads up to 100K rows per file, making destination-side intake faster than the source extraction step in many cases.

  • Acumatica's Migration Mode must be disabled before live posting

    Acumatica includes a Migration Mode flag (accessible in Preferences for each module) that suppresses inventory valuation updates, GL postings, and financial period validation during initial data load. While in Migration Mode, Production Orders cannot be released and invoices cannot be released for billing. We enable Migration Mode before migration begins, validate all data loads, then disable it in a controlled step once reconciliation is confirmed. Leaving Migration Mode on post-go-live causes financial reporting gaps because inventory movements and production transactions will not post to the GL.

  • VISUAL job-costing actuals have no native Acumatica equivalent

    VISUAL tracks actual cost against estimated cost per work order with per-operation labor and material actuals. Acumatica's standard production cost tracking records labor and material issues against a Work Center rate, but the per-order actuals comparison is a management-reporting construct that requires custom fields or a reporting project. We migrate actual cost history as EstimatedCost__c, ActualCost__c, and Variance__c custom fields on Production Order so financial reviewers can compare against standard costs without rebuilding from GL entries.

  • EDI transaction sets require manual reprocessing

    VISUAL supports ANSI X12 EDI transaction sets (850 PO, 810 Invoice, 856 ASN, 940 Warehouse Shipping Order) through its EDI module. Acumatica has a separate EDI Configuration workspace with its own mapping model. Raw EDI transaction data stored in VISUAL cannot be directly translated because Acumatica expects EDI data in its configured trading partner format. We extract EDI transaction history as reference documents and advise rebuilding EDI mappings in Acumatica's EDI Configuration using the extracted transaction data as a reference.

Migration approach

Six steps for a successful Infor VISUAL to Acumatica data migration

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

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

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

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

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

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

Context on both ends of the pair

Infor VISUAL logo

Infor VISUAL

Source

Strengths

  • Order-driven scheduling that respects both capacity and material availability simultaneously.
  • Built-in EDI (ANSI X12) support for customer orders, ASNs, and invoices without third-party middleware.
  • Work-order-centric design aligns with make-to-order and job-shop manufacturing workflows.
  • Real-time actual costing (FIFO, average, standard) integrated with production operations.
  • Integration ecosystem through Infor OS API Gateway with tiered rate limits.

Weaknesses

  • Pricing is opaque — no public list price and implementation costs vary by scope.
  • Implementation timelines average 4 months, driven largely by consultant dependency for configuration.
  • Performance issues reported under high transaction volumes or complex multi-level BOMs.
  • Limited migration tooling — Infor's own 2015 migration example document is the primary reference, suggesting manual and consultant-led processes.
  • Cloud and SaaS feature parity gaps compared to native Infor CloudSuite Industrial.
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. 2 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 Infor VISUAL and Acumatica.

  • Object compatibility

    B

    2 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

    Infor VISUAL: 250K–6.25M executions/month depending on tier; peak 3,000–15,000 req/min.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Infor VISUAL 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 Infor VISUAL to Acumatica data migrations

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

Can't find your answer?

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 consultation

Most VISUAL-to-Acumin migration timelines run 4–8 weeks for a complete dataset including master data, transactional history, and manufacturing artifacts (BOMs, routings). Small datasets under 50,000 transactional records can complete faster. The longest phase is typically BOM and routing mapping because VISUAL's operation-scattered material structure requires deliberate decomposition before Acumatica ingestion. Schedule planning should account for Acumatica schema setup and testing before any data moves.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Infor VISUAL.
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