Migrate from PrismERP to Acumatica

PrismERP Customer Master stores all customer details including addresses, contacts, banking info, and credit terms. Maps directly to Acumatica's Customer DAC (AR303000). Payment terms, credit limit, and tax zone fields on the PrismERP customer record map to Acumatica Customer class attributes — CR202000 is the screen where migrated customer records land for tax-zone assignment.

PrismERP's vendor master (the Accounts Payable counterpart to Customer Master) maps to Acumatica's Vendor DAC. Vendor-type classification in PrismERP (e.g., goods vs. services vendor) translates to the Acumatica Vendor Class field which controls AP settings. Remittance contact details and 1099 settings from PrismERP populate Acumatica's Vendor Details tab.

PrismERP items classified as stocked inventory route to Acumatica Stock Item (IN202500) with warehouse-specific quantity and location tracking; non-stocked items purchased for resale or consumed as expense map to Non-Stock Item (IN202000). PrismERP item-specific cost layers (FIFO or average) must be declared in Acumatica's Inventory Valuation method field per item class. Item-specific GL accounts for cost of goods sold and inventory clearing are mapped via the Acumatica item class.

PrismERP account codes are single-level alphanumeric strings. Acumatica enforces a segmented account structure — Account segment plus mandatory Subaccount segment. We decompose each PrismERP account code into an Acumatica Account code and a derived Subaccount, preserving the original account description and active/inactive status. The mapping table is delivered as an import-ready Acumatica CSV before the GL migration runs.

PrismERP stores all financial postings as vouchers with debit and credit lines linked to account codes. Each voucher maps to an Acumatica GL Journal Transaction batch. The original voucher number becomes the batch reference, posting date is preserved, and the source module tag (AP, AR, INV, FA) is stored as a custom text field on the batch for reconciliation traceability. Historical periods are migrated first to establish opening balances before open-period transactions.

PrismERP AR invoices carry customer reference, invoice date, due date, terms, and line items. These map to Acumatica AR Invoices. The PrismERP payment terms code (e.g., Net 30) maps to the Acumatica Payment Term object, which controls discount availability and due date calculation. Partial payments received in PrismERP before migration cutover must be reflected as separate AR Payment applications in Acumatica.

PrismERP AP bills with vendor, invoice number, date, and expense lines map to Acumatica AP Bills. The PrismERP vendor invoice reference number becomes the Acumatica Bill document number or reference number depending on your numbering sequence setup. Hold status and approval flags from PrismERP AP are not transferable — AP bills land as active documents in Acumatica and require manual re-release if approval workflows were in place.

PrismERP purchase orders with vendor, line items, quantities, and promised dates map to Acumatica Purchase Orders. Open and closed status is preserved. Lines with received-but-not-invoiced quantities in PrismERP require a separate receiving transaction in Acumatica's PO Receipts screen before the PO can be closed — this is flagged during the migration plan so your AP team is prepared at cutover.

PrismERP Sales & Distribution orders with customer, line items, quantities, and warehouse fulfillment data map to Acumatica Sales Orders. The PrismERP order status (open, partially shipped, closed) translates to Acumatica SO status flags. Taxes applied at order entry in PrismERP map to Acumatica tax zone and tax category assignments per line — tax calculation in Acumatica uses the destination tax engine, so legacy tax amounts are preserved as a reference column on the order.

PrismERP's Approval Workflow Management configures multi-step routing per module with thresholds and escalation rules. Acumatica has no equivalent module-level approval engine — these rules must be rebuilt in Acumatica using generic inquiries to identify records needing approval, automation schedules to trigger notifications, and manual approval screens per document type. We export the PrismERP workflow definitions as a reference document for your Acumatica administrator to use during the rebuild phase.

PrismERP extends its standard entities with module-specific custom properties stored as additional columns in the export. Each PrismERP custom property in a financial or inventory module requires an Acumatica custom field defined in a customization project and published to the target DAC. Fields must be published before the migration data loads — we deliver the field definition list first so your Acumatica admin can publish them ahead of the data migration run.

PrismERP's Document Management System stores files attached to vouchers, orders, and customer records. Files are downloaded from PrismERP's document store and re-uploaded to Acumatica as attachments on the matching document records (e.g., PO attachments on PO301000, customer attachments on AR303000). File size limits of 25 MB per file in Acumatica apply — files exceeding this are split or stored as zipped archives with a reference note.

PrismERP Production Planning & Control BOMs and production orders require translation to Acumatica Manufacturing BOM revision structures and Production Order documents. PrismERP BOM lines with scrap percentages map to Acumatica BOM line operation step waste settings. Work center capacities from PrismERP are not natively supported in Acumatica Manufacturing's default configuration — we surface them as notes on the Acumatica Work Center records for manual reference after migration.

PrismERP Project System records with customer association, budget lines, and billing schedules map to Acumatica Projects. Project status (active, completed, on-hold) carries over as the Acumatica PM status. Budget-to-actual tracking from PrismERP maps to Acumatica's project commit and actual amounts — however, PrismERP's project cost capturing model (time-and-materials vs. fixed-fee) must be declared as the Acumatica billing rule type during migration.