Migrate from Konnect ERP to Odoo ERP

Konnect Customer records carry name, contact details, GSTIN, billing address, shipping address, and outstanding balance. We split these into Odoo Contact records (personal details, GSTIN, addresses) and Company records (organization name, website, fiscal position) with the Contact linked via the Contact field. GSTIN stored as a custom field on the Contact. Outstanding balance from Konnect becomes a follow-up note rather than a live balance field in Odoo because Odoo's accounting balance is derived from invoices rather than stored as a customer attribute.

Konnect Item master covers both inventory items and service line items with SKU, description, unit of measure, tax code, cost price, and sales price. We classify each Item into the corresponding Odoo product type: stockable items become storable products with BoM capability, non-stock items become consumables, and service items become service products. HSN codes from Konnect map to the l10n_in_hsn_code field in Odoo's Indian localization product form. SAC codes map to l10n_in_service_type_code for service products.

Konnect account codes and hierarchies are per-company and vary by customer configuration. We extract the full Chart of Accounts and build a destination-account mapping table before import. Odoo's Indian localization includes a pre-built Indian chart of accounts (based on the standard COA structure); if the Konnect COA diverges significantly, we configure a custom COA and load account codes with their parent structure using the account.group and account.account models via XML-RPC. Account type mapping (receivable, payable, expense, revenue, etc.) is defined in the mapping table.

Outstanding Konnect invoices carry open or closed status, invoice number, invoice date, due date, amounts, and line items referencing Item IDs. We export open invoices only (closed invoices are historical and loaded as reconciled moves if required). Each invoice line references the migrated Product record. Customer and supplier invoices map to Odoo account.move with move_type 'out_invoice' and 'in_invoice' respectively. The Konnect invoice number becomes the Odoo invoice reference; the original invoice date is preserved as the invoice date.

Konnect Project records include customer association, billing plan, milestone schedule, and man-hour allocations. We preserve the project name, customer link, and planned hours. Milestones map to Odoo project tasks with the milestone name as the task name and the scheduled date as the task deadline. If Konnect stores a billing plan (rate per hour or fixed price per milestone), we document it in the migration notes for the customer's Odoo partner to configure in Odoo's Timesheet and Billing apps post-migration.

Konnect Timesheet records link an employee to a project and a date range with hours logged. We map these to Odoo Account Analytic Lines linked to the migrated Project and Employee. Entries without a valid project reference in the destination are flagged for the customer's review before import. If Odoo's Timesheet app is not installed, analytic lines still load under the Projects app as project track entries.

Konnect Employee master includes personal details (name, contact, department, designation), effective-dated employment status, and any active compensation fields. We map these to Odoo HrEmployee with name, work email, department link, and job title. Konnect departments map to Odoo HrDepartment via the department field on the employee. Effective status (active/inactive) maps to the active boolean on HrEmployee. Compensation fields (basic, allowances) are stored as custom fields on HrEmployee or in the Payroll app notes section depending on whether Odoo Payroll is in scope.

Konnect E-Invoicing records are GSTIN-tagged with invoice number, date, seller and buyer GSTIN, line items with HSN/SAC codes, tax amounts (CGST, SGST, IGST), and the IRN (Invoice Reference Number). We migrate these as Odoo account.move records with the Indian localization fields populated: l10n_in_gstin, l10n_in_state_id, and the tax tags set to the correct GST rate. The IRN is stored in a custom field for audit traceability. HSN/SAC codes that do not have a direct match in Odoo's tax code table are flagged and escalated before import to prevent silent errors.

Konnect E-Way Bill records carry the E-Way Bill number, date, validity, transporter details, and linked invoice reference. Odoo Community does not include native E-Way Bill generation; this is available via the Indian localization partner module (l10n_in) or a third-party E-Way Bill integration app on the Odoo Apps marketplace. We migrate the E-Way Bill metadata as a custom field on the related account.move and document the linked invoice. Post-migration, the customer's Odoo partner configures the E-Way Bill generation module to align with current GSTN portal requirements.

Konnect Supplier records store vendor name, contact details, GSTIN, and PAN. We import these as Odoo Contacts with the Supplier checkbox enabled. The vendor's GSTIN maps to the same custom GSTIN field used for customers. PAN is stored in a custom field. Outstanding payables from Konnect map to follow-up notes on the vendor Contact rather than as a live balance because Odoo's AP balance is derived from vendor bill records.

Konnect Department records define the organizational hierarchy used by the Employee module. We map these directly to Odoo HrDepartment with the parent_id hierarchy preserved. Department names and codes migrate as department name and code fields. This mapping must complete before Employee migration because Odoo HrEmployee requires a valid department_id reference.