Migrate from Streamleader to Odoo ERP

Streamleader Customer records map to Odoo res.partner with partner_category set to a Customer tag. The Streamleader customer name, contact details, billing address, and account code map to Odoo Partner fields (name, phone, email, street, city, property_customer_payment_method_id). We resolve the country/state lookup from Streamleader's address fields using Odoo's country_id and state_id relational fields. Where Streamleader exposes an account balance field, we note it for post-migration manual reconciliation in Odoo rather than as a migrated value.

Streamleader Vendor records map to Odoo res.partner with partner_category set to a Vendor tag. Vendor payment terms, bank details, and tax identification numbers migrate to Odoo Partner fields. We separate Customer and Vendor into distinct Partner records in Odoo even if Streamleader stores them in a single table; the category assignment is the primary differentiator in Odoo's accounting and purchasing workflows.

Streamleader Item records map to Odoo product.template with SKU from the Streamleader item code mapped to product.barcode or default_code. Unit of measure from Streamleader migrates to Odoo's uom.uom model with category matching (time, unit, weight). Pricing tiers from Streamleader require decision: we can create Odoo Pricelist entries per tier or collapse to a single list price, depending on the customer's pricing complexity. Custom item attributes migrate as Odoo attribute lines on the template.

Odoo's Chart of Accounts must be built before any transactional records import because every invoice, bill, and payment references an account_id. We configure the account types (receivable, payable, expense, revenue, other) and reconcile flags to match Streamleader's account structure as closely as possible. Australian tax codes (GST 10%) map to Odoo account.tax records with the appropriate tax_scope (AUS) and amount (10.0). This is the first schema element we configure and the one that gates all downstream record imports.

Streamleader open Accounts Payable records (unpaid vendor bills) migrate to Odoo account.move of type in_invoice, with the Partner field resolved to the corresponding Vendor Partner, the account_id resolved to the accounts payable account, and the invoice_date and invoice_date_due preserved from Streamleader. Line items map to invoice_lines with the product_id, quantity, and price_unit from Streamleader. We flag any partially paid bills for manual reconciliation in Odoo after migration because partial payment allocation requires a decision about whether to carry forward the payment or reset the bill to unpaid.

Streamleader open Accounts Receivable records (unpaid customer invoices) migrate to Odoo account.move of type out_invoice, with the Partner resolved to the Customer record, the accounts receivable account configured, and the invoice_date and invoice_date_due preserved. Line items migrate with product_id, quantity, and unit price from Streamleader. Any credit notes or overpayments on the Streamleader side map to Odoo account.move of type out_refund or in_refund respectively.

Historical transactions from Streamleader migrate as Odoo account.move entries of type entry (journal entries). We chunk exports by date range and validate line-item totals match the Streamleader source document totals. Full audit trail transfer is recommended for financial reporting continuity but is scoped separately because large transaction volumes can exceed Odoo's standard import performance and may require XML-RPC batch scripting or a custom import module. We agree on the historical lookback period during discovery before exporting.

Streamleader User records map to Odoo res.users with the email address as the login identifier. Role and permission names from Streamleader do not have a direct Odoo equivalent because Odoo uses record rules and access groups tied to installed apps. We map Streamleader role names to Odoo access rights per app (sales user, inventory user, accounting user, etc.) and flag any Streamleader permission that cannot be represented in Odoo's standard security model for the customer's admin to configure post-migration.

Streamleader's undocumented API means we cannot confirm whether binary document attachments (invoices, receipts, contracts, images) are accessible for export. We attempt API-based attachment discovery during the technical audit phase. If attachments are inaccessible, we document their locations by record and provide a manual file-transfer checklist for the customer's admin rather than claiming automated attachment migration.

Streamleader custom fields and any custom object structures discovered during API exploration map to Odoo custom fields via ir.model.fields or x_studio_field_name conventions depending on whether Odoo Studio is available in the destination plan. We pre-create the destination schema before any data import to satisfy referential integrity. Any Streamleader custom field that has no Odoo equivalent (due to different data types or missing apps) is flagged in the mapping document with a recommended workaround.