Migrate from Foundry Bean to Odoo ERP

Foundry Bean accounts organized into Balance Sheet and Income Statement categories map to Odoo ERP Account records. Each Foundry Bean account code becomes the Odoo code field, account type maps to Odoo account type (receivable, payable, asset, liability, equity, income, expense), and the reconciliation flag is set based on the Foundry Bean account's use in open receivables or payables. Multi-company configurations in Odoo require a distinct account chart per company record.

Foundry Bean Customer records map to Odoo Partner with the Customer flag enabled. Address, contact, payment terms, and currency assignment migrate directly. Custom fields on Foundry Bean customer records require explicit value mapping to Odoo custom partner fields. Foundry Bean's customer-linked receivables map to Odoo Account Receivable moves during invoice import.

Foundry Bean Vendor records map to Odoo Partner with the Supplier flag enabled. Banking information, addresses, purchase terms, and vendor-linked payables migrate directly. The vendor's currency assignment maps to Odoo's property_purchase_currency field. Foundry Bean's vendor-linked purchase orders map to Odoo Purchase Order records in a subsequent phase.

Foundry Bean Employee records including compensation history, benefits, and organizational assignments map to Odoo Employees. Effective-dated changes in Foundry Bean require careful sequencing; we import current employment state first as the primary Employee record, then apply historical compensation entries as Odoo timesheet or hr. payslip records where applicable. Organizational hierarchy maps to Odoo department and job titles.

Foundry Bean Items with inventory tracking across multiple warehouses and locations map to Odoo Product records. Item numbers become Odoo default_code, costing methods (standard, average, FIFO) map to Odoo cost_method, and warehouse assignments map to Odoo warehouse-specific routes and pull/stock rules. Custom pricing tiers on Foundry Bean items are flagged for manual pricing list configuration in Odoo.

Foundry Bean sales invoices, recurring invoices, and subscription-generated invoices map to Odoo Account Move records with move_type=out_invoice. Vendor invoices map to Odoo move_type=in_invoice. Invoice-to-payment linkages migrate as Odoo payment records linked to the same account move, preserving aging data. Invoice status from Foundry Bean (draft, open, paid, void) maps to Odoo's state field (draft, posted, paid, cancelled).

Foundry Bean approved expense reports auto-convert to vendor invoices, requiring a pre-export suppression strategy. We capture the approval workflow state before conversion, export the source expense report with its settlement status, and apply a flag to suppress the duplicate invoice record that would otherwise be created from the same source document. Mapped Odoo Expense records reconcile to accounting entries through Odoo's Expense app without the auto-invoice behavior Foundry Bean exhibits.

Foundry Bean Subscription records with flat-fee, usage-based, and volume pricing map directly to Odoo Subscription. Tiered pricing subscriptions store rate definitions as nested start-threshold, end-threshold, and per-unit-rate objects that do not map directly to flat Odoo pricing fields. We flatten each tier definition into individual rate records during transformation and generate Odoo pricing rule lines, flagging any subscription that relies on tier stacking for manual pricing list review in Odoo Subscriptions.

Foundry Bean Contract records link to subscription billing and revenue recognition schedules. Each contract maps to an Odoo Contract record, and if the contract drives recurring billing, we also create a linked Odoo Subscription. The Foundry Bean recognition method (milestone, time-based, percentage-of-completion) maps to Odoo's revenue recognition model configuration. ASC 606 schedules are recalculated from the contract data in Odoo rather than imported as static records.

Foundry Bean Purchase Orders map to Odoo Purchase Order records. Vendor assignment, item lines, quantities, and pricing migrate directly. The PO-to-invoice relationship is preserved: Foundry Bean's received and invoiced quantities map to Odoo's qty_received and qty_invoiced fields. Purchase order history (open and closed) migrates for procure-to-pay audit trails.

Foundry Bean bank and credit card accounts with real-time balance tracking and auto-reconciliation map to Odoo Bank Account records linked to an Odoo Bank Journal. Account numbers, bank details, and opening balances migrate to Odoo's account_number and bank_id fields, with opening balance set as an Odoo bank statement opening balance entry.

All Foundry Bean journal entries from bank reconciliation, invoice processing, and manual entries stored chronologically migrate to Odoo Account Move records. Each move preserves line-level debits and credits, account assignments, memo, and date. Adjustment entries and historical ledger balances migrate in date order, with the earliest open period migrated first to establish Odoo's account opening balances.

Foundry Bean ASC 606 recognition schedules are derived objects that must be recalculated in Odoo rather than imported as static records. We extract the underlying contract terms, subscription billing data, recognition method (milestone or time-based), and recognized-to-date amounts. Odoo Subscription's revenue recognition configuration is set to the same ASC 606 method identified in Foundry Bean. Any amounts already recognized in Foundry Bean become Odoo deferred revenue journal entries with the recognized portion applied on the recognition start date.

Foundry Bean custom objects catalogued during discovery migrate to Odoo custom model records using Odoo's ir.model and ir.model.fields framework. We pre-create the destination schema including all custom fields, field types, and relational mappings before data import. Custom object naming is preserved with Odoo's standard naming conventions, and any lookup relationships to standard objects (Customer, Vendor, Item) are resolved at migration time using the standard object mapping.