Migrate from Elvis Business ERP to Acumatica

Elvis Customer records map directly to Acumatica Customer DAC. Acumatica requires a primary Location record per Customer — Elvis address records are consolidated into a single Location with the most-recent address preserved, additional addresses captured as a custom reference field.

Elvis Vendor records map to Acumatica Vendor DAC. Vendor payment terms and tax ID values are mapped value-by-value to Acumatica's Terms and TaxZone codes. Remit-to addresses migrate as secondary Location records under the Vendor. Each vendor's primary contact is linked via the Contact entity, and default shipping preferences are captured as UDFs for downstream processing.

Elvis Inventory Item maps to Acumatica InventoryItem DAC with ItemType distinguishing stock vs. non-stock. Elvis's item class or category maps to Acumatica's StockCategory field for reporting grouping. BOM structures are preserved as a custom reference note since Acumatica uses a separate Bill of Materials DAC.

Elvis GL Account codes map to Acumatica Account records. The AccountType (Asset, Liability, Expense, Income) maps to Acumatica's Account Class field. Subaccounts in Elvis map to Acumatica Subaccount segments — the segment count is preserved from the Elvis chart of accounts configuration.

Elvis invoices map to Acumatica ARInvoice lines. The original invoice date and invoice number are preserved in the DocumentRef and DocDate fields respectively. Elvis invoice-level discounts map to Acumatica's discount line structure; terms-based discounts use the Customer's payment terms lookup.

Elvis PO and AP records map to Acumatica APInvoice. Line-level item references resolve to InventoryItem lookups; direct purchases without inventory links use a generic expense account override field. PO statuses (Open, Closed, Cancelled) map to Acumatica's Hold and PendingAP flags.

Elvis cash receipts map to Acumatica Payment records applied against the corresponding ARInvoice via the ApplyToRefNbr field. Elvis payment method (check, ACH, credit card) maps to Acumatica's CashAccount and PaymentMethod lookups. If the original receipt includes a reference number, it is preserved as a custom UDF for audit trail purposes and to support future reconciliation queries.

Elvis inventory adjustment transactions map to Acumatica InventoryAdjustment records. The adjustment reason code from Elvis is stored as a custom ReasonCode__c UDF in Acumatica. If the adjustment references a specific batch or cycle count, that reference is preserved in the transaction note field.

Elvis custom object types map to Acumatica custom objects using the Customization Manager. Elvis's relationship fields (many-to-many or one-to-many) require Acumatica junction table DACs when the source uses N:N link tables. The migration plan surfaces the Elvis relationship schema before Acumatica schema is built.

Elvis user records map to Acumatica Employees (Employee DAC) and Users (Users table) resolved by email match. Elvis owner IDs on transactions are resolved to Acumatica Employees by email lookup; unmatched owners are flagged before migration for manual assignment and a detailed log is generated for the admin team.

Each Elvis custom field is created as a UDF in Acumatica via the Customization Manager before data lands. Field type parity is enforced — pick-list fields from Elvis become Acumatica attribute groups, numeric UDFs map to Decimal fields, and date UDFs map to Acumatica Date fields.

Elvis location and address records map to Acumatica Location under the parent Customer or Vendor. Elvis's flat address model is restructured into Location records with address line, city, state, postal code, and country fields. Elvis's primary address flag becomes the IsDefaultLocation flag in Acumatica.