Migrate from Runple to Odoo ERP

Runple Customer records map to Odoo res.partner with partner_type=contact. We extract name, email, phone, street address, VAT number, and tax identification fields, preserving them in Odoo's partner fields. Runple's custom tax code properties map to Odoo's fiscal_position rules if the customer has multi-country invoicing. Country-specific address formats (Austrian postal codes, German street conventions) are preserved as freeform text during migration.

Runple Products (SKU, name, description, unit price, cost) map to Odoo product.template with product_type=product or product_type=service. Runple's item-level stock tracking maps to Odoo's product qty_on_hand via stock.quant records. We preserve the original SKU in product.default_code and map Runple's cost field to Odoo's standard_price for margin reporting. Products without stock tracking in Runple map as consumable or service products.

Runple Invoices (line items, tax codes, totals, currency, payment status) map to Odoo account.move with move_type=out_invoice or in_invoice. The Runple invoice number sequence maps to Odoo's name sequence field. Tax codes are mapped to Odoo account.tax records; if no matching Odoo tax exists, we flag it for the customer's admin to configure before import. Paid invoices migrate as posted moves; unpaid invoices migrate as draft moves with open journal items.

Runple Payments linked to invoices map to Odoo account.payment records with payment_method_line matched to the invoice's journal. We resolve the partner_id from the invoice mapping and preserve payment date, amount, and method (bank transfer, credit card, cash). Standalone payments without invoice links migrate as miscellaneous payments against the appropriate bank or cash account.

Outstanding payables and receivables require careful mapping of aging buckets, due dates, and residual amounts. We extract current open items from Runple and map them to Odoo account.move.line records in draft state. The reconciliation is handled post-migration by Odoo's auto-reconciliation wizard or manual reconciliation view. Any historical aging data is preserved in a note field for audit.

Runple stock levels map to Odoo stock.quant with location_id resolved to the default warehouse's stock location. Stock movement history maps to stock.move records with reference back to the source Runple transaction ID. If Runple used multiple warehouse locations, we create corresponding Odoo stock.location records and map inventory levels accordingly. Runple's warehouse assignments that do not have a direct Odoo equivalent are flagged for the customer's admin to configure post-migration.

Runple's EU VAT-compliant tax codes require manual mapping to Odoo's account.tax records because Odoo uses country-specific chart of accounts with built-in tax templates. We extract the Runple tax code list during scoping and deliver a mapping table for the customer's admin to configure Odoo taxes before invoice import begins. Reverse-charge rules and intra-EU VAT handling require separate Odoo fiscal position configuration.

Runple user accounts with roles and permissions must be remapped to Odoo's access rights model. We extract Runple role assignments and map them to Odoo access groups (res.groups) during scoping. Odoo's granular group-based permissions (Sales Manager, Account User, Inventory User, etc.) require the customer's admin to assign groups post-migration; we cannot infer the appropriate Odoo permission set from Runple's internal role model without a role inventory from the customer.

Commission data stored as HR-adjacent records in Runple require field-level mapping because Odoo accounting does not have a native commission tracking object. We map commission amounts to custom decimal fields on account.move.line or store them as internal notes on the related invoice. The customer chooses the approach during scoping based on whether commission reporting requires native Odoo views.

Time tracking data from Runple (hours, dates, employee assignments) is mapped to a custom timesheet model or stored as notes if the Odoo Timesheet app is not included in the destination configuration. We extract the data and present both options to the customer during scoping; the choice depends on whether the customer's admin activates the Odoo Timesheet module post-migration.