Migrate your Astral Manufacturing ERP data

Customer and vendor master records are standard structured objects with name, contact, and address fields. We migrate these as master-record inserts with foreign-key references preserved for all linked orders and transactions.

Vendor/Client details are a distinct module in Astral. We map vendor records to the destination's supplier object, preserving vendor codes and payment terms.

Product Management module stores Items with BOM (Bill of Materials) links for manufactured goods and standard SKU data for purchased items. We migrate Items as parent records and decompose BOM children into destination-specific structure.

Purchase Management generates POs against vendor and item. We map PO header and line data, but destination-side PO numbering schemes and approval statuses often require custom field mapping.

Stock Management tracks inventory at batch level with real-time status. Batch serial numbers, warehouse locations, and stock-on-hand quantities migrate but require reconciliation against open production orders at migration cutover.

Production Process module manages work orders, routing steps, and quality checkpoints. We map production headers and BOM linkages; custom routing steps or工序-level tracking may require manual re-configuration in the destination.

Order Management generates sales orders linked to inventory and pricing. Open orders at migration cutover are migrated as-is; historical orders are migrated as closed records with a flag to prevent re-processing.

Payment Collection and Expense Management track open receivables and payables. We extract current balance, due date, and party link, but payment history and reconciliation records are not independently queryable and require extraction sequencing.

Sales Management generates invoices linked to orders. Invoices are migrated as line-item records with tax and discount data; attachment linking (PDFs) requires separate document migration handling.

Quality Test records attach to production batches. We migrate test results as structured fields, but threshold rules and pass/fail configurations are destination-specific and must be re-defined.

User Management module stores user accounts with role assignments. We migrate active users with role/permission structure mapped to the destination's access control model.

Astral does not publish a public extension or custom field API. Any custom properties added during implementation must be identified via schema inspection during the discovery phase and handled as one-off field mappings.

The native HRMS module stores employee records. Where the destination lacks an HRMS module, we migrate core employee fields and flag compensation and PTO history for manual post-migration entry.

Reports in Astral are generated within the platform and are not independently exportable. We do not migrate custom reports; these are rebuilt in the destination BI tool post-migration.