Migrate from Astral Manufacturing ERP to Odoo ERP

Astral Sales Management Customer records map to Odoo Contact with partner_type=contact and customer_rank set to distinguish from Vendors. We preserve the Astral customer code, payment terms, credit limit, and GST/tax registration as custom fields on the Odoo Contact. Address fields (billing, shipping) map to Odoo's contact addresses with address_type. Active/inactive status is preserved; inactive customers are archived in Odoo rather than deleted.

Astral Vendor/Client records map to Odoo Contact with partner_type=supplier. Vendor codes, payment terms, and bank details transfer to Odoo as custom fields or through the Odoo Accounting vendor bank account model. Vendor GST/TDS registration fields map to Odoo's fiscal information fields on the supplier contact.

Astral Items with associated BOM records decompose into an Odoo Product (the finished good) and one or more Odoo BOM records. For single-level BOMs, we create one Odoo BOM with the component Items as lines. For multi-level BOMs, we create phantom or sub-assembly BOMs in Odoo matching the Astral structure, preserving the quantity-per and operations routing. Item-level cost data migrates as Odoo's standard cost on the product form.

Astral Items without BOM (purchased-for-resale or raw materials) map directly to Odoo Product with product_type=consumable or product_type=product. SKU, unit of measure, and reorder point transfer to the Odoo product form. Stock control settings (make-to-order, min/max rules) require configuration during Odoo setup based on the customer's inventory policy.

Astral BOM child records for each manufactured Item merge into an Odoo BOM with BOM lines referencing the component Product records. BOM type (kit, manufacturing, phantom) maps based on the Astral production type flag. Routing steps from Astral's Production Process (work centre, operation sequence, cycle time) map to Odoo Work Orders with work centre assignment and operation duration.

Astral Production Process records map to Odoo Manufacturing Order. We preserve the source production order ID as a reference field, map the BOM version to Odoo's BOM revision, and transfer routing steps as Odoo Work Orders linked to the MO. Open production orders (in-progress at cutover) migrate with their current state and WIP quantity; closed production orders migrate as done records with a migration flag.

Astral Stock Management batch records map to Odoo Quant records at the product-warehouse-location level, with batch serial numbers stored as Odoo Lot records. We reconcile stock-on-hand quantities from Astral against Odoo's initial inventory valuation before opening the warehouse for live transactions. Open production moves in progress migrate as Odoo internal transfers in pending state.

Astral Purchase Management POs map to Odoo Purchase Order. Open POs migrate as draft or purchase orders in Odoo; closed POs migrate as done records with a completed-flag. Line items map by Item to Product, with qty_ordered, price_unit, and taxes preserved. Approval status on open POs requires Odoo approval workflow configuration post-migration.

Astral Order Management sales orders map to Odoo Sale Order. Open orders at cutover migrate as Quotation or Sale Order in confirmed state to preserve the customer commitment. Closed orders migrate as done records. Line items map to Odoo order lines with product, quantity, and price. The sales team owner maps via email lookup to the Odoo User.

Astral Payment Collection open receivables and Expense Management open payables map to Odoo Accounting as open Account Move lines (invoices and vendor bills) with partner_id, amount, due date, and residual amount. We extract the current outstanding balance and due date from Astral and create Odoo invoices with the same residual. Full payment history does not migrate as independent records; the open residual is the migration target.

Astral Quality Test records attach to production batches and purchase receipts. We migrate test results as Odoo Quality Check records linked to the relevant Manufacturing Order, Stock Move, or Lot. Test result values (pass/fail, measured values) transfer to Odoo's qc_team, qc_trigger, and control_point models. Threshold rules and pass/fail configuration are destination-specific and require manual redefinition in Odoo Quality settings post-migration.

Astral User Management records map to Odoo User by email. We preserve active/inactive status and the user's Astral role as a custom field in Odoo. Odoo's access rights model (groups, multi-company, portal access) is configured post-migration based on the customer's desired permission structure. If the customer used Astral's HRMS for employee records, those migrate separately to Odoo HR.