Migrate from Accolent ERP to Epicor Prophet 21

Accolent Customer records with billing/shipping addresses, contact details, and account type flags map to Epicor's Customer table. We extract all address records, contact persons, and payment term codes from Accolent's customer master and insert into Epicor's CustTable, preserving the Accolent account number as an external reference field for dedupe. Tax exempt flags map to Epicor's Tax Exempt check box and related Tax Grp ID.

Accolent Vendor records including address, payment terms, and PO defaults map to Epicor's Vendor table. The Accolent vendor code becomes Epicor's Vendor ID, and the primary contact maps to the Epicor VendorPP contact record. Payment term codes (NET 30, NET 60) require cross-reference to Epicor's PaymentTerms table during mapping.

Accolent Items (products and inventory) with multiple warehouse locations, cost layers, reorder points, and BOM links map to Epicor's Part table. We map Accolent's unit of measure and pricing tiers to Epicor's Part UOM conversions and Price Lists. Part Type (inventory vs non-inventory vs service) maps to Epicor's TypeCode field. Stocking uom and purchasing uom differences between the two systems require UOM class mapping during the transform phase.

Accolent Sales Orders with line items, pricing, and fulfillment status map to Epicor OrderHed (order header) and OrderDtl (order detail). We extract fulfilled vs open status and set Epicor's OrderRel records accordingly. Accolent order total and tax amounts map to Epicor OrderHed fields; line-level pricing including discount percentages map to OrderDtl.UnitPrice and DiscountPercent fields. Open orders are prioritized in migration; historical orders are loaded with a closed status.

Accolent Purchase Order records with vendor references, line items, and receipt status map to Epicor POHeader and PODetail. Receipt-stage flagging (pending, partial, complete) maps to Epicor's PORel (PO release) status. Accolent PO defaults for terms and shipping instructions map to POHeader fields during import.

Accolent's structured GL chart with account numbers, names, types (Asset, Liability, Expense, Revenue), and cost-center assignments maps to Epicor's GLAccount table and associated COAC (Chart of Accounts Control). Account codes map directly where the numbering scheme is compatible; alphanumeric Accolent codes require mapping to Epicor's natural account + department + division structure if the destination uses a segment-based COA.

Historical Accolent GL transactions (date, account, debit/credit amounts, source references) map to Epicor GLJrnHed and GLJrnLine. We preserve original posting dates and map the Accolent source module to an Epicor JournalCode. Migrations that scope historical GL data require significant transform work because Accolent stores accounts as numeric codes while Epicor uses the full COAC segment key. We recommend loading only the current fiscal year plus one prior year unless the customer specifically requires full history.

Outstanding Accolent AP and AR invoices represent live payables and receivables that cannot be re-invoiced in the destination — they must land as existing open balances. We extract invoice and credit-memo headers with outstanding amounts from Accolent and map them to Epicor's open-balance mechanism using APInvHed with InvoiceType = Credit Memo for AR credit memos and ARInvcHead with OpenInvoice = true for open AR. We flag any record where the original invoice date exceeds 90 days past for customer review before committing. Accolent does not expose a dedicated AP/AR aging export, so we reconstruct aging from invoice header and payment records.

Accolent fixed asset records including acquisition cost, depreciation method, accumulated depreciation, and asset class map to Epicor FAAsset. We extract the current book value and remaining depreciable life, creating Epicor FAAssetBook records with the appropriate depreciation method and convention. Asset class codes map to Epicor Asset Group codes.

Accolent tax codes with rates and applicability rules map to Epicor's SalesTax and TaxGRp tables. We extract the full tax code master and map each Accolent jurisdiction to an Epicor Tax Juris record. Any jurisdiction-specific codes (states, provinces, or local tax districts not present in Accolent) are flagged for the customer's admin to configure in Epicor before go-live.

Accolent multi-level BOMs with parent-component-quantity relationships, routing steps, work-center assignments, and phantom BOM flags map to Epicor PartBOM. We extract the full Accolent BOM tree, flatten multi-level structures into Epicor's single-level PartBOM with revision control, and flag any BOM exceeding three levels for manual review before loading to prevent circular-reference errors in Epicor's MRP system. Phantom assembly flags map to Epicor's ProcessMfg check box and BOM type designation.

Accolent multi-warehouse site definitions with bin/shelf location codes map to Epicor Warehse and WarehseBin tables. We extract warehouse IDs and bin codes from Accolent and create corresponding Epicor warehouse records, then populate bin locations. Inventory quantities per warehouse are loaded as PartWhse records tied to each Part after the Part and Warehse tables are committed.

Accolent work orders with production steps and material requirements map to Epicor JobHead, JobMtl, and JobOper records. Accolent's manufacturing order header maps to JobHead; component lines with quantities and operation steps map to JobMtl and JobOper. Job status (released, complete, closed) maps to Epicor JobHead.JobReleased, JobComplete, and JobClose fields.

Accolent user accounts with role assignments and access-control flags map to Epicor UserFile and related security tables. We extract user records and role definitions, then create Epicor User records with matching role associations. Accolent role names are mapped to Epicor Security Role names during the transform phase, with any unmapped roles flagged for the customer's admin to assign in Epicor before production migration.

Accolent stores documents and file attachments associated with orders, items, and customers. The platform does not expose a documented file-retrieval API or export mechanism. We do not migrate attachments or documents. The customer's admin retains access to Accolent in read-only mode for document retrieval post-migration or archives documents independently before the cutover date.