Migrate from Certinia ERP Cloud to Odoo ERP

Certinia Accounts map to Odoo Res.partner records with the customer flag set to True. The Account Name becomes partner name, billing address maps to the partner's invoice address fields, and shipping address maps to delivery fields. We preserve the multi-entity entity assignment as a custom field or separate Company record depending on the destination Odoo configuration. External ID from Certinia becomes the partner's external_id for reconciliation.

Certinia Contacts map to Odoo Res.partner records with individual type. Contact roles, related Account (partner) lookup, and email/phone/address fields migrate directly. Custom fields added by Certinia packages migrate as custom partner fields in Odoo.

Certinia Opportunities map to Odoo CRM Leads and Opportunities. The Opportunity stage maps to the Odoo stage_id with a stage name translation. Estimated hours and project start date fields from Certinia PSA extensions become custom lead fields. Owner (Salesforce User) maps to the Odoo user_id on the crm.lead record.

Certinia PSA Projects map to Odoo project.project records. Milestones map to Odoo task stages or sub-task milestones depending on the milestone dependency structure. Project status (Active, On Hold, Completed) maps directly. Custom project statuses require Odoo stage configuration before migration.

Certinia PSA Assignments (Resource bookings against Projects) map to Odoo planning allocatEon records if the Odoo Planning app is installed, or to project.task records with assignee fields. Allocation percentage, booking dates, and skills migrate as custom fields. Skillsets stored as custom fields on the Assignment record require Odoo skill configuration or a custom many2many field.

Certinia PSA Budgets (planned vs. actual cost/revenue by Project) map to Odoo project.budget if using Odoo Industry: Project Management, or to account.budget.post with crossovered.cudget.lines for financial budgets. Rate-based, fixed-fee, and expense-only budget types each carry different field sets; we type-tag the migration records so the correct Odoo budget structure is applied during import.

Certinia Billing Events generate Invoices in Certinia. Each Billing Event header and its linked time entry and expense line items become an Odoo account.move (Customer Invoice). Line-level billing rates, quantities, and descriptions map to invoice lines. We split multi-line Billing Events into one Odoo invoice per event header, preserving the invoice-to-project link via a custom field.

Certinia Invoices (posted) map to Odoo account.move records with move_type = out_invoice. Invoice headers and line items migrate directly. Payment records linked to the invoice require AR record migration in the same run to maintain open-invoice integrity. Payment state maps to Odoo's payment_state field (paid, partial, unpaid).

Certinia POs and AP records map to Odoo account.move with move_type = in_invoice. Vendor name resolves to the Odoo Res.partner vendor record. PO approval status cannot be migrated as Odoo approval workflows are separate; we flag approval history for manual records. Open PO status is preserved as a draft bill to be approved post-migration.

Certinia Financial Management Fixed Asset records map to Odoo account.asset.asset. Depreciation schedules, asset categories, and book values migrate directly. The asset profile (depreciation method, useful life,Salvage value) maps to Odoo's asset profile configuration. Depreciation entry lines become Odoo asset depreciation lines posted to the general ledger.

Certinia GL entries with multi-dimensional analysis fields (region, department, project) require Odoo's analytic accounting and dimension configuration before posting. We stage the entry data, configure Odoo Analytic Plans (Account, Project, Department dimensions) during setup, then import GL lines with the correct analytic account references resolved. Unmapped account codes are flagged before the import run to prevent posting errors.

Certinia Users (Salesforce Users with PSA Resource attributes) map to Odoo res.users. We match by email address. PSA resource skills, utilization targets, and cost rates stored on the Resource record migrate as custom user fields. Any Certinia User without a matching Odoo user goes to a reconciliation queue for the customer to provision before record import resumes.

Certinia custom objects built within the managed package and accessible via Salesforce API migrate to Odoo custom models created via the Studio or Python. We pre-create the destination model with the same field names and types, then import the data with external IDs preserved for cross-record linkage.