Migrate from Accura to Epicor Prophet 21

Accura Customer records map to Epicor ERP Customer (Customer table) with the primary contact as a CustCnt record. Billing address and shipping address from Accura export as separate address columns; we split these into the Customer header address and one or more ShipTo records in Epicor. The Accura customer code becomes Epicor's CustNum as a string. Duplicate-name handling in Epicor uses CustNum as the unique key, not the company name, so we suppress Epicor's built-in duplicate warning during load and rely on the Accura customer ID as the dedupe anchor.

Accura Job records are the primary entity and map to Epicor ERP SalesOrder (for active/in-progress jobs) and Quote (for quotes not yet converted to jobs). The Accura job status (Quote, Order, In Progress, Completed, Cancelled) determines whether we load to Quote or SalesOrder. Job number from Accura becomes OrderNum in Epicor, and job line items map to OrderDtl records with part number, quantity, unit price, and job stage resolved to Epicor's OrderLine record status.

Accura job stages (Estimate, Awaiting Approval, Scheduled, In Production, Shipped) map to Epicor OrderHed.OrderStatus and OrderDtl.StatusCode. We build a status mapping table during discovery and apply it during the transform phase. Custom stage values that have no Epicor equivalent are flagged as UD fields for the customer's Epicor admin to configure in the OrderHed UD table after schema setup.

Accura Inventory Items (stock and non-stock) map to Epicor Part records. Stock items with on-hand quantity create PartWhse (Part Warehouse) records with OnHandQty, ABCCode, and BinNum populated. Non-stock materials and consumables create Part records with TypeCode = Non-Stock. The Accura item number becomes Epicor PartNum, and the cost basis from Accura becomes the initial StandardCost on Part. Items with negative balances or zero on-hand are flagged for customer review before Epicor load to prevent phantom stock carry-forward.

Accura job records may contain embedded Bill of Materials lines that represent the job's material inputs. We split these into Epicor JobMtl (material requirement) records linked to a manufacturing Job record in Epicor. The Accura job must first be promoted to an Epicor Job (JobProd/JobHead) before BOM lines can be attached. We sequence the Job creation before JobMtl load so that the JobNum foreign key is satisfied at insert time.

Accura Invoices (open and historical) map to Epicor InvoiceHed and InvoiceDtl. Paid invoices transfer as read-only records with InvoiceHed.InvoiceSuffix = '-HIST' to distinguish them from open receivables. Open invoices load with their original invoice date, due date, and payment terms, and we link the InvoiceHed.CustNum to the corresponding Epicor Customer record created during the Customer phase. Accura payment records link to InvoiceHed via reference number.

Accura Vendor records map directly to Epicor ERP Vendor. Vendor name, contact info, payment terms, and default GL accounts carry forward. Duplicate-name handling in Epicor uses VendorID as the unique key, not vendor name, so we use the Accura vendor ID as VendorID during import and suppress Epicor's duplicate warning. We validate that no two Accura vendors share the same name but have different IDs before loading.

Accura per-seat user accounts map to Epicor User records with role and department preserved. User passwords do not transfer and must be reset manually in Epicor post-migration. We inventory active vs. inactive user accounts during scoping and flag any seats that should be deprovisioned rather than migrated, so the customer does not over-license at Epicor. If Epicor HR modules are in scope, we map Accura users to Employee records with DcdUSERID linked to the User record.

Accura custom fields export as additional columns in the standard object CSV exports. We carry each custom field into Epicor as a User-Defined field (UD01-UD30) on the corresponding table (e.g., OrderHed.UD01 for a custom Accura job field). For custom fields that require derived logic (e.g., populating a ZIP code from the ShipTo entry), Epicor requires a BPM; we document these as part of the post-migration handoff so the customer's Epicor admin or partner can implement the BPM logic after go-live.

Accura tax codes in the export map to Epicor TaxRegion records. We build a tax region mapping table during discovery by reviewing the tax codes in use across Accura customers, vendors, and invoices. If the customer uses a tax calculation service (Avalara, Vertex), we configure TaxConnect integration separately from the migration scope and document the required Epicor tax setup steps.

Accura payment terms (Net 30, 2/10 Net 30, COD, etc.) map to Epicor ERP Term records. TermCode from Accura becomes Term.TermCode, and Term.DaysDefault maps from Accura's net days value. We validate term code coverage during discovery to ensure all Accura terms have a matching Epicor Term before the Invoice phase begins.

Proofs, job files, and documents stored within Accura are not accessible via standard CSV export. We provide a file-location inventory to the customer listing each document's path or storage reference in Accura so they can manually retrieve, archive, or re-upload to Epicor's DocStar EDMS or Content Library post-migration. This is a manual step outside the automated migration scope and is documented in the handoff package.

Accura pricing lists attached to customers or jobs map to Epicor PriceLvl records. For customer-specific pricing, we create CustomerPartXRef records linking the Epicor Customer to the Part with the negotiated price. Standard list prices migrate as PriceLvl records attached to Part records. Epicor supports multiple price lists per customer; we document the price list structure during discovery and apply it during the Customer and Order phase.

Accura shipping methods in the export map to Epicor ShipVia records. ShipViaCode, Description, and tracking URL fields carry forward. If Accura uses carrier-specific account numbers, we map these to Epicor's ShipVia.FreightChargeAccount field so that freight costing flows correctly into Epicor's AR and AP modules.