Migrate from Visibility ERP to Acumatica

Visibility Customer records map directly to Acumatica Customers. The key transformation is remapping Visibility's customer class codes to Acumatica Customer Class codes, which control credit limits, payment terms, and statement settings per customer group. Address records transfer as Location records under each Customer, and primary contact information populates the Contact subtab for each customer location.

Vendor records carry over with direct mapping. Visibility's vendor class codes map to Acumatica Vendor Class records, which define default terms, tax zone assignments, and remittance settings. Multi-address vendors in Visibility become Vendor Locations in Acumatica, with the primary remittance address set as the default for AP payment processing.

Visibility inventory items can be stock, non-stock, or kit items. Acumatica distinguishes between Stock Items (tracked in warehouses) and Non-Stock Items (expensed or used in manufacturing). Kit and assembly items in Visibility map to Acumatica's Manufacturing/bill of materials model or distribution kit groups.

Visibility BOM structures map to Acumatica BOMs with material lines, overhead costs, and revision control. BOM versions in Visibility (revision history) migrate as Acumatica BOM revisions linked by revision ID and effective date. Phantom BOMs in Visibility map to Acumatica phantom assemblies.

Visibility work orders map to Acumatica Production Orders. The status, priority, and estimated completion fields translate to Acumatica's production order states (pending, in-process, completed, closed). Open work orders migrate as in-progress production orders with material allocations and labor bookings preserved.

Open Sales Orders migrate as active Acumatica Sales Orders with line items, quantities, promised dates, and warehouse assignments. Visibility's multi-warehouse order allocation maps to Acumatica's warehouse fulfillment logic. Closed orders migrate as historical records in AR Invoice history.

Open Purchase Orders map directly to Acumatica Purchase Orders with line items, quantities, promised dates, and vendor location assignments. Visibility's PO line types (goods, services, special) map to Acumatica line types that determine posting behavior in AP. Line-level cost codes and routing information transfer to Acumatica's extended description and reference fields.

Visibility GL accounts map to Acumatica Chart of Accounts entries. Account numbers and descriptions transfer directly. Visibility's account segment structure (division, department, cost center) must map to Acumatica's segment definitions if using a multi-segment chart of accounts. Active and inactive status flags carry over to control account availability in new transactions.

Open AP invoices migrate as unpaid Acumatica AP documents with original invoice dates, vendor references, and due dates preserved. Visibility's invoice hold status maps to Acumatica's hold flag on AP Invoice. Historical paid invoices migrate to AP Register history, and fully reconciled invoices are archived with payment reference numbers intact.

Open AR invoices migrate as active Acumatica AR documents with customer references, invoice dates, and due dates intact. Visibility's billing terms and customer-specific payment schedules map to Acumatica's terms and customer-specific payment settings. Historical invoices migrate to AR Register history with payment application records preserved.

Visibility inventory issues, receipts, and adjustments map to Acumatica's Inventory Receipt and Issue transactions. Each Visibility transaction generates one or more Acumatica IN Register entries. Transaction dates and warehouse locations are preserved. Lot and serial number history carries forward.

Visibility project or job records map to Acumatica Projects with customer association, status, budget, and billing rules. Visibility's change order records migrate as Acumatica change orders within the project. Project-specific inventory allocations map to Project Supply lines in Acumatica. Project template records transfer as inactive templates available for new project creation.

Visibility UDFs on any object migrate to Acumatica custom fields using Acumatica's schema extension API. Each UDF's data type (text, number, date, list) determines the Acumatica field type. Custom fields appear automatically in Generic Inquiries and report designer after creation, and they persist through Acumatica version upgrades.

Documents and file attachments linked to Visibility records (work orders, customers, inventory items) re-upload to Acumatica's file storage linked to the corresponding record. The original filename, upload date, and linked entity are preserved in Acumatica's document management.

Visibility workflows, alert rules, and automated actions do not migrate. These must be rebuilt in Acumatica using Generic Inquiries for alerts, Automation Schedules for batch processing, and Acumatica's workflow designer for approval chains. We provide an export of Visibility workflow definitions as a rebuild reference so your team can reconstruct the logic in Acumatica.