Migrate from Newton ERP Software to Odoo ERP

Newton ERP centers all modules on a company profile (GST number, address, logo). Odoo holds this in res.company, which also drives fiscal localization. We set the GST registration number as a custom field on res.company using India's l10n_in localization module, and configure the company's address structure to match the GSTIN format before any transactional data loads.

Newton ERP maintains a COA tied to the company profile with account codes, names, and types (Revenue, Expense, Asset, Liability). We map each account to Odoo's account.account with the matching code, name, and user_type_id from Odoo's standard chart of accounts template. Indian localization (l10n_in) provides a pre-built COA aligned with GST reporting; we cross-reference Newton account codes against it and append any non-standard accounts before loading.

Newton Customer records carry name, GST number, address, contact info, and credit terms. Some implementations include custom fields added via Forms Customization. We extract all standard fields plus any custom properties captured via the correct form view, map GSTIN to l10n_in_gstin on res.partner, and set customer_rank to flag the partner as a customer. Credit terms map to property_payment_term_id on the partner record.

Vendor records in Newton mirror Customer records with the addition of bank details and PAN/TAN. The vendor list drives Purchase Orders and GRNs. We map PAN and TAN as custom fields on the res.partner record, bank account details to partner bank records (res.partner.bank), and set vendor_rank to flag as supplier. Vendor credit terms map to property_supplier_payment_term_id.

Items include name, SKU, unit of measure, opening stock, reorder level, and valuation method. Newton tracks stock in real-time via the Inventory module. We export item master data and current stock quantities, map valuation_method to product.category's property_cost_method, and load stock.quant records to seed opening inventory at the warehouse level. Non-stock items (services) load as product.product with type = service.

Newton Sales Orders link to Customers and reduce inventory with line items carrying quantity, rate, tax, and discount. We export full line-item detail and order status (open or closed). Open orders load as sale.order with state = draft or sale_order depending on the Newton's status. Closed orders load with state = done for historical record. Tax codes map to Odoo's account.tax records using India's GST tax structure.

Purchase Orders in Newton link to Vendors and drive GRN creation. We export PO header data and line items, mapping vendor references to the destination res.partner records created in the vendor load phase. Open POs load as purchase.order with state = draft or purchase; closed POs load with state = done. Tax mapping uses the same l10n_in GST structure as sales orders.

Outstanding receivables in Newton's Accounts module map to Odoo account.move records of type out_invoice with state = posted and payment_state = not_paid. Each invoice carries the customer partner, invoice date, due date, and open amount. We compute the aging buckets (current, 30, 60, 90 days) from the due date and write them to custom fields for reporting. Payment terms come from the mapped customer res.partner record.

Outstanding payables map to Odoo account.move records of type in_invoice with state = posted and payment_state = not_paid. Each record carries the vendor partner, invoice date, due date, and open amount. Aging buckets compute from due date. PAN/TAN from the vendor record is available on the partner for tax reporting.

The HR module holds employee profiles, salary slips, and hiring records. Employee numbers and department assignments vary between implementations. We export the employee master and map departments to Odoo hr.department records, creating the department structure first so that the Many2one reference is satisfied at import time. Active employment status from Newton maps to the employee resource calendar and contract state in Odoo HR.

Newton Forms Customization adds non-standard properties to Customer, Vendor, or Item records. These custom fields do not appear in standard report exports unless the specific custom-form view is used. We audit the source tenant's active forms during scoping, list every custom field with its data type and picklist values, and pre-create matching custom fields on the Odoo res.partner and product.product models using Odoo Studio or direct _columns definition before the main data load.

Newton ERP supports document attachments at transaction and master-record level, but there is no public attachment export API. We cannot guarantee reliable bulk attachment extraction. We flag this as a limitation and instruct the customer to manually export any critical attached documents (signed PDFs, GRN scans, delivery challans) via Newton's built-in download capability before cutover. We provide a naming convention mapping so that re-uploaded attachments can be linked to the correct Odoo record.