Migrate from Perfecto ERP to Acumatica

Perfecto ERP's Chart of Accounts maps directly to Acumatica GLAccount entity. Account code (AccountCD) and description migrate 1:1. Account type (Asset, Liability, Equity, Revenue, Expense) requires value mapping to Acumatica's account type enumeration. Inactive flags in Perfecto ERP map to Active = false in Acumatica.

Historical GL transactions from Perfecto ERP's General Ledger migrate to Acumatica GLTran records. Each Perfecto ERP journal entry becomes a batch (BatchModule = GL) with multiple transactions. Original entry date preserved as TranDate; user who created entry resolved by email match to Acumatica Employees.

Perfecto ERP stores party data in a single entity that serves both customers and vendors. Acumatica separates these into Customer and Vendor entities with distinct NbrSeq numbering. We split on PartyType flag if present in export; otherwise, we create both Customer and Vendor records for each party and cross-link them.

Perfecto ERP's address and contact fields on party records map to Acumatica Address and Contact entities linked via ContactID. Multiple addresses per party (billing, shipping) become separate Address records with AddressType = 'Billing' or 'Shipping'. Primary contact email migrates to Contact's Email field.

Perfecto ERP inventory items with ItemNbr, Description, UnitCost map to Acumatica InventoryItem with InventoryCD, Description, ItemStatus = 'Active'. Valuation method (FIFO, Average, Standard) from Perfecto ERP maps to ValMethod field; if unspecified, DefaultValMethod from Acumatica Inventory Preferences applies. Item class and stock/non-stock designation migrate as ItemClassID and ItemType respectively.

Perfecto ERP warehouse or location codes become Acumatica Warehouse records with WarehouseCD and Name. Physical address of warehouse maps to Address entity linked to Warehouse. Multiple sites in Perfecto ERP become separate Warehouse records with SiteID as the Acumatica identifier.

Open and historical sales orders from Perfecto ERP migrate to Acumatica SOOrder. OrderNbr becomes OrderNbr, CustomerOrderNbr holds the original Perfecto ERP order number. Line items with inventory item references resolve via InventoryCD match. Status maps: 'Open' to 'Open', 'Shipped' to 'Completed', 'Cancelled' to 'Cancelled'.

Purchase orders migrate to Acumatica POOrder with POType = 'Normal' for standard POs. Vendor reference comes from the Vendor record created during party migration. Line items with vendor part numbers preserved in POOrderDetails with VendorID and VendorLocation. Drop-ship and blanket PO types mapped accordingly based on Perfecto ERP order classification.

Perfecto ERP invoices flagged as customer invoices route to Acumatica ARInvoice; vendor invoices route to APInvoice. InvoiceNbr becomes RefNbr; original document date becomes DocDate. Balance due maps to CuryOrigDocAmt with CuryID set per currency. Prepayments preserved as separate document types.

Employee records from Perfecto ERP's HR module migrate to Acumatica Employee with EmployeeID, FirstName, LastName, Department, Position. Employment status (Active, Terminated) maps to EmployeeStatus. Email address preserved for Acumatica User account linking. Compensation fields migrate as UDFs if present. Employee branches and payment methods require separate configuration in Acumatica HR settings.

Perfecto ERP manufacturing BOMs map to Acumatica BOMHead with BOMID and description. Component items with quantity-per assemble map to BOMDetail with BOMLineNbr, ComponentID (InventoryCD), QtyBasis, and ScrapFactor. Phantom BOMs if supported in Perfecto ERP become BOMLevel = 0. BOM revisions and alternate BOMs preserved as separate BOMHead records with revision sequence numbers.

Any Perfecto ERP custom fields defined via End-User Customization Studio that lack standard equivalents become Acumatica UDFs. UDFs created as custom fields on the target DAC (e.g., Customer with UsrCustomField) using Acumatica's customization framework. Field type preserved: string fields become Text, numeric fields become Number, dates become Date.

Perfecto ERP's Approval Workflows are business process configurations, not transactional data. These do not export as records and cannot migrate to Acumatica. We document the Perfecto ERP workflow definitions (approval chains, thresholds, routing rules) as a configuration reference for rebuilding in Acumatica's Automation Engine.

File attachments associated with Perfecto ERP records (invoices, orders, inventory items) are extracted and re-uploaded to Acumatica. Files attach to NoteDoc records linked to the target entity via NoteID. Original file names and upload timestamps preserved. Acumatica's file size limit (default 50MB per file) applies.