Migrate from Edara to Epicor Prophet 21

Edara's chart of accounts maps 1:1 to Epicor's GL Account table. Account codes, names, types (Asset, Liability, Equity, Revenue, Expense), and active/inactive status transfer directly. We preserve the full account hierarchy so that Epicor's segment structure (typically Company-Division-Department or similar) can be mapped from Edara's account code segments. If Edara uses a flat account code structure, we create a standard Epicor segment configuration during setup.

Edara Customer records map to Epicor Customer with billing/shipping addresses, contact information, payment terms, and customer currency assignments preserved. We flag any custom customer properties (customer-specific discounts, credit limits, salesperson assignments) for mapping to Epicor Customer UD fields or UserDefined fields. Duplicate detection runs on CustomerName and TaxID before insert to avoid Epicor constraint violations.

Edara Vendor master records map to Epicor Vendor with addresses, tax IDs, default payment terms, and buyer assignments preserved. We reconcile vendor names for duplicates before insert and flag any vendor-specific PO markup fields requiring mapping to Epicor's VendorUPSData or UserDefined tables.

Edara Item master records map to Epicor Part. SKU, description, cost, price, unit-of-measure conversions, inventory valuation method (FIFO, LIFO, Average), and warehouse assignments transfer directly. We flag any custom item properties (vendor-specific pricing, barcode associations, lot-control settings) for Epicor Part UD fields. If Edara uses Lot or Serial tracking, we map to Epicor's Lot/Serial number tables and preserve traceability data.

Edara warehouse records and per-warehouse stock levels map to Epicor Warehouse and PartWhse. Bin locations and bin-level quantities transfer where Edara stores them. We flag negative stock entries in Edara for the customer's operations team to resolve before committing to Epicor, because Epicor's inventory valuation may reject or flag negative quantities depending on site configuration. Multi-warehouse setups in Edara map directly to Epicor's site-warehouse hierarchy.

Edara open AR aging maps to Epicor AR Invoice and AR Adjustment records. Outstanding invoice amounts, due dates, and currency assignments transfer. We export Edara's AR aging report and map each open document to Epicor's InvoiceNum or an AR Adjustment with a reason code. Any open credit memos map to Epicor CMemo records. Currency conversion records are preserved from Edara's multi-currency exchange rate history so that the outstanding balance in Epicor matches the original transaction currency and converted amounts.

Edara open AP aging maps to Epicor AP Invoice and AP Adjustment records using the same approach as AR. Outstanding PO-linked invoices are matched to Epicor's PO Receipt records. Vendor-held credits map to Epicor VendorPP records. Multi-currency AP documents carry exchange rate history to preserve original and converted amounts.

Edara open and closed sales orders map to Epicor OrderHed and OrderDtl. Line items, quantities, pricing, discounts, and salesperson assignments transfer. For Pro-plan Edara customers with more than 30,000 orders in the migration window, we detect the cap during discovery and stage extraction in monthly batches aligned with Edara's billing cycle. Closed orders transfer as historical records with OrderOpen = false; open orders retain their status for fulfillment continuity.

Edara purchase orders map to Epicor POHeader and PODetail. Vendor assignments, line items, quantities, unit costs, approval status, and linked receipt records transfer. We preserve PO approval workflows as notes in Epicor's PO approval fields for the customer's admin to reconfigure in Epicor's approval routing.

Fixed asset records including acquisition cost, accumulated depreciation, depreciation method, and useful life are only fully accessible on Edara Ultimate. We export the depreciation schedule from the trial balance and Edara's financial reports where Ultimate API access is not available, reconcile the asset register against the general ledger, and flag any discrepancy for the customer's accountant to resolve before committing the asset ledger to Epicor. Once reconciled, assets map to Epicor's Asset table with depreciation method and book values preserved.

Edara POS register configurations and per-register billing metadata have no native Epicor equivalent. Epicor's POS and retail modules are limited compared to its manufacturing depth. We export POS register definitions, salesperson assignments, and register-to-location mappings as a written inventory document for the customer's admin to reconfigure in Epicor or a separate POS solution post-migration. The per-register billing structure ($29 base + $17/register) does not map to Epicor's pricing model.

Edara multi-currency data (available on Pro and above) maps to Epicor Currency and Exchange Rate tables. We export exchange rate history alongside transactional data so that converted amounts in Epicor match the original Edara records. If Edara holds open AR/AP in multiple currencies, the exchange rate at document date is preserved on each migrated document to avoid Epicor's current-rate revaluation from creating phantom gains or losses at migration cutover.