Migrate from WP ERP to Odoo ERP

WP ERP employee records in erp_hr_employees map to Odoo hr.employee. We resolve the wp_user_id foreign key to pull the WordPress user display name, email, and role, then create the hr.employee record with name, work email, department_id (mapped from erp_hr_departments), job_title, hire_date, and employment status (employment_status field). Compensation data from the HRM module (salary, pay frequency) maps to hr.contract records linked to the employee. Department tree is migrated first so that employee.department_id references are satisfied during employee import.

WP ERP department records in erp_hr_departments use a simple parent_id hierarchy. We migrate the department tree top-down, preserving the parent-child structure in Odoo's hr.department model where each department has a manager_id (resolved from the migrated hr.employee record) and a parent_id pointing to the parent department. Departments must migrate before employees so that department_id foreign keys are valid at employee insert time.

WP ERP CRM contacts map to Odoo res.partner. WP ERP stores individuals (contacts) and organizations (companies) as separate tables (erp_crm_contacts and erp_crm_companies), while Odoo uses a single res.partner model with an is_company toggle. We map WP ERP contacts where is_crm_company=0 to res.partner with is_company=False, and WP ERP companies to res.partner with is_company=True. The lifecycle_stage and source attribution from WP ERP migrate as custom Char fields on res.partner. When WooCommerce CRM integration is active, we detect duplicate contact candidates (same email in both manual CRM contacts and WooCommerce order records) and give the customer the choice to merge before export.

WP ERP company records map to Odoo res.partner with is_company=True. The company name, billing address, phone, website (domain field), and industry classification migrate directly. Company-to-contact relationships stored in erp_crm_contact_relations are preserved as child res.partner records linked to the parent company partner. Company IDs are remapped during migration to match Odoo's sequential partner ID generation, and the mapping table is maintained so that any deal associations reference the correct partner.

WP ERP Deals ($9.49/mo extension) map to Odoo crm.lead. Deal title, value, currency, stage, owner (hubspot_owner_id resolved to Odoo res_users), and pipeline association migrate to crm.lead fields (name, planned_revenue, currency_id, stage_id, user_id, team_id). WP ERP pipeline stages are mapped to Odoo stage names within the crm.lead stage pipeline configuration. The deal_currency field from WP ERP maps to Odoo's currency_id using ISO 4217 currency codes. Deals without a linked contact or company are migrated as unassigned leads for the customer admin to route.

WP ERP CRM activities (calls, meetings, emails, tasks, notes) stored in erp_crm_activities with polymorphic type fields map to Odoo mail.message records linked to the parent res.partner or crm.lead. Each activity type maps to a different Odoo model: calls and tasks become mail.message with subtype indicating call or task; emails become mail.message with email=True; meetings create calendar.event records linked via mail.message. Notes migrate as mail.message with note=True. We preserve the original activity timestamp and the owner (resolved via wp_user_id to Odoo res_users) for audit continuity.

WP ERP Chart of Accounts in erp_ac_chart_of_accounts maps to Odoo account.account records. The primary challenge is translating WP ERP's flat COA with type and subtype fields into Odoo's structured account type hierarchy (view, receivable, payable, liquidity, revenue, expense, etc.). We map WP ERP account types (Asset, Liability, Equity, Income, Expense) to Odoo account.account.account_type values, and preserve the parent-child account grouping in Odoo's account.group model for financial statement structuring. Account codes are mapped directly; the customer configures Odoo's account_digits setting to match WP ERP's code length before import.

WP ERP accounting customers in erp_ac_customers link to CRM contacts via erp_crm_contacts.id. We resolve this cross-reference during migration so that the accounting customer lands as the same res.partner record as the CRM contact, with customer_rank elevated and the account_receivable account assigned from the mapped COA. Any open receivable balance from WP ERP's accounting ledger migrates as a start_balance on the res.partner record.

WP ERP vendor records in erp_ac_vendors map to Odoo res.partner with supplier=True. We migrate the vendor name, billing address, contact email, and phone. Vendor-ledger entries in the accounting module link via the vendor_id foreign key to the partner record. The account_payable account from the mapped COA is assigned to the vendor partner record in Odoo.

WP ERP invoices in erp_ac_invoices map to Odoo account.move records with move_type set to out_invoice (customer) or in_invoice (vendor). We extract line items, tax codes (mapped to Odoo account.tax records using the tax name as the dedupe key), payment status, and due date. WP ERP invoice status (open, paid, voided) maps to Odoo's state field (draft, posted, cancel). Open invoices migrate as posted journal items against the correct receivable or payable account. Closed invoices migrate with state=posted and the payment reconciliation recorded against the bank journal. We flag any partially paid invoices for manual reconciliation in Odoo after import.

WP ERP journal entries in erp_ac_journal_entries (both manual entries and those generated by the Payroll module) map to Odoo account.move records with move_type=entry. Each journal entry's debit and credit line items are mapped to Odoo account.move.line records with the correct account_id resolved from the COA mapping, partner_id for receivable/payable lines, and analytic_account_id if analytic dimensions exist in the WP ERP entry. Payroll-generated journal entries are imported as entry moves with a payroll reference in the narration field for audit trail purposes.

WP ERP Payroll extension ($9.49/mo) historical payslip records in erp_hr_payroll* tables map to Odoo hr.payslip records linked to the corresponding hr.employee. We extract payslip date, worked days, inputs (allowances, deductions), and the computed net pay. Payslip PDFs are not regenerated by Odoo; if the customer requires payslip documents for compliance, they must either regenerate them in Odoo using the payslip data or retain the original WP ERP PDFs as an archive. We document this as a post-migration action item.