Migrate from Vault-ERP to Epicor Prophet 21

Vault-ERP stores the full account hierarchy via its NetSuite-derived API. Epicor Kinetic uses a GL Account table with Account Type (Asset, Liability, Equity, Revenue, Expense), Posting Account flags, and a Company Assignment. We extract the Vault-ERP account structure with account number, name, type, and parent reference, then map it to Epicor's GL Account with the same posting semantics. Intercompany account mappings require additional configuration in Epicor's Multi-Company Journal entry setup if the destination spans multiple Epicor companies.

Vault-ERP Customer records map to Epicor Kinetic Customer records with contact details, ship-to and bill-to addresses, credit limits, and payment terms preserved. The Vault-ERP customer class and region codes map to Epicor Customer Group and Territory fields. Any Vault-ERP custom classification fields require pre-migration UD field setup in Epicor before the Customer import batch begins.

Vault-ERP Vendor records map to Epicor Kinetic Vendor records with address, payment terms, and bank account details. Vendor holds are preserved as a Vendor.ApprovalStatus field configuration in Epicor. Vendor-specific lead times and freight terms migrate to the Epicor Vendor PPP (Purchasing Terms) record.

Vault-ERP Item records map to Epicor Kinetic Part records with Part Number, Description, Type (Stock, Non-Stock, Service), UOM (Unit of Measure), and cost information. Vault-ERP item classes map to Epicor Part Class codes. Current on-hand quantities from Vault-ERP transfer to Epicor PartBin records by warehouse. Custom item fields in Vault-ERP require UD field setup on Epicor's Part table before this import batch runs.

Vault-ERP BOM (Bill of Materials) structures with multi-level assemblies map to Epicor Kinetic PartMtl (material) and PartOpr (operation) records. Each Vault-ERP BOM header becomes a Part record of Type MfgKit or Assemble; each component becomes a PartMtl row with qty-per, scrap percent, and material type flags. We preserve the BOM revision and effective date in Epicor's PartRev and PartRevDtl tables. Manufacturing routing data from Vault-ERP maps to PartOpr records with work center and cycle time assignments.

Open payable records in Vault-ERP carry vendor reference, invoice number, invoice date, due date, outstanding balance, and currency. These map to Epicor Kinetic APInvoice records with invoice line distributions mapped to GL accounts from the Chart of Accounts migration. We preserve the original AP invoice number in Epicor's Invoice Reference field. Prepayments and partial payments migrate as separate APTran entries.

Open receivable records in Vault-ERP map to Epicor Kinetic ARInvoice with customer reference, invoice number, invoice date, due date, and outstanding balance. Vault-ERP payment terms map to Epicor AR Terms codes. Deposit records and credit memos migrate as separate ARTran entries with transaction type flags. Currency and subsidiary assignments are preserved from the source records.

Vault-ERP Sales Orders map to Epicor Kinetic OrderHed (order header) and OrderDtl (order detail). The customer reference and ship-to address resolve via the Customer mapping; line items resolve via the Part mapping. Vault-ERP order status (open, partial, complete) maps to Epicor OrderHed.OrderStatus. Custom fields on Vault-ERP order headers migrate to UD fields on OrderHed after UD field setup in Epicor. We flag any Vault-ERP order that references a discontinued part and hold it for customer admin resolution.

Vault-ERP Purchase Orders map to Epicor Kinetic POHeader and POLine records. Vendor resolves via the Vendor mapping; line items resolve via the Part mapping. POStatus, buyer assignment, and FOB terms migrate. Purchase order approvals in Vault-ERP do not transfer; Epicor's PO approval workflow is configured separately post-migration.

Vault-ERP Employee records carry job title, department, hire date, and effective-dated compensation changes. These map to Epicor Kinetic EmpBasic (name, address, contact, department, job code) and pay rate data. We extract the full effective-dated change log from Vault-ERP and load it into Epicor as a sequence of dated HR records, preserving audit continuity. Custom employee fields migrate to UD fields on EmpBasic after pre-migration UD field configuration.

Vault-ERP time entries with billable and non-billable hours, project associations, and employee links map to Epicor Kinetic LaborDtl records. We map the Vault-ERP project reference to an Epicor JobNum or ProjectID, and the hours, labor type, and work date transfer to LaborDtl with the appropriate LaborType and LaborHrs values. Vault-ERP's configurable time entry layout requires a pre-migration review to identify which fields map to Epicor's fixed LaborDtl schema.

Vault-ERP bank account definitions and current balance snapshots map to Epicor Kinetic BankAcct records with bank code, account number, currency, and opening balance. We transfer the balance as of the migration effective date as an opening balance. Epicor's bank reconciliation module is configured separately; historical cleared transactions are not migrated as part of the standard scope.

Vault-ERP tax codes with jurisdiction-specific rates and rules map to Epicor Kinetic TaxRegion and TaxConnect configuration. Each Vault-ERP tax code becomes an Epicor TaxRegion with associated TaxDetail rows for rate, tax type, and effective date. Tax exemptions and tax group assignments migrate to Epicor TaxExempt records linked to Customer and Vendor.

Vault-ERP file attachments linked to customers, vendors, orders, and items export as document records with binary content and metadata. We transfer the file content, original filename, and linked record reference. Every migrated attachment is verified post-transfer by SHA-256 checksum comparison against the source file; any mismatch is flagged for manual resolution. Epicor Kinetic stores these in its Document Management system with reference links back to the parent record.