Migrate from Edara to Acumatica

Edara's Customer master maps directly to Acumatica's Business Account. Acumatica splits contact details into separate Locations (addresses) and Contacts (people) linked to the account. Primary AR terms, credit limit, and tax zone from Edara map to the Account's Terms, Credit Limit, and Tax Zone fields. We preserve the original Edara customer ID in a custom Source_ID__c field on the Account for reconciliation.

Edara's Vendor master maps to Acumatica's Business Account flagged as a vendor. AP terms, payment method, and tax ID from Edara map to the corresponding vendor-specific fields. Multiple Edara vendor contacts map to Acumatica's Vendor Contacts table linked by email match. We flag any Edara vendor that is also a customer for manual Acumatica review before creating a combined account.

Edara's Item master branches into Acumatica's Stock Item (for inventory-tracked goods) or Non-Stock Item (for services and dropship goods). Item type, lot/serial settings, and warehouse-specific default locations from Edara are mapped to Acumatica's Item Class (IN201000) and Item warehouse settings. We surface the full Edara item attribute set before assigning Stock vs. Non-Stock classification.

Edara's warehouse locations map 1:1 to Acumatica Warehouses (WH204000). Edara BIN locations within a warehouse map to Acumatica's BIN IDs under the same warehouse. If Edara tracks lot numbers, we map those to Acumatica's Lot/Serial classes (IN204000) — the Ultimate tier with MTO manufacturing also maps Edara bill-of-materials to Acumatica's Bill of Materials (AM208000).

Edara sales orders map to Acumatica Sales Orders with line-level item, quantity, unit price, warehouse, and discount detail preserved. Order status, shipment linkage, and customer reference number are carried into SO301000. If Edara tracks multiple shipments per order, we create multiple Acumatica shipments and link them to the parent order. Payment terms on the order map to the customer account's default terms unless overridden at order level.

Edara purchase orders map to Acumatica Purchase Orders with vendor, line items, quantities, and receipt warehouse preserved. The receipt-linked status in Edara maps to Acumatica's PO receipt workflow — we create the corresponding AP bill (AP301000) record after receipt is confirmed. Drop-ship purchase orders are flagged with the IsDropShip flag on the PO line.

Edara AR invoices map to Acumatica AR Invoices (AR301000) with line items, tax amounts, payment terms, and document references preserved. If an Edara invoice is linked to a sales order, we link the Acumatica invoice to the corresponding Sales Order. Overdue charges from Edara are not automatically generated in Acumatica — we flag these for manual review of Acumatica's Finance Charge policy configuration.

Edara AP bills map to Acumatica AP Bills (AP301000). Vendor invoice number, invoice date, due date, and line expenses map directly. Prepayments recorded in Edara are mapped to Acumatica's Prepayment Application screen for manual application against the vendor bill. Tax codes from Edara are mapped to Acumatica's tax zone and tax category combination per vendor location.

Edara's flat account list maps to Acumatica's GL Account structure with subaccounts as a separate dimensional axis. Each Edara account gets a primary Acumatica account; if Edara uses cost-center tags on transactions, we create corresponding subaccounts in Acumatica. Active vs. inactive status is preserved. Account types (Asset, Liability, Equity, Revenue, Expense) map directly to Acumatica's Account Class field.

Edara customer receipts map to Acumatica Customer Payments (AR302000) applied against the corresponding AR invoice. Payment method, check number, and payment date are preserved. If the Edara receipt was applied to multiple invoices, we create multiple application lines in Acumatica, each referencing the appropriate invoice and amount. Unapplied balances become hold payments for manual allocation.

Edara Fixed Assets (Ultimate tier feature) map to Acumatica Fixed Assets (FA202000). Asset description, acquisition date, acquisition cost, depreciation method, and useful life are preserved. Depreciation schedules are recalculated in Acumatica based on the original acquisition date and method — we capture the net book value from Edara as the opening balance for the Acumatica asset register.

Edara custom properties on any entity (Customer, Vendor, Item, Order) require an Acumatica Customization Project to be created and published before migration. Each Edara property is evaluated for data type: text fields become String fields, numeric fields become Decimal or Integer fields, pick-list fields become Combo fields with the Edara values as options. The Customization Project must be published per Acumatica tenant before field-level data can be inserted.

Edara employee records (if included in the migration scope) map to Acumatica Employees (EP203010). Name, email, department, employment status, and manager hierarchy are carried over. Acumatica employees have additional attributes (labor item, timecard settings) that are not in Edara — these default to company settings unless otherwise specified.