Migrate from SoftLedger to Odoo ERP

SoftLedger Locations are the top-level entity objects, each with its own currency, address, and COA inheritance. We map each Location to an Odoo Company record, configuring the functional currency, address, and fiscal year settings per entity. For single-location SoftLedger accounts, this maps to one Odoo Company. For multi-location accounts, each SoftLedger Location becomes a separate Odoo Company. We also configure the multi-company access rights so users see only the entities they are assigned to. Intercompany eliminations require a dedicated services company in Odoo with dedicated elimination journals; SoftLedger's consolidation settings do not auto-transfer.

SoftLedger's per-location COA includes account number, name, type (Asset, Liability, Equity, Revenue, Expense), tax code assignment, and status. We extract the full COA per entity, map the account types to Odoo's internal type taxonomy, and create corresponding account codes in Odoo's Accounting > Configuration > Chart of Accounts. SoftLedger's account-level tax code assignments map to Odoo's tax tags. Odoo's fiscal localization (US, EU, FR, DE, etc.) affects the default COA template; we overlay the migrated SoftLedger COA on the applicable localization template so tax reporting and statutory filing remain intact.

SoftLedger Customers migrate to Odoo Contacts with the Customer flag enabled. Fields map directly: name, email, phone, street, city, state, zip, country. Payment terms migrate to Odoo Property Payment Term on the partner. The SoftLedger currency assignment maps to the partner's property_supplier_currency and property_customer_currency where Odoo supports per-partner currency. Custom fields on Customer records transfer to Odoo custom fields on res.partner. Open AR balances migrate as open journal items against the appropriate receivable account after the Customer record is created.

SoftLedger Vendors migrate to Odoo Contacts with the Supplier flag enabled, mirroring the Customer migration pattern. SoftLedger-specific fields like 1099 eligibility map to Odoo's US tax fields (l10n_us_1099 field where the Odoo US localization is installed). Payment terms migrate to the supplier's property_supplier_payment_term. Custom fields on Vendor records transfer to res.partner custom fields. Outstanding AP balances are migrated as open vendor bill lines after the Vendor record is established in Odoo.

SoftLedger Journal Entries with multi-currency lines migrate to Odoo Account Moves. Each SoftLedger journal line maps to a move line with debit/credit amounts, account reference, and optional analytic account. For multi-currency entries, we preserve the SoftLedger exchange rate override metadata as the Odoo move line's currency_id and amount_currency, applying the override rate rather than Odoo's standard rate. Dimensional tags from SoftLedger (department, cost center) map to Odoo Analytic Account tags on the move lines. Source references and transaction narratives transfer to the Account Move's ref field for audit traceability.

SoftLedger AR Invoices migrate to Odoo Customer Invoices. The invoice status (open, closed, paid, void) is preserved as Odoo's state (draft, posted, paid, cancelled). Line items map to Odoo move lines with the correct account, quantity, and price unit. Tax lines map to Odoo's tax lines with the applicable tax tag. Payment terms from SoftLedger migrate to Odoo's invoice payment term assignment. For open invoices, the journal item matches against the customer's open receivable balance so that aged receivable reports in Odoo reflect the migrated state correctly. Closed and void invoices migrate as historical records with their final state preserved.

SoftLedger AP Invoices migrate to Odoo Vendor Bills following the same line-item and tax mapping pattern as AR Invoices. Open AP invoices create matching journal items against the appropriate vendor payable account so that aged payable reports in Odoo reflect outstanding vendor balances. Closed and void AP invoices migrate as historical records. SoftLedger's 1099 category assignments transfer to Odoo's US tax fields where the Odoo US localization is in use.

SoftLedger Bank Transactions linked to Journal Entries map to Odoo bank journal moves. The critical requirement is reconciliation status: unreconciled items in SoftLedger must land as unreconciled bank statement lines in Odoo so that the Odoo reconciliation widget captures outstanding items and the bank reconciliation process resumes from where it left off in SoftLedger. Reconciled items migrate as matched lines with the reconciliation ID preserved in the Odoo move line's reconciliation record. We set the bank statement's ending balance to match SoftLedger's reconciled balance for the bank account so that Odoo's reconciliation report opens at the correct starting position.

SoftLedger uses a dedicated Beginning Balance upload mechanism rather than standard journal entry posting to seed opening balances. We use SoftLedger's beginning balance endpoint to extract the trial balance by entity and account, then create Odoo opening entries using the dedicated opening journal (a configurable journal with the special Odoo opening entry flag). Each account's opening debit or credit populates the Account Move line with the account reference and balance. This ensures the trial balance in Odoo reflects the correct opening position from day one without distorting the prior period through a raw journal post. Multi-entity balances are seeded per Company in Odoo with the corresponding account references resolved.

SoftLedger supports Custom Fields on standard objects including Customer, Vendor, Invoice Lines, and Journal Lines. We discover all active custom fields during scoping, capture their data types (text, number, date, select, multi-select), and create equivalent Odoo custom fields on the corresponding res.partner or account.move.line models via Odoo's Settings > Technical > Custom Fields interface (or directly in the database for batch creation). Values transfer field-by-field with type coercion applied where the destination field type differs. Any custom fields without a destination equivalent are flagged in the scoping report for the customer to resolve before migration.

SoftLedger Dimensions tag journal lines with organizational attributes such as department, cost center, project, or region. We preserve the full dimension schema and all tag assignments during migration. In Odoo, Dimensions map to Analytic Accounts (a.plan model), which tag move lines with cost-center or project-level tracking. We create the Analytic Account structure matching the SoftLedger dimension hierarchy, and apply the tags to each migrated journal line and invoice line. Reporting continuity is maintained by ensuring that the Analytic Account dimension appears on the same report layouts the finance team uses in SoftLedger.

SoftLedger custom report definitions store account ID references and report layout configurations. These cannot migrate as executable code to Odoo because Odoo's report engine uses a different structure (QWeb templates, external IDs, and report paper format). We extract the full report JSON configuration, identify every referenced account ID, and map those IDs to their Odoo account equivalents. We deliver a written report inventory document that lists each SoftLedger report, its account composition, its filters and groupings, and the recommended Odoo equivalent (native financial report or custom report built via Odoo Studio). The customer's Odoo partner or finance admin rebuilds the reports post-migration using this document.