Migrate from Apptivo to Odoo CRM

Apptivo Contacts with lead status or source tracking map to Odoo crm.lead (Lead). Apptivo Contacts attached to a Customer record with closed or active status map to Odoo res.partner (Contact) linked to an Account. The split rule is defined during scoping based on the customer's Apptivo status field values and lifecycle stage mapping. We preserve the original Apptivo contact ID in a custom char field on both the Odoo Lead and Contact for audit traceability.

Apptivo Customers are B2B company records with billing address, shipping address, and associated contacts. They map directly to Odoo res.partner with is_company=True. The customer name becomes the partner display name, billing address migrates as the partner address (type=default), and additional addresses migrate as res.partner child records with type=delivery or type=invoice. We resolve the Customer-to-Contact link before importing Contact records so that each res.partner Contact can be linked to its parent company partner.

Apptivo Leads export directly as Odoo crm.lead records. Lead scoring values, source tracking fields, and lifecycle stage from Apptivo map to custom integer and char fields on the Odoo Lead. The Apptivo lead status (New, Contacted, Qualified, Converted) maps to Odoo Lead status. Lead priority maps to Odoo priority (0-3 scale). Owner assignment migrates by email match to Odoo res.users.

Apptivo Opportunities map to Odoo crm.lead with type='opportunity'. The Apptivo pipeline stage names and probabilities map to Odoo Kanban stage names and on_change probabilities defined in the crm.stage model. We configure the Odoo Pipeline and stages (crm.team + crm.stage) before migration begins so that stage mapping is resolved at import time. Expected close date, deal amount, and probability migrate to Odoo's date_deadline, planned_revenue, and probability fields.

Each Apptivo Opportunity pipeline and its stage sequence becomes an Odoo crm.team (pipeline) with an ordered set of crm.stage records. We create the Odoo stages with the same sequence order as Apptivo, copy stage probability percentages to crm.stage.probability, and set stage_type to readonly for migrated stages. This is the first Odoo configuration step because all Opportunity records depend on a valid stage_id.

Apptivo Cases map to Odoo helpdesk.ticket. Ticket status (Open, In Progress, Resolved, Closed) maps to Odoo ticket stage_id. Priority migrates to Odoo priority. The Apptivo case owner becomes the helpdesk.ticket user_id via email match to Odoo res.users. Conversation threads from the Apptivo case messaging log migrate as mail.message records linked to the helpdesk.ticket via res_model='helpdesk.ticket' and res_id=ticket_id. Customer Portal access flags do not migrate; we document the access levels for the Odoo Helpdesk portal configuration step.

Apptivo Projects map to Odoo project.project records. Project name, description, start date, and deadline migrate directly. Apptivo project tasks migrate to Odoo project.task records linked to the parent project.project via project_id. Task hierarchy (milestones, sub-tasks) is reconstructed from Apptivo task parent_id relationships. Project assignment to employees maps via email match to Odoo res.users. Custom project-level attributes from Apptivo's Master Layout migrate as custom char or selection fields on project.project depending on the field type.

Apptivo Employee records (name, job title, department, contact info) map to Odoo hr.employee. We match by work email to Odoo res.users and link the hr.employee record to the matched user. Department names from Apptivo create or link to Odoo hr.department records during migration. Employment status (Active, Inactive) maps to Odoo active field.

Apptivo Items (product and service catalog) map to Odoo product.product with type set to 'product' or 'service' based on the Apptivo item type field. Item name, description, unit of measure, and standard price migrate directly. Custom attributes on Items (text, number, date, dropdown) map to product.product custom fields created in Odoo Studio before import. Items without a unit price become Odoo product.product records with list_price=0.

Apptivo Invoices map to Odoo account.move records with move_type='out_invoice'. Invoice header data (customer reference, date, due date, total amount) migrates to Odoo account.move fields. Line items linked to Items in Apptivo map to Odoo account.move.line records with product_id, quantity, price_unit, and tax links resolved from the product.product lookup. Partial payment history migrates as Odoo account.payment records linked to the original invoice. Note that we do not migrate the Odoo accounting configuration (chart of accounts, taxes, payment terms) as these require post-migration Odoo accounting setup by the customer's finance team.

Apptivo per-app Master Layout attributes are the highest-risk migration artifact. Each Apptivo app has an independent attribute set, so a field called 'Region' in the Contacts app is a different field from 'Region' in the Cases app. We enumerate all custom attributes per app during discovery, create matching Odoo custom fields (char, selection, integer, float, date, datetime, many2one, text) via Odoo Studio before any data import, and build a per-app field mapping table that prevents silent field collisions or dropped custom data. Custom attribute values are migrated as values on the corresponding Odoo record after the destination field is created.

Apptivo file attachments (stored against Contacts, Cases, Opportunities, and Projects) migrate as Odoo ir.attachment records. We export the file blob and filename from Apptivo, then insert into Odoo's ir.attachment table with res_model set to the corresponding Odoo model (res.partner, crm.lead, helpdesk.ticket, project.project) and res_id set to the migrated record's Odoo ID. The attachment name maps from the original Apptivo filename. Large attachments are chunked during export to avoid Apptivo's file size limits.