Migrate from Logo Go to Odoo ERP

Logo Go Chart of Accounts records map directly to Odoo account.account with account code preserved as code and account name preserved as name. We set the reconcile flag on balance-sheet accounts (Assets, Liabilities, Equity) to match Logo Go's open-item tracking. Expense and revenue accounts disable the reconcile flag. Account groups from Logo Go map to account.group in Odoo, which controls the financial report tree structure. Any Logo Go account without a clear Odoo counterpart is flagged for manual mapping during scoping.

Logo Go Customer records map to Odoo res.partner with type=contact, customer_rank set to 1 (or incremented if multiple customer addresses exist). The primary customer address maps to partner_id.address field, and additional shipping addresses create child res.partner records of type=contact with the same parent_id. We preserve Logo Go's tax ID and fiscal code fields in the partner's vat and l10n_tr_tax_id fields respectively. Credit limits from Logo Go map to credit_limit on res.partner.

Logo Go Vendor records map to Odoo res.partner with type=contact, supplier_rank set to 1 or higher. Vendor-specific fields including payment terms, bank account details, and WHS (withholding tax) status migrate to Odoo partner fields and the l10n_tr_withholding field for Turkish localization. Vendor items and vendor-specific pricing from Logo Go map to product.supplierinfo records linked to the vendor partner.

Logo Go Items map to Odoo product.product with the product.template parent record created first. Item type (stockable, consumable, service) maps to Odoo's type field (product, consumable, service). The Logo Go item code becomes the product's default_code (SKU), and item name maps to product.template name. Cost price from Logo Go becomes the standard_price on product.product, and sales price maps to a product.pricelist item in the default sale pricelist.

Open Accounts Receivable invoices from Logo Go migrate as Odoo account.move with type=out_invoice in draft state for customer review and posting. Line items resolve to product.product via SKU match, and account codes resolve to account.account via the Chart of Accounts mapping. Logo Go's paid invoices are migrated as out_invoice with state=posted for historical record, and Logo Go's cancelled invoices are logged as out_refund with state=posted for audit completeness.

Open Accounts Payable invoices from Logo Go migrate as Odoo account.move with type=in_invoice in draft state. Vendor partner resolves via supplier_rank matching, line items resolve to product.product, and account codes resolve via the Chart of Accounts mapping. Supplier withholding tax (WHT) amounts from Logo Go are preserved in the move's l10n_tr_withholding_amount field for the Odoo partner to post correctly.

Logo Go journal entries are migrated as Odoo account.move with type=entry. Due to period-closure constraints, we flag all entries in closed Logo Go fiscal periods for manual reconciliation rather than automated import, because posting them in Odoo may trigger date_closed restrictions on the destination fiscal year. Entries in open periods migrate as draft moves for the customer's accountant to review and post.

Logo Go fixed asset records migrate to Odoo account.asset.asset with asset name, acquisition date, original value, and depreciation method preserved. The asset category from Logo Go maps to account.asset.category with matching depreciation account and cumulative depreciation account codes resolved via the Chart of Accounts mapping. Accumulated depreciation entries are migrated as manual depreciation lines rather than automated journal entries for accountant verification.

Logo Go stock records migrate to Odoo stock.warehouse and stock.location models. If Logo Go provides warehouse-level stock quantities, we map them to Odoo stock.quant records linked to the resolved product.product and location_id. Stock valuation accounts are resolved via the Chart of Accounts mapping for inventory and cost of goods sold accounts. This mapping requires Logo Go database access to extract bin-level or warehouse-level stock data, which is confirmed during scoping.

Logo Go's localized Turkish and Middle Eastern tax codes (VAT, withholding tax, special consumption tax) map to Odoo account.tax records. We create tax templates during migration, and the customer's Odoo partner or accountant configures the tax grid mapping for Turkey's local fiscal reporting requirements. Tax groups from Logo Go map to account.tax.group. This mapping is inherently manual because Logo Go's localized tax configuration structure is not exposed in a standard schema.