Migrate from Tech Cloud ERP to Odoo ERP

Tech Cloud ERP customer records map to Odoo res.partner with partner_type = contact for bill-to and ship-to addresses. We preserve tax registration numbers, payment terms, credit limits, and custome fields. Address records are extracted as separate partner records linked via type = delivery or invoice. The database query selects from the customer master table with address joins where the schema is accessible; otherwise we use the Imports & Exports module output and validate field completeness against the expected row count.

Vendor master records from Tech Cloud ERP map to Odoo res.partner with partner_type = supplier. We preserve supplier categories, payment terms, customs license details relevant for import/export operations, and any custom fields. Vendor records are imported before purchase orders to satisfy the supplier_id foreign key on purchase.order.line. Tax identification numbers are mapped to the l10n_in_gstin field if the Indian GST context applies, or to a generic tax_id field for other jurisdictions.

Item masters from Tech Cloud ERP map to Odoo product.product records. We extract unit_of_measure, cost_price, sales_price, product_type (stockable vs consumable vs service), and item category for mapping to Odoo's product.category hierarchy. The hs_sku or item_code becomes product.default_code for deduplication. BOM links for manufactured items are flagged for the production mapping phase and do not block the item import itself.

Tech Cloud ERP item category records map to Odoo product.category with parent_id resolved for hierarchical category structures. We extract category codes and names from the database where accessible and build the full category tree in Odoo before product import so that the categ_id foreign key is satisfied at insert time.

The Finance & Accounting module's account codes and types from Tech Cloud ERP map to Odoo account.account records. Account code mapping preserves the numeric segment structure (for example, 1-xxxx for assets, 2-xxxx for liabilities). We extract account groupings and cost-center hierarchies field-by-field and configure account_type, reconcile flag, and tag_ids in Odoo to match the source structure. Currency alignment is confirmed with the customer if multi-currency is used on the source.

Fixed Asset records from Tech Cloud ERP (acquisition cost, acquisition date, asset category, depreciation method, useful life, location) map to Odoo account.asset.asset and account.asset.profile. We reconstruct the depreciation schedule from the asset master and let Odoo's accounting engine regenerate journal entries. Depreciation journal entries are not independently exportable from Tech Cloud ERP, so historical posted depreciation is carried as opening balance adjustments at the go-live date. We flag depreciation method mismatches (straight-line vs reducing balance) for explicit customer confirmation before proceeding.

Open and confirmed sales orders from Tech Cloud ERP map to Odoo sale.order. We preserve customer reference, order date, line items (product, quantity, unit price, tax), discount, and shipping details. Order status (Draft, Confirmed, Invoiced) maps to Odoo state values. Invoiced orders that are fully paid are migrated as closed records with invoice_id linking to account.move; partially invoiced orders are migrated as partial records with remaining quantities noted for the customer's sales team to follow up.

Open purchase orders from Tech Cloud ERP map to Odoo purchase.order. We preserve vendor reference, order date, line items (product, quantity, unit price, tax), and payment terms. GRN linkage is reconstructed by matching PO line quantities against received quantities from the Tech Cloud ERP GRN module, and Odoo's stock_picking records are created to represent received-but-not-invoiced quantities. Historical closed POs are migrated as completed records with a reference to the last GRN.

GRN records from Tech Cloud ERP map to Odoo stock.picking records of type = incoming. We extract the PO reference, received product, quantity received, date, and any duty or tax implications. For GRN records with corresponding invoice lines in Tech Cloud ERP, we match against account_move entries to create Odoo account_move records linked to the stock_picking via the purchase_invoice_policy. GRN records without invoices become unreconciled stock picks requiring manual purchase order receipt in Odoo.

Current stock balances per item, warehouse, and location from Tech Cloud ERP map to Odoo stock.quant records. We extract batch numbers, serial numbers, and expiry dates where present. Inventory valuation method (FIFO, Average, Standard) is confirmed with the customer before migration and configured in Odoo as product_category.property_valuation = real_time or periodic. Stock reconciliation records are created in Odoo for any inventory discrepancies discovered during the extraction window. POS transactions that wrote directly to the inventory ledger in Tech Cloud ERP are separated into settlement records (account_move) and inventory deduction records (stock_quant) and loaded in correct dependency order.

BOM records from Tech Cloud ERP are extracted from the database where accessible and mapped to Odoo mrp.bom. BOM structures (component items, quantities, bom_line_type) are preserved as exported, but BOM representations differ between platforms (step-based vs formula-based). If the destination Odoo instance uses a different BOM type than the source, we flag this for manual review by the customer's production engineer before committing the data. We do not migrate production routings as standard schema equivalents exist inconsistently across Tech Cloud ERP configurations.

Open production orders from Tech Cloud ERP map to Odoo mrp.production records with product_id, product_qty, bom_id, and location_src_id resolved. Work-in-progress status is preserved as mrp.production state values. Closed production orders are migrated as history with no further action required. Routing data (operation sequences, work centers, cycle times) requires manual review because Tech Cloud ERP's production module stores routing data in a non-documented format that varies by organization configuration.