Migrate from Actito to Odoo CRM

Actito Profiles are the central record type and map directly to Odoo CRM Contacts. All standard profile attributes (email, name, phone, address fields) map to Contact fields. Custom profile attributes migrate as custom fields on the Contact model (ir.model.fields with res.partner as the model). We preserve the original Actito profile ID in a custom field actito_profile_id__c for reconciliation and cross-reference.

For profiles where the company_name attribute is populated and the profile represents a business rather than an individual, we create a separate res.partner record with is_company=True and link the Contact as a child. We use the Actito profile's company_name field to create the Company record and set the Contact's parent_id to the Company after both are inserted.

Actito Custom Tables linked to Profiles are translated into Odoo CRM as custom fields on res.partner (for profile-level attributes) or as a standalone custom model (for tables with a many-to-one relationship to profiles and their own attribute set). We inspect the table schema during scoping, create the Odoo field definitions (char, integer, float, boolean, date, datetime, selection, many2one, text) before migration, and import the data as contact custom field values.

Actito entities partition all resources (profiles, custom tables, campaigns, scenarios) within a licence. Odoo CRM uses the multi-company feature (res.company) to partition records. We map each Actito entity to a corresponding res.company record, configure multi-company rules in Odoo's access control (ir.rule), and assign Contact records to the correct company during import. If the customer has only one entity, no multi-company configuration is required.

Actito campaign configuration metadata (name, schedule, targeting criteria, channel) migrates as campaign records in Odoo Email Marketing. We map the campaign name, channel type, and targeting segment definition (as a written note referencing the Actito segment). We do not migrate campaign content or HTML templates; these require reconstruction in Odoo's WYSIWYG email builder. Push channel campaigns have no Odoo CRM equivalent and are documented as a gap.

Actito Scenarios (event-triggered automation workflows) are documented in a written inventory delivered to the customer. Each entry describes the trigger condition, branching logic, action steps, and API-call or webhook destinations. Odoo Studio Automations use a different trigger-action model; the customer or an Odoo partner rebuilds them post-migration. We do not implement Studio Automations as part of the data migration scope.

Actito subscription opt-in and preference data (double opt-in status, channel-level consent flags, subscription source, GDPR attributes) migrates as structured custom fields on the Contact record. Channel preferences (email, SMS, push, postal) map to boolean custom fields (e.g., consent_email__c, consent_sms__c). Preference dates and sources map to datetime and selection fields respectively. We preserve the full preference tree as a set of custom fields rather than a JSON blob for native Odoo filtering and segmentation.

Actito campaign interaction events (opens, clicks, bounces, unsubscribes) are exported via Actito's ETL or campaign reporting export. We migrate these as CRM Activities (crm.activity or note) on the relevant Contact record with the event type, timestamp, and campaign reference preserved in custom fields. Note: interaction events are generated by Actito's platform and exported from campaign reports rather than the standard API, so the customer must run the campaign export job before scoping.

Actito web tracking goals and behavioural event definitions migrate as Odoo CRM custom fields on Contact or as tags (mail.mt.tag) used for segmentation. Goal names and trigger conditions are documented as field labels; UTM source/medium/campaign values from Actito tracking URLs are stored in dedicated custom fields (utm_source__c, utm_medium__c, utm_campaign__c) for reporting continuity.

Actito segment-building rules (profile selection criteria using operators like 'is last month', 'has attribute equal to', 'belongs to') are translated into Odoo domain filter expressions and documented as an inventory. Complex criteria using Actito-specific temporal operators are noted as requiring manual rebuild in Odoo using the domain filter builder. Segment membership itself migrates as a contact tag (mail.mt.tag) for each Actito segment.

ETL jobs and webhook subscriptions defined in Actito are documented as a configuration inventory. Since webhook target URLs and ETL credentials are destination-specific, we preserve the job structure (schedule, source entity, export format) and flag endpoint URLs that must be reconfigured to point at Odoo or the customer's other systems. Odoo has an incoming webhook module (webhook module on apps.odoo.com) if the customer wants to receive external events.

Actito channel sender configurations (FROM name, reply-to, email address per channel) migrate to Odoo's outgoing mail server configuration (ir.mail_server). DNS authentication records (DKIM, SPF, return-path) must be reconfigured on the customer's mail infrastructure; we document the Actito DNS records as a checklist for the customer's IT team to reapply against Odoo's mail sending method.