Migrate from Astral Manufacturing ERP to Infor CloudSuite Corporate

Astral Customer master records map to Infor Business Partner records with Role = Customer. We extract customer name, contact details, address structure, payment terms, and GST/TIN identifiers. The customer code from Astral becomes the Business Partner ID; the original source system reference is preserved in a custom field for audit. Where Astral stores multiple contact persons per customer, we create primary and secondary contact roles on the Business Partner address record.

Astral Vendor records map to Infor Business Partner with Role = Supplier. Vendor code, payment terms, and bank details extract as-is. Where Astral's vendor module is shared with the customer module under a single client master, we separate these by role during transformation to avoid duplicate Business Partner records in Infor. If a party appears as both customer and vendor in Astral, we create a single Business Partner with both roles enabled.

Astral Items migrate to Infor Part Master as the product catalog parent record. We map item code, description, unit of measure, item type ( manufactured vs purchased), and standard cost. The item's active/inactive status maps to the Part Master site's stocking policy. Item-specific custom fields identified during discovery migrate as extended attributes on the Part Master.

Astral Items with BOM links decompose into Infor BOM Header records (one per manufactured item) and BOM Line records (one per component). Multi-level BOMs (sub-assemblies referencing their own BOMs) create a BOM hierarchy that Infor resolves via BOM Level and Revision fields. We validate quantity-per and scrap-percentage fields during decomposition. Phantom BOMs used for kit items map to a flagged BOM type in Infor.

Astral Purchase Order header and line records map to Infor PO records. PO number, vendor reference, order date, and expected delivery date migrate. Line items resolve the Part Master reference (via item code lookup) and map quantity and unit cost. Open POs at cutover migrate as open; closed POs migrate as closed with a received-status flag. PO approval workflows in Infor are reconfigured post-migration as they are destination-specific.

Astral batch tracking records map to Infor Inventory Lot records with lot number, manufacture date, expiry date (if applicable), and quantity-on-hand. Warehouse and location codes from Astral map to Infor site and warehouse designations. Where Astral tracks batch-level stock at multiple sites, we create separate lot records per site. Stock-on-hand quantities are reconciled against open production orders before final import.

Astral Production Orders map to Infor Work Orders with header fields (order number, item to manufacture, quantity, scheduled start/end) and BOM linkage to the decomposed Part Master BOM. Routing steps from Astral's production process module map to Infor Work Order Operations with work center references. Custom quality checkpoints in Astral's production process are noted as Infor QC specification attachments requiring manual redefinition in the destination.

Open Sales Orders from Astral migrate to Infor Sales Orders with customer reference, order date, requested date, and line items (item, quantity, price). Closed historical orders migrate as closed records with an order-status flag to prevent accidental re-processing. Order-to-invoice linkage is preserved via the original Astral order number stored as a reference field on the Infor Sales Order.

Astral open receivables (Payment Collection module) map to Infor AR records with customer link, invoice reference, due date, and outstanding amount. Astral open payables (Expense Management) map to Infor AP records with vendor link, invoice reference, due date, and outstanding amount. Payment history and reconciliation records do not migrate independently; they are reconstructed in Infor from the posted AP/AR transaction history post-migration.

Astral invoices migrate as line-item records with tax and discount data to Infor. Invoice PDFs are identified during discovery and flagged for separate document migration handling via Infor Document Management (IDM). Invoice-to-payment linkage (whether paid or open) is preserved via the source invoice number as a reference key in Infor's payment application records.

Astral Quality Test records attached to production batches migrate as Infor QC Specification lines with test type, parameter, and threshold values. Test results (pass/fail, measured values) map to Infor inspection result records linked to the Work Order. Pass/fail threshold configurations are destination-specific and must be redefined in Infor's QC setup post-migration; we deliver a written threshold mapping document as part of the handoff.

Astral User Management accounts map to Infor Operator records with user ID, name, email, and role/permission structure mapped to Infor's role-based access control. Active users migrate with their current role assignments; inactive users migrate with inactive status for audit continuity. Any custom permission sets in Astral are documented and mapped to the closest Infor role for admin review.