Migrate from Tech Cloud ERP to Epicor Prophet 21

Tech Cloud ERP Customer records (company name, contact details, billing address, ship-to addresses, payment terms, tax registration number) map 1:1 to Epicor Kinetic Customer. We map Tech Cloud ERP's customer code to Epicor's CustNum with CustID as the external reference. Multiple ship-to addresses from Tech Cloud ERP become Epicor ShipTo records linked to the parent Customer. Payment terms (Net 30, Net 60, etc.) map to Epicor's Terms table by code match.

Tech Cloud ERP Vendor master records map to Epicor Kinetic Vendor. Vendor code, name, contact information, bank details, and payment terms transfer directly. For vendors used in import/export operations, any customs license or supplier rating fields in Tech Cloud ERP migrate as user-defined fields on the Epicor Vendor record.

Tech Cloud ERP Item records map to Epicor Kinetic Part. We map item code, description, unit of measure, cost price, sales price, and stock category. Part Type (stocked vs. non-stocked vs. service) is inferred from Tech Cloud ERP's item classification. Stocking UOM and purchasing UOM are mapped separately; any fractional conversion factors between them are recorded for Epicor's UOMClass configuration.

Tech Cloud ERP BOM is stored as item-component links with quantity-per. Epicor Kinetic BOM is operation-linked with material requirements per operation step. We extract the flat BOM from Tech Cloud ERP (via database query or Imports & Exports), map each component to a JobMtl line in Epicor, and flag for the customer's production engineer whether the destination BOM requires operation-step alignment. If Tech Cloud ERP BOMs include phantom assemblies or co-products, we note these explicitly for Epicor BOM revision configuration.

Tech Cloud ERP does not document a routing export format. Where database access is available, we extract any operation sequence data and map it to Epicor JobOper (job operation) records with labor hours, work center assignments, and sequence order. If no routing data exists in Tech Cloud ERP, we create a single default operation in Epicor and flag this for the customer's Epicor consultant to detail. Work centers in Epicor must be configured with capacity and efficiency factors before routing data is committed.

Tech Cloud ERP account codes and types (Asset, Liability, Equity, Revenue, Expense) map to Epicor GL Account and AccountType. We preserve the account code structure (segment lengths, separators) from Tech Cloud ERP and replicate it in Epicor's COA segment configuration. Cost center segments, if present in Tech Cloud ERP, map to Epicor GLGpc (global project) or a user-defined segment. Account descriptions and active/inactive status transfer directly.

Open Sales Orders from Tech Cloud ERP map to Epicor Kinetic SalesOrder. Order number, customer reference, order date, line items (PartNum, UOM, quantity, unit price), taxes, and freight charges transfer. Order status (Draft, Confirmed, Invoiced) maps to Epicor's OrderRel held/release flag. Backordered lines are flagged for review because Epicor uses Site and Warehouse on OrderRel to determine fulfillment availability.

Open Purchase Orders map to Epicor Kinetic POHeader and PODetail. Vendor reference, order date, line items (PartNum, quantity, unit cost, promised date), and approval status transfer. Tech Cloud ERP's approval workflow status does not have a direct Epicor analog; we load POs as unreleased and flag for the customer's Epicor admin to release after approval configuration is set up.

GRN records from Tech Cloud ERP (linked to a PO and confirming received quantity) map to Epicor POReceipt. The GRN-to-invoice linkage in Tech Cloud ERP does not directly map to Epicor's separate invoicing layer; we note the GRN reference in a POReceipt comment field and flag any partial-receipt discrepancies for the accounts payable team to reconcile.

Stock balances per item per warehouse from Tech Cloud ERP map to Epicor PartBin (quantity on hand per site/warehouse/bin). We confirm the inventory costing method (FIFO or Average) with the customer before writing; Epicor's costing method is set per Part and per Site, and mismatches cause perpetual cost discrepancies. Batch and serial number data, if present in Tech Cloud ERP, maps to Epicor's LotBin and SerialBin records.

Fixed Asset master records (asset tag, description, acquisition date, acquisition cost, depreciation method, useful life, location, asset category) map to Epicor Kinetic Asset. We reconstruct the depreciation schedule from the asset master because Tech Cloud ERP depreciation journal entries are not independently exportable. Epicor regenerates the journal entries from the asset register on go-live. Depreciation method (Straight-Line, Declining Balance, Units of Production) must match between systems; we flag any mismatches before writing.

Tech Cloud ERP employee records (employee number, name, department, designation, hire date, compensation details) map to Epicor Kinetic Employee. Role-based access in Tech Cloud ERP maps to Epicor Employee Security Groups. Org hierarchy segments, if present in Tech Cloud ERP, map to Epicor's LaborHierarchy or Department structure. Active/inactive employment status transfers; terminated employees are loaded as inactive in Epicor.

Open Accounts Payable and Accounts Receivable balances from Tech Cloud ERP (excluding historical closed-period invoices) map to Epicor APOpen and AROpen records. These load as opening balances at the designated go-live date. We exclude historical invoice detail unless specifically requested because Tech Cloud ERP's closed-period transaction format is incompatible with Epicor's AP/AR posting model; opening balance carries the total outstanding amount, vendor/customer reference, and due date.

Tech Cloud ERP POS transactions write directly to the inventory ledger as a combined cash/inventory entry. We split these into two migration paths: cash settlement records load as AR Invoice or cash receipt entries in Epicor, and inventory deduction records load as PartTran with a POSerial or batch reference. This sequencing prevents double-counting of stock in Epicor's inventory module at go-live.