Migrate from Astral Manufacturing ERP to Epicor Prophet 21

Astral Customer master records map to Epicor Kinetic Customer. We extract customer name, contact details, billing and shipping addresses, payment terms, and credit limits. The customer code from Astral becomes CustNum or an alternate Customer ID in Epicor. Where Astral stores multiple ship-to addresses under a single customer, we create Epicor ShipTo records linked to the parent Customer.

Astral Vendor/Client master records map to Epicor Kinetic Supplier. Vendor codes, payment terms, bank details, and contact information migrate. The Tally Integration vendor records (if synced to Tally) are flagged separately for Tally-side reconciliation rather than migrated directly into Epicor's Supplier table to avoid duplicate-entry risk at cutover.

Astral Items with type finished goods map to Epicor Part records with TypeCode = Stocked Item. We extract part number, description, unit of measure, standard cost, and stock categories. The source item code becomes PartNum; PartDescription maps from Astral's item name. Stock on hand migrates as PartBin records at the warehouse level.

Astral Items flagged as raw materials map to Epicor Part records with TypeCode = Stocked Item. Raw material cost rolls into BOM costing on the manufactured parent. Where Astral tracks expiration dates or lot attributes on raw materials, these migrate as PartLot records with the corresponding lot number and shelf life fields.

Astral Items with Bill of Materials decompress into Epicor Part (parent) and PartMtl records (child materials). Each BOM line in Astral becomes a PartMtl row with MtlPartNum referencing the sourced Part, RequiredQty, and the appropriate BOM sequence. Multi-level BOMs (sub-assemblies) are resolved recursively so that all PartMtl records point to existing Part records at migration time. We validate that all child PartNum references exist in the destination before inserting PartMtl rows.

Open Purchase Orders from Astral's Purchase Management module migrate to Epicor POHeader. We extract PO number, vendor reference, order date, terms, and buyer assignment. Closed or completed POs are not migrated unless the customer specifies historical PO reporting as a requirement. PO approval statuses map to Epicor POHeader.ApprovalStatus, which may require configuration to match Astral's workflow states.

PO lines from Astral map to Epicor POLine with line number, part number, quantity ordered, unit cost, and due date. Where Astral records partial receipts against a PO line, we create Epicor PORel (PO Release) records with the received quantity and remaining balance. POLine.ReceivedToDate in Epicor reflects the open receipt balance at migration cutover.

Astral Stock Management batch records map to Epicor PartBin (quantity on hand by warehouse and bin) and PartLot (lot number, expiration, attributes). We extract current stock-on-hand quantities, warehouse assignments, and lot serial numbers. Open production orders referencing specific lots require JobMtl lot allocation review before migration because Epicor's lot allocation model differs from Astral's real-time batch tracking.

Astral Production Process module generates work orders that map to Epicor JobHead (job header), JobMtl (material allocations), and JobOper (routing steps with work center and estimated hours). We extract job number, production item, quantity, scheduled start and end dates, BOM revision used, and routing steps. Active jobs (in-progress at cutover) migrate with current WIP status; completed jobs migrate as closed with actuals if the customer specifies historical production reporting. Custom routing steps or quality checkpoints in Astral that do not map to standard JobOper fields are flagged for manual Epicor MES configuration.

Open Sales Orders from Astral's Order Management module migrate to Epicor OrderHed. We extract order number, customer reference, order date, terms, and sales rep assignment. OrderHed.Open铠甲 reflects open status at cutover. Closed historical orders are migrated as closed records with a migration-flag field to prevent re-activation. Order number sequences in Epicor may require configuration to match Astral's numbering scheme.

Sales order lines migrate as Epicor OrderDtl with part number, quantity ordered, unit price, discount, and scheduled ship date. Where Astral links lines to specific production jobs or purchase orders, we map the corresponding JobNum or PONum reference on the OrderDtl. Line-level taxes and freight from Astral map to Epicor OrderMsc records.

Astral invoices (from Sales Management) migrate to Epicor InvoiceHed and InvoiceDtl. Line items, tax amounts, and discounts preserve. Invoice PDFs are not stored in the record migration; we flag them for document migration handling separately. Invoice payment status (paid, partially paid, outstanding) maps to Epicor's AR application records if the customer uses Epicor Collections.

Astral Payment Management open AP balances migrate as Epicor APOpen records with vendor, invoice number, current amount, due date, and invoice date. We do not migrate payment history or reconciliation records as these are operational tables in Astral that reference each other across periods. The AP balance at cutover is verified against the vendor statement and Tally sync before Epicor go-live.

Astral Payment Collection open AR balances migrate as Epicor AROpen records with customer, invoice number, current amount, due date, and invoice date. Payment history and reconciliation records do not migrate independently. Where a customer has partial payments applied in Astral, we preserve the applied amount and remaining balance as Epicor AROpen entries. AR balance at cutover is reconciled against the customer statement.

Active user accounts from Astral's User Management module map to Epicor UserFile. We extract user ID, name, email, and role assignments. Role-to-permission mapping requires configuration against Epicor's access control model because role naming and granularity differ between platforms. Inactive users are excluded unless the customer specifies historical user reporting.

Astral's native HRMS module employee records map partially where Epicor Kinetic includes HR functionality or where the customer uses a separate HR system. Core fields (employee ID, name, department, designation) migrate to the destination's employee structure. Compensation history, PTO balances, and payroll data do not migrate as these require separate HRMS configuration and are typically managed outside Epicor.