Migrate from Camp Automation to Odoo CRM

Camp Automation Contacts map to Odoo res.partner records with contact_type set to 'contact'. The source email field maps to email, phone maps to phone, and the company association maps to parent_id pointing to a separate res.partner record with contact_type 'company'. We resolve the parent_id lookup before inserting child contacts so that the Contact-to-Company hierarchy is satisfied at import time. Any contact without a company association in Camp creates a standalone res.partner with no parent_id.

Camp Automation Company records map to Odoo res.partner with contact_type set to 'company'. The company name becomes the partner's name field (required in Odoo), domain maps to website, and industry and size fields map to custom res.partner fields that we pre-create during schema configuration. Company records insert before any dependent Contact records so that the parent_id foreign key constraint is satisfied during the Contact import phase.

Camp Automation Deals map to Odoo crm.lead records with type='opportunity'. The deal pipeline maps to a crm.team (sales team) in Odoo, and the deal stage maps to a stage_id within that team's pipeline. We pre-configure the pipeline stages in Odoo Studio during schema setup, mapping Camp stage names to Odoo stage names using a customer-provided stage matrix. Deal value, close date, and custom deal fields migrate directly once the stage mapping is validated.

Each Camp Automation deal pipeline becomes an Odoo crm.team with its own crm.stage sequence. Stage probability percentages from Camp map to Odoo's probability field on crm.lead. Stage names are preserved as-is where they match Odoo's default set (New, Qualified, Proposition, Won, Lost) and are created as custom stages where Camp uses non-standard names. Lost stage values from Camp map to Odoo's stage_id with type='lost'.

Camp Automation Campaigns are multi-channel parent objects with no direct Odoo CRM equivalent. Odoo does not have a native multi-channel Campaign object that spans email, SMS, social, and push in a single parent record. We create an Odoo crm.tag for each Camp Campaign (with the tag name set to the Campaign name) and tag all migrated activity records (emails, meetings, tasks) with the corresponding campaign reference. This preserves the campaign association in Odoo's tag filter while noting that the unified Campaign UI view will not exist in the destination.

Camp Automation email templates export as HTML with inline CSS and variable placeholders. We import them as Odoo mail.template records, preserving the subject line, body (as Odoo's email_from and body_html fields), and variable syntax. Odoo's mail.template uses Jinja-style {{ }} placeholders which we translate from Camp's placeholder format during the transform phase. Template categories from Camp map to mail.template's category_id.

Camp Automation workflows consisting of triggers (form submit, email open, deal stage change) and multi-branch action sequences do not migrate as automation logic to Odoo. The trigger-action model in Camp has no direct equivalent in Odoo's ir.actions.server framework, which uses server actions, automated actions, and base.action.rule with a different condition syntax. We deliver a written inventory of every active Camp workflow with its trigger type, conditions, and action sequence mapped to a recommended Odoo automated action or server action configuration. The customer's admin or an Odoo partner rebuilds these post-migration.

Camp Automation custom fields on Contacts are discovered through schema inspection (UI export or screen recording of the Contact settings page) before migration. We pre-create each custom field in Odoo using ir.model.fields with the correct field type: text fields map to char or text, date fields map to date, dropdown fields map to selection, and multi-select fields map to many2many or char with delimiter. Field types must be correct because incorrect types corrupt reporting filters and conditional views in Odoo that depend on field type.

Camp Automation custom fields on Deals require the same schema discovery process as Contact custom fields. We pre-create them as crm.lead custom fields using ir.model.fields before migration. Custom Deal fields that reference Contact lookups or Company lookups are created as many2one fields pointing to the correct model, and we ensure the foreign key values resolve correctly during the Deal import phase by running a pre-import validation pass.

Camp Automation tags on Contacts and Deals map to Odoo crm.tag records. The tag taxonomy is preserved exactly: each distinct tag label from Camp creates a crm.tag record in Odoo, and the tag assignments migrate as crm.lead.tag_ids entries linking each crm.lead to its tags. Tags that do not exist in the destination are created automatically during import. If the customer uses tags for content classification rather than deal segmentation, we discuss whether res.partner.category (which Odoo uses for partner categories) is a better target at scoping time.

Camp Automation Owners map to Odoo res.users records by email address. We resolve owners by email match against the destination Odoo instance's res.users table. Any Camp Owner without a matching res.users record enters a reconciliation queue for the customer's Odoo admin to provision before record import resumes. Inactive Odoo users can receive migrated records; active users are required for crm.lead assignment to function correctly in Odoo's activity and team assignments.

Camp Automation campaign activity records (email sends, SMS sends, social posts, push notifications) do not have native Odoo CRM equivalents as a unified object set. Email activities migrate as mail.mail records linked to the crm.lead via the res.partner. Meeting activities migrate as calendar.event records. Call and task activities migrate as mail.activity records with activity_type_id mapped to the nearest Odoo activity type. Social and push activity data migrates as notes attached to the related crm.lead, with the channel reference preserved in the note body. The campaign tag association documented in the Campaign mapping preserves the cross-activity relationship.

Camp Automation landing page forms and inline web forms export with field configurations and submission data. Odoo does not have a native form builder within its CRM module; website forms typically live in Odoo Website with the crm.lead creation handled by an ir.config.parameter setting. We migrate form submission data as crm.lead records with the original form name stored in a custom source field (x_form_name) and submission timestamp stored in create_date. Form field values map to crm.lead custom fields using the field mapping documented during discovery.