Migrate from Astral Manufacturing ERP to Acumatica

Astral's product master carries part number, description, UOM, costing method, and reorder point. Acumatica splits items into Stock Item (tracked inventory with cost layers) and Non-Stock Item (expensed or services). We infer the split from Astral's stock-tracking flag, then map UOM codes and cost method as Acumatica attribute values on the target item record.

Astral BOMs with version, component lines (part number, quantity per), and operation steps map 1:1 to Acumatica BOMs. Multi-output BOMs in Astral require Acumatica's multi-output configuration with separate material allocation lines per output item. We also preserve BOM revision histories and ensure that any BOMs with inactive components are flagged for Acumatica admin review before activation to prevent orphaned material lines.

Astral production orders carry order number, status, BOM reference, scheduled quantities, warehouse, and material issue tracking. We map these to Acumatica Production Orders with the same material requirement lines and operation references preserved against the source BOM. If a production order references a BOM that has not yet been migrated, we hold the order in a pending queue until the BOM is available, ensuring referential integrity throughout the load.

Astral customer master with name, billing/shipping addresses, payment terms, credit limit, and tax ID maps directly to Acumatica Customer. We preserve the original create date and any custom classification flags as Acumatica custom fields. During the load, we validate each customer's tax registration ID against Acumatica's tax schema and flag any missing tax zones for admin configuration before the customer record is committed.

Astral vendor records with name, address, payment terms, and account code map to Acumatica Vendor. Purchase terms and remit-to addresses carry forward as Acumatica Vendor attributes; GL account assignment requires Acumatica admin review of the AP subaccount structure. We also map vendor-specific note fields to Acumatica's Vendor Note document type, preserving any internal comments or attachments for future reference.

Open Astral sales orders with header fields (order number, customer, date, warehouse) and line items (part number, quantity, unit price, warehouse) migrate as open Acumatica Sales Orders. We preserve line-level order numbers and original order dates for post-migration reconciliation against the source.

Open Astral purchase orders map to Acumatica Purchase Orders with vendor, ship-to branch/warehouse, line items, quantities, and costs. Header-level freight and tax estimates in Astral map to Acumatica's tax and shipping attributes on the PO line. If any line references an inventory item that has not yet been loaded, we hold the line in a pending state and alert the migration team to resolve the missing item before the PO is finalized.

Astral inventory balances per warehouse site are loaded into Acumatica as Inventory Receipt transactions against the target branch and warehouse, applying the item's costing method. We use a mass-receipt import rather than one-by-one posting to handle high-volume balance loads efficiently.

Astral income and expense accounts map directly to Acumatica accounts. Balance-sheet accounts require branch context in Acumatica — we map them to the default company branch and flag accounts that need Acumatica admin assignment to additional branches for multi-branch deployments.

Astral's quality test records (pass/fail results per batch, QC parameters) have no native Acumatica equivalent without the Quality Management Suite. We preserve QC results as a custom entity linked to production orders and inventory lots, and surface the Quality Management module as a separate Acumatica add-on decision.

Astral user records with login name, role, and site access map to Acumatica Employees and Users. We resolve by email match against Acumatica users and flag any Astral owner records that have no corresponding Acumatica login for admin assignment. Additionally, we map any active directory group memberships from Astral to Acumatica's role-based security groups, ensuring that permission sets are replicated as closely as possible during the migration.

Astral's CRM and Lead records in the Customer module merge into Acumatica's Customer + Contact model. We attach all contact details, phone numbers, and classification flags to the Customer record's Contacts tab and set the primary contact as the account's main point of record.

Astral HRMS records (employee details, attendance, payroll) do not map to Acumatica's Employee record structure without the Payroll module. We preserve HRMS data as an exported dataset for reference and flag HRMS migration as a separate scope requiring Acumatica Payroll configuration.