Migrate from Open-Prod to Acumatica

Open-Prod customer records map 1:1 to Acumatica Customers. Primary address, shipping address, and contact information migrate to the corresponding Acumatica address and contact tabs. Tax zone assignment requires a lookup against Acumatica's Tax Zones screen — customers without a tax zone are flagged for manual assignment before go-live.

Open-Prod vendor records map to Acumatica Vendors. Remit-to address and AP account assignment migrate. Acumatica requires each vendor to have a Tax Registration ID and a primary payment term; vendors missing these fields are flagged for manual setup before the vendor record activates in Acumatica.

Open-Prod products map to Acumatica Inventory Items. Because Acumatica tracks inventory at the product-location combination, a single Open-Prod product may generate multiple Stock Item records — one per warehouse location where stock exists in Open-Prod. We distribute quantities proportionally across Acumatica warehouse locations based on Open-Prod's location allocation data.

Open-Prod warehouse records map to Acumatica Warehouses. Each warehouse has a LocationID structure within Acumatica; if Open-Prod uses bin-level tracking, we map bins to Acumatica Location records under the corresponding Warehouse. The warehouse-level settings for posting class and default values are preserved.

Open-Prod sales orders migrate to Acumatica Sales Orders with all line items, quantities, unit prices, and discount amounts preserved. Order status (Open, Completed, Cancelled) maps to Acumatica's order status field. Original order dates and promised ship dates are preserved in custom datetime fields since Acumatica sets its own CreatedDateTime at migration time.

Open-Prod AR invoices map to Acumatica AR Invoices with original invoice dates, due dates, terms, and line items. The Accounts Receivable account assignment comes from Acumatica's Cash Account map. Invoices with payments applied in Open-Prod carry the payment records as AR Payments in Acumatica.

Open-Prod vendor bills map to Acumatica AP Bills with original invoice dates, terms, and line items. The Accounts Payable account maps from Acumatica's Cash Account configuration. Prepaid and prepayment records migrate as AP Payments; vendor prepayments applied to specific bills require reconciliation during migration validation.

Open-Prod chart of accounts entries map to Acumatica Accounts. Acumatica's segmented account code structure requires reformatting Open-Prod flat account numbers — we parse the account number and populate each segment according to the Acumatica dimension definitions your team configures before migration. Active/inactive status and account type map directly.

Open-Prod journal entries map to Acumatica GL Batches with individual debit and credit lines as GL Entries. Every Acumatica journal entry must balance (total debits equals total credits) — we validate balance before import and flag any unbalanced entries for review. Source module and reference fields are preserved in the Batch description and entry details.

Open-Prod purchase orders migrate to Acumatica Purchase Orders with vendor assignment, line items, quantities, and expected dates. Receipts and shipments linked to the PO in Open-Prod migrate as separate receipt and shipment records in Acumatica, linked to the PO via the POLineNbr reference.

Open-Prod project or job records map to Acumatica Projects with project status, manager assignment, and dates. Project phases and tasks migrate as sub-records under the Project using the TaskID structure. Budget amounts for each cost code migrate to Project Budget lines; we preserve the original budget version and any approved revisions as separate budget revisions.

Lot and serial number records in Open-Prod map to Acumatica Lot/Serial items. If Open-Prod tracks lot expiration dates, these migrate to LotSerialNbr.ExpirationDate in Acumatica. Lot assignments on existing inventory transactions are preserved via the LotSerialNbr field on the corresponding GL or inventory entry.

Open-Prod user accounts that represent employees with system access map to Acumatica Users, matched by email address. Open-Prod contact records that are business contacts map to Acumatica Contacts. A contact that is also a system user gets both records linked via the same email key. Contacts without an email receive a generated identifier for manual linking.

Open-Prod custom entities that store data as records migrate as custom tables in Acumatica using the Usr-prefixed DAC structure. Open-Prod custom fields stored as additional columns migrate as custom fields registered in the Acumatica Customization Project with the appropriate field type. Business logic and computed fields encoded in Open-Prod scripts do not migrate and must be rebuilt in Acumatica.