Migrate from Keap to Odoo CRM

Keap Contacts map to Odoo res.partner records. Standard fields (name, email, phone, address) map directly. Custom fields on the Keap contact must be pre-created in Odoo via Studio or the UI before import because Odoo requires the field to exist before data can be written. We retrieve the Keap contact model schema via the REST API to enumerate all active custom field IDs and their labels, then the customer creates matching fields in Odoo before migration. Keap's tag assignments on contacts map to Odoo Tags (ir.attachments with res_model='res.partner') and optionally to a custom Char field tracking the primary tag for routing.

Keap Company records map to Odoo res.partner records with company_type='company' distinct from person-type Partners. The Company-to-Contact association in Keap becomes a child-partner relationship in Odoo. We import companies first in the load order so that the parent reference is satisfied before contact records are inserted. The company domain from Keap populates the Odoo Partner website field.

Keap Tags serve dual purposes: contact segmentation and automation triggers. We export all tags as Odoo Tags (ir.attachments tagged to res.partner) for segmentation. For tags that drive automation logic in Keap, we map them to Odoo Stage names on CRM Opportunities or to a custom Char field that triggers Odoo Studio automated actions. The customer chooses the strategy during scoping because the correct approach depends on how deeply the sales team relies on tag-based routing.

Keap Opportunities map to Odoo crm.lead records in the CRM pipeline. Keap's user-defined stage names become Odoo Stage values in the CRM Stage configuration. We create the target stages in Odoo via the CRM pipeline settings UI before migration so that stage references are satisfied at insert time. Deal value maps to Odoo's expected_revenue field. The opportunity owner in Keap maps to the Odoo User responsible field, resolved by email match against Odoo's res.users table. Expected close date maps to date_deadline.

Keap Invoice records map to Odoo account.move records with move_type='out_invoice' (for sales invoices). Line items map to account.move.line records. Keap's invoice status (draft, sent, paid) maps to Odoo's state field (draft, posted, cancelled). The Keap invoice-to-contact link becomes the Odoo partner_id on the account.move. We query the Keap invoice API endpoint directly rather than relying on deal activity logs, bypassing Keap known issue #3275175 where the pipeline UI does not display invoice activity lines.

Keap Products map to Odoo product.template records. Fields include name, default_code (SKU), list_price, and description. Product images and advanced attributes (such as weight, dimensions, or lot numbers) require Odoo Inventory app activation and are migrated as additional fields on the template or as product.attribute records if the customer uses variants.

Keap Orders map to Odoo sale.order records if the Odoo Sale app is active, or to account.move records if only accounting is in scope. Order line items map to sale.order.line with product and quantity resolved via the product mapping. Payment status from Keap (pending, paid, refunded) maps to Odoo's order state or invoice state depending on the scope.

Keap Tasks map to Odoo project.task records if the Project app is active, or to mail.message records attached to the relevant Partner or CRM Opportunity. We preserve the task subject, due date, assigned user (resolved by email), status (todo, complete), and completion timestamp. Tasks linked to specific contacts or opportunities in Keap attach to the corresponding Odoo record via the res_model and res_id context.

Keap Notes map to Odoo mail.message records attached to the relevant res.partner or crm.lead. We preserve the note content as the message body, the author name, and the creation timestamp. If the Odoo Discussion app is active, notes appear in the chatter; otherwise they land as internal notes visible in the record history.

Keap automation sequences cannot be exported in structured form via API. We export the sequence names, step counts, trigger conditions (tag names), and any associated email campaign names as a written inventory document. The customer's Odoo administrator or a certified Odoo silver partner uses this inventory to rebuild sequences in Odoo Studio automated actions and server actions. This is a manual step outside our migration scope.

Keap landing pages and web forms cannot be exported via API. We document the URLs, form field structures, and any custom field IDs captured by each form as a written handoff for the customer's marketing team to re-create in Odoo Website builder forms or a third-party form tool of their choice.

Keap user accounts (name, email, role, permissions) map to Odoo res.users records. We resolve by email match. Any Keap user without a matching Odoo account goes to a reconciliation queue for the customer's admin to provision. Odoo's access rights groups (Administrator, User, Portal) map from Keap's role hierarchy, with the caveat that Keap's permission model and Odoo's groups-based security are structurally different and may require manual adjustment post-migration.