Migrate from eBIZ SMARTZ Business ERP to Epicor Prophet 21

eBIZ SMARTZ Customer master records (including consolidated order history and payment records) map to Epicor Kinetic Customer table. The HubSpot 360-degree consolidated view is decomposed: Customer.CustID and Customer.Name map directly; the consolidated order-to-invoice-to-payment history is distributed across SalesOrder, InvcHead, and CashHead with Customer.CustNum as the foreign key. Customer Tax Management fields from eBIZ SMARTZ map to Customer.TaxRegion and Customer.TaxConnectEnabled. We use the Epicor REST API CustomerSvc to upsert by CustID as the dedupe key.

eBIZ SMARTZ Order records (with their transactional linkages to invoices and customer accounts across all operating locations) map to Epicor Kinetic OrderHed and OrderDtl. OrderHed carries CustomerNum, OrderNum, and Plant; OrderDtl carries LineNum, PartNum,SellingQuantity, UnitPrice, and Tax attributes. The eBIZ order-to-cash cycle linkage is preserved by importing OrderHed first (to establish OrderNum), then OrderDtl (linked by OrderNum), and finally resolving the open invoice status against InvcHead post-import.

eBIZ SMARTZ Invoice records map to Epicor Kinetic InvcHead and InvcDtl. Each invoice's reference to its originating order (OrderHed.OrderNum) is preserved as InvcHead.OrderNum so the order-to-cash linkage is queryable via BaqAPI post-migration. Customer Tax Management data from eBIZ SMARTZ maps to InvcHead.TaxRegionCode and InvcHead.LockRate. Invoice receipt status (Knock off in eBIZ SMARTZ) is mapped to InvcHead.InvoiceAmt and InvcHead.Doc invoice balances. We skip eBIZ SMARTZ advance and deposit records as a separate phase because they require AR Credit Memo handling in Epicor.

eBIZ SMARTZ Payment records (linked to invoices and customer accounts) map to Epicor Kinetic CashHead and CashDtl. CashHead.GroupID and CashHead.TranDate carry the payment date; CashDtl links to InvcHead via InvoiceNum and InvoiceLine to complete the cash application. eBIZ SMARTZ's Inter Bank Transfer and Bank Reconciliation data map to CashHead.BankAcctID and CashHead.TranNum. Bank reconciliation flags from eBIZ SMARTZ are stored in custom fields on CashHead pending the customer's Epicor admin confirmation of the bank reconciliation workflow.

eBIZ SMARTZ Vendor Management data (Vendor Opening Balances, Vendor Tax Management, Purchase Invoices, and Invoice Payments) map to Epicor Kinetic Vendor. Vendor.VendorID and Vendor.Name map directly from eBIZ SMARTZ's vendor master. eBIZ SMARTZ's advance and refund deposit records for vendors map to Vendor.CreditPct and AP adjustments in the VendorPayment table. Vendor tax management fields map to Vendor.TaxRegionCode and Vendor.TaxConnectEnabled.

eBIZ SMARTZ Purchase Invoices (Expense, Services, and Material categories) map to Epicor Kinetic APInvoiceHed and APInvoiceDtl. The invoice knock-off logic for AP (paying purchase invoices against vendor payments) maps to APInvoiceHed.InvoiceAmt and the linked VendorPayments in Epicor. eBIZ SMARTZ Vendor Opening Balances map to APInvoiceHed.DocinvoiceAmt as an opening AP balance rather than a standard invoice.

eBIZ SMARTZ's Multi-Level Chart of Account (corporate to division to operating location) maps to Epicor Kinetic's segment-based GL account structure. We first extract the full account code hierarchy from eBIZ SMARTZ, then configure Epicor Kinetic's COA segments to match the source hierarchy: the first segment maps to the corporate-level account, subsequent segments to division and operating location. AccountType and Balance fields (Debit/Credit) map to GLAccount.ActiveFlg and GLAccount.Summarized. This is a configuration step that requires Epicor admin sign-off before GL data loads.

eBIZ SMARTZ General Ledger transactions (Cash Transactions, Bank Transactions, General Transactions, Debit and Credit Notes, Voucher Posting and Cancellation) map to Epicor Kinetic GLJrnGrp (journal group) and GLJrnLine (journal lines). Voucher posting sequence is preserved by setting GLJrnGrp.JournalNum and GLJrnLine.FiscalPeriod and FiscalYear to match the eBIZ SMARTZ posting date and fiscal period. eBIZ SMARTZ Multi-Level Approval status is stored as a custom GLJrnGrp.ApprovalStatus field because Epicor Kinetic approvals are handled at the configuration level. Voucher Cancellation records in eBIZ SMARTZ are stored as negative-offset GLJrnLine entries with a CancellationRef field, not as deletions.

eBIZ SMARTZ's Multi-Level Cost Center Categories, Multi-Level Cost Centers, and Project-linked cost centers map to Epicor Kinetic CostCategory (the cost center entity) and Site (for site-level cost attribution). We map each eBIZ SMARTZ cost center level to an Epicor Kinetic cost set, and then assign CostCategory codes to Site entities where the operating location is also an Epicor Plant or Warehouse. Project-linked cost centers map to Epicor Project with Project.CostRuthType set to E ( Earned Value). This mapping requires the customer's Epicor admin to confirm the number of Kinetic cost sets and their fiscal period assignment.

eBIZ SMARTZ Corporate Headquarters, Division, and Operating Location structures are decomposed into Epicor Kinetic Site records (for organizational hierarchy) and Plant and Warehouse entities (for operational hierarchy). eBIZ SMARTZ's cascading consolidation model (local forecast to financials) maps to Epicor's multi-site reporting structure, where each Site aggregates its Plant-level data. We use Site.SiteID and Site.Name from the operating location name, and map the division-level entity to an Epicor Business Unit or Region entity configured in the customer's Epicor chart of accounts segment.

eBIZ SMARTZ Employee records (HR module data with organizational structures, historical compensation, and benefits) map to Epicor Kinetic Employee. Employee.Num, Name, and Department map to Epicor Kinetic EmpBasic.EmployeeNum and EmpBasic.Name. eBIZ SMARTZ organizational structure maps to Epicor Kinetic EmpBasic.Dept and the LaborDtl table for historical time and attendance records if the customer migrated their HR module alongside the ERP. Benefits and compensation history are stored in custom fields on EmpBasic pending the customer's Epicor HRIS integration decision.

eBIZ SMARTZ Multiple Budgets per period, Verification Mode, Transaction Blocking, and Budget Comparison map to Epicor Kinetic BudgetGrp and BudgetDtl. Budget Comparison variances stored as eBIZ SMARTZ budget reports are preserved as BudgetDtl values with BudgetDtl.BudgetHedID set to the source budget version. eBIZ SMARTZ Transaction Blocking status (which prevents posting to blocked budget lines) maps to a BudgetDtl.BlockedFlg custom field because Epicor Kinetic's standard budget blocking is handled via workflow configuration rather than a flag.