Migrate from Tranquil ERP to Epicor Prophet 21

Tranquil ERP account hierarchies map to Epicor GL Account codes with segment structure preserved. We extract the full account tree including inactive flags and parent-child relationships, then map to Epicor's COA structure which supports multi-segment account codes. Any Tranquil accounts flagged as inactive are loaded with an InActive flag in Epicor to prevent post-migration transaction posting. We flag duplicate account codes and segment mismatches during the transform pass before writing.

Tranquil Customer records map to Epicor Customer with contact details, payment terms, and credit limits preserved. The customer code in Tranquil becomes the Epicor CustomerID; the customer name maps to Name. Open AR balances link to invoice records via CustomerID resolution. We detect duplicate customer names during the audit pass and consolidate before import to prevent Epicor's validation rules from rejecting duplicate customer codes.

Tranquil Vendor master records map to Epicor Vendor with bank details, purchasing terms, and contact information. Vendor code in Tranquil maps to VendorID in Epicor. Accounts payable ledger reconstruction requires linking vendor IDs to open Purchase Orders before vendor import completes, since Epicor's PO entry validates the VendorID reference at insert time. We run vendor reconciliation before PO import to ensure no orphaned purchase orders.

Tranquil Items with serial/batch tracking, expiry dates, and multi-UoM configurations map to Epicor Part records. Serial number and batch tracking attributes transfer to Part Lot records; expiry dates map to Lot Effective Date and Lot Expiration Date fields. Multi-UoM requires explicit UoM conversion class setup in Epicor before item import: we extract the Tranquil UoM ratio per item and create PartUOM entries with the appropriate conversion factor. Items without a UoM class default to Each. Part Number in Epicor maps from Tranquil's item code or SKU field.

Tranquil Purchase Orders map to Epicor POHeader with line items in PODetail. Open POs migrate with current status preserved; closed POs migrate as historical records with a closed flag. VendorID, ship-to warehouse, and PO date transfer directly. Line items resolve PartNum, UOM, and quantity against the item mapping completed in the prior phase. Epicor's PO approval workflow status may need to be reset or configured before import if Tranquil used a different approval model; we flag this during scoping.

Tranquil Sales Orders map to Epicor OrderHed with OrderDtl line items, customer references, pricing, and fulfillment status. Open orders migrate in full with current status; completed orders migrate with their final fulfillment state intact. CustomerNum resolves via the customer mapping; line items resolve PartNum via the item mapping. Pricing transfers as unit price and discount percentage; Epicor's price list (PartUOM.PricePerQty) is populated where Tranquil maintained pricing schedules.

Tranquil inventory quantities across warehouses map to Epicor PartBin records per warehouse and site. Serial/batch and expiry data transfer to PartLot linked by PartNum and LotNumber. Multi-warehouse configurations in Tranquil map to Epicor Warehouse codes under their respective Plant/Site. We extract current stock levels, warehouse assignments, reorder thresholds, and minimum/maximum quantities. The Epicor warehouse structure must exist in the destination before inventory import begins; we create missing warehouse records during schema setup.

Tranquil Employee records map to Epicor Employee with personal data, roles, and compensation history from the HR module. Effective-dated compensation fields migrate to Epicor's EmployeePay records if the HR module is in scope. Employee number in Tranquil maps to EmpID in Epicor. We extract the current roster; historical payroll records are typically out of scope unless the customer requires open-payroll-period migration, which requires separate scoping. Active/inactive status preserves from Tranquil.

Tranquil custom fields on Customers, Vendors, Items, Orders, and Employees map to Epicor User-Defined (UD) tables. Epicor Kinetic uses a ZDataTable framework where UD field definitions require configuration via the UD Table maintenance screen, specifying field labels, data types (String, Integer, Date, etc.), and table associations. For custom fields that reference parent record values (e.g., a custom ZIP field that should mirror the ShipTo ZIP), Epicor requires a BPM (Business Process Management) method to propagate values post-insert; simple field-to-field mapping does not cover propagation logic. We document every such case and recommend the BPM rebuild scope.

Tranquil multi-warehouse configurations map to Epicor Warehouse codes under their respective Plant/Site. Each Tranquil warehouse with its address, bin structure, and default settings creates an Epicor Warehouse record. If Tranquil uses bin-level tracking, we map bins to Epicor PartBin entries. Plant-level assignment is required before PartBin records can be inserted; we create Plant records during the schema setup phase before inventory import.

Tranquil UoM definitions per item require Epicor UOM Class and UOM Unit setup before item import. We extract every distinct UoM from Tranquil's item records, create matching UOM records in Epicor with the correct type (Area, Count, Length,Mass, Volume, Time), and define UoM conversion entries per Part and PartUOM. Tranquil's base UoM per item becomes the default purchasing and stocking UoM in Epicor; all other UoMs on that item link via PartUOM with conversion factors.

Open accounts payable balances from Tranquil ERP map to Epicor AP Invoice records linked to VendorID. Closed AP history migrates as read-only historical records if the scope includes historical financial data. We preserve vendor payment terms and outstanding invoice amounts for AP reconciliation post-migration. AP Invoice and APPayment creation requires the GL Account mapping to be complete first since every AP entry posts to the AP subledger and the linked expense or inventory GL account.