Migrate from Success ERP to Odoo ERP

Success ERP customer records map to Odoo res.partner with partner_type set to 'customer'. We extract customer name, GSTIN (mapped to the VAT field), billing address, phone, email, and credit limit where present in the export. Payment terms from Success ERP migrate as a custom field or map to an Odoo payment term if the terms match a standard Odoo template. The partner must be inserted before any invoice or sales order that references it, so it is loaded in the first migration phase.

Vendor records from Success ERP map to Odoo res.partner with partner_type set to 'supplier'. We preserve vendor name, PAN/TAN (stored as a custom field in the absence of a native Indian tax ID field in Odoo), contact information, and payment terms. Bank account details for vendor payments must be explicitly included in the export; we flag records missing bank information for customer verification before import.

The Indian accounting chart of accounts exported from Success ERP maps to Odoo account.account records with code, name, and account_type preserved. The account hierarchy (group assignments) is reconstructed using Odoo's account.group structure or parent_id references. Because Odoo defaults to a European chart of accounts, we replace it with the customer's Indian-compliant structure before any financial transactions are imported. This object must be fully loaded before any invoice or journal entry.

Sales invoices from Success ERP map to Odoo account.move with move_type = 'out_invoice'. The invoice header (partner_id, invoice_date, GSTIN, invoice number) and line items (product, quantity, rate, GST amount, HSN code) migrate separately. GST amounts are preserved as tax lines; Odoo's GST rate configuration must be pre-loaded from the customer's tax rate file because Odoo does not inherit Indian tax rates from the source export. We flag any invoice with missing GST details for manual reconciliation before import.

Purchase invoices from Success ERP map to Odoo account.move with move_type = 'in_invoice'. The same tax line and HSN code considerations apply as for sales invoices. Vendor GSTIN is validated against the vendor res.partner record before import. Bills with mismatched GSTIN values or missing tax breakdowns are held in a reconciliation queue.

Item masters from Success ERP map to Odoo product.product linked to product.template. Item code becomes the product's default_code (SKU), item name becomes the template's name, and stock quantity from the last available export becomes the initial stock.quant record. UoM (unit of measure) is mapped to Odoo's uom.uom model. Serial number and batch tracking are preserved only if the export includes those fields; this varies by implementation and is confirmed during scoping.

Basic employee records (name, designation, department, date of joining) map to Odoo hr.employee. Salary details and payroll history require a separate export file explicitly requested from Success ERP during scoping; we flag that these files are not included by default. Leave balances and attendance history are not accessible via documented export mechanisms and are documented as a manual reconciliation item.

Success ERP exports do not contain Odoo-native tax configuration. GST rates (CGST, SGST, IGST) must be configured in Odoo as account.tax records before any invoice is imported, because invoices reference tax IDs rather than tax amounts directly. We request the customer's current GST rate schedule during scoping and pre-build the account.tax records with the correct tax_group_id, amount, and type (sale/purchase) in the test environment before production import.

Implementation partners frequently add custom fields to standard Success ERP objects such as Customers, Items, or Transactions. These fields are not documented in any public schema and cannot be detected without the customer providing the complete field list and export data. We ask customers to audit their own report exports for any columns they do not recognise and include those fields in the migration scope before kickoff. Any custom fields identified are mapped as Odoo custom fields on the equivalent object if the customer requests them; otherwise they are documented in the handoff checklist.

Documents attached to invoices, purchase orders, or employee records in Success ERP reside within the platform's file storage layer, which is not exposed through any documented export mechanism. Customers must separately extract attachments from the platform or request their implementation partner to provide the file store. We include a manual document checklist in every Success ERP migration plan to prevent this from being overlooked. We do not migrate attachment files; the checklist enables the customer's team to handle them outside the automated migration scope.