Migrate from AltheaSuite to Epicor Prophet 21

AltheaSuite Items map to Epicor ERP Part records. Standard fields (item number, description, uom, item type) translate directly. Custom Item fields from AltheaSuite (text, number, lookup value, date, fractional number) map to Epicor UD tables (UD01-UD10 or table-prefixed ZDataField entries) with explicit field-type conversion. We discover all custom Item field definitions during schema profiling, validate them against the live AltheaSuite system, and create matching UD fields in Epicor before Part import begins. PartPlant records are created for each Site where the Item carries on-hand quantity or reorder level data.

AltheaSuite serial numbers are stored as separate assignment records linked to Items. Epicor manages serial numbers via PartLot with a dedicated SerialNumber table. We extract the full serial-to-item mapping as a child table during export, then re-associate each serial assignment in Epicor by inserting a PartLot record with the AltheaSuite serial number and linking it to the correct Part via PartLot.PartNum. We flag any orphaned serial records with no parent Item for manual resolution before finalizing the import.

AltheaSuite lot-controlled Items carry lot number and expiry date. Epicor ERP stores lot data in PartLot with LotNumber, ExpirationDate, and Plant fields. We migrate lot assignment records with expiry dates preserved, and we flag any FEFO (first-expiry-first-out) implications for inventory planning in Epicor. If the destination Epicor site has lot cost averaging or lot-specific GL accounts configured, we align the lot cost data to the relevant PartLot.CostPerEach or PartLot.MiscCost fields.

AltheaSuite Customer records migrate to Epicor Customer with contact details, addresses, and account-level fields. Customer's default ship-to addresses map to Customer.ShipTo records in Epicor. Vendor-managed inventory flags stored as boolean properties on AltheaSuite Vendor records translate to Customer.VMTaxbl or a custom UD field on Customer. The customer number from AltheaSuite becomes Customer.CustID if it meets Epicor's field-length constraints; otherwise we generate a mapped CustID and maintain the AltheaSuite reference in a UD field.

AltheaSuite Vendor records transfer with contact info, addresses, and supplier-level fields intact. Vendor.ManagedInventory flag from AltheaSuite translates to Vendor.VendQtaxable or a UD01 flag on the Vendor record. Bank details, payment terms, and routing information migrate as Vendor PPVVendor records if the destination Epicor company has vendor payment configuration enabled.

AltheaSuite Sales Orders map to Epicor OrderHed (order header) and OrderDtl (order lines). Order-to-delivery linkage from AltheaSuite translates to Epicor OrderRel records for each scheduled release. Fulfillment status (partial vs. complete) migrates as OrderDtl.OrderLine.Complete sets. Multi-currency order amounts require explicit mapping against Epicor's Currency table if the destination company uses multi-currency. We do not migrate POS-specific sales records; these are flagged as POS-layer data outside the ERP migration scope.

AltheaSuite Purchase Orders map to Epicor POHeader and PODetail. Line items, quantities, and costs translate directly. Multi-currency PO amounts and landed-cost fields require explicit value-mapping against Epicor's Currency and LandedCostCode tables. If AltheaSuite PO records carry any custom fields, these map to PODetail character or numeric UD fields.

AltheaSuite Work Orders are tied to multi-level BOMs and track production status. Epicor ERP represents production as a Job record with JobMtl (materials) and JobOper (operations) child tables. We translate each AltheaSuite Work Order to an Epicor Job with the BOM structure flattened into JobMtl entries. Step-level labor and machine time entries from AltheaSuite migrate as JobOper records with the AltheaSuite duration and work center data mapped to Epicor's LaborHrs and ResourceGrpID fields. If AltheaSuite tracks scrap or rework at the step level, we carry those quantities as JobMtl.MtlSpansreven or JobOper.ScrapQty. Production status (released, in-progress, complete, closed) migrates to JobHead.JobEngineered, JobHead.JobReleased, and JobHead.JobComplete flags.

AltheaSuite BOMs support nested sub-assemblies (parent Item, child sub-assembly Item, sub-sub-assembly Item). Epicor ERP uses a flat PartMtl table with a ParentPartNum reference and a BOMLevel integer. We flatten the AltheaSuite BOM hierarchy during the transform phase, computing the Epicor BOMLevel for each row and preserving the quantity-per-parent and scrap-factor data from each AltheaSuite BOM line. If AltheaSuite carries alternate materials or BOM notes, these translate to PartMtl.AltMtl and PartMtl.Text fields respectively. The BOM revision in AltheaSuite maps to PartRev.RevisionNum in Epicor.

AltheaSuite custom Item fields (text, number, lookup value, date, fractional number) require pre-creation in Epicor UD tables before Part import. We enumerate all custom field definitions during schema profiling, map each AltheaSuite field type to the corresponding Epicor UD field type (character for text, decimal for fractional, integer for number, date for date, and dropdown options for lookup values), and create the UD table entries via Epicor Ice BO ZDataTable or directly via Epicor REST API. AltheaSuite lookup values requiring specific picklist options in Epicor UD fields are pre-seeded with the AltheaSuite option list.

AltheaSuite reorder levels, reorder quantities, and min/max levels migrate to Epicor PartPlant records. If AltheaSuite carries vendor-specific pricing per Item, this data migrates to Epicor PartVendor records for MRP-driven PO suggestions. Standard costs from AltheaSuite map to PartRev.EstScrapQty or Part.CostID depending on the Epicor cost set in use.

AltheaSuite on-hand quantities per Item per location translate to Epicor PartWhse records. We extract the full inventory snapshot from AltheaSuite before cutover and load it into Epicor PartWhse with the corresponding WarehseCode. On-hand quantities are loaded last in the migration sequence to avoid MRP noise during earlier phases. We reconcile the on-hand total against AltheaSuite's inventory valuation report and flag discrepancies exceeding 0.5% for manual review before go-live.