Migrate from Ortto to Odoo CRM

Ortto People map to Odoo CRM Contact records. We resolve the Person-to-Account linkage by first creating the Account record from Ortto's linked Organization (Account), then attaching the Contact with the account_id lookup. Ortto lifecycle_stage maps to a custom contact field stage_level__c because Odoo CRM does not have a native lifecycle stage property. Email, phone, address, and location fields migrate directly. Custom fields up to 100 are mapped to Odoo custom fields created in Studio before migration.

Ortto Accounts (Organizations) map directly to Odoo CRM Account (Company) records. The account API name and domain fields transfer to Odoo's Account Name and Website. We preserve the up-to-3,000-person link count in a custom field org_contact_count__c for reference. Ortto custom fields (up to 25) map to Odoo custom fields. The Accounts API endpoint is separate from People and we process Accounts first to satisfy the parent-account lookup on Contact insert.

Ortto tags are first-class objects in the API and are stored as a tag assignment per Person. We export the full tag taxonomy and tag-to-person mapping, then recreate tags in Odoo using the contacts.tag_ids multi-valued relationship. Tags that do not exist in Odoo are created during the import phase. The tag taxonomy (groupings, categories) is preserved as Odoo tags with the original tag names for post-migration reorganization.

Ortto Activities (behavioral events: email opens, form submissions, calls, meetings, custom events) are split into Odoo-native objects: calls map to Odoo CRM Call records, meetings map to Odoo Calendar Meeting records, and generic notes map to Odoo Note records. The Activity API returns up to 100 records per paginated feed view; we iterate through pages using ActivityDate ordering and preserve the feed sequence in a custom activity_sequence__c field. Custom event types from Ortto are mapped to Note records with the event name stored in the note body or a custom field.

Ortto Audiences are dynamic or static segments of People. Odoo CRM does not have a native segment object, so we convert audience membership into a combination of Odoo tags (for dynamic segments) and contact groups via the mail.group model (for static lists). We document the segment definition rules (field conditions, date ranges, tag filters) in a written segment inventory so the customer can rebuild audience logic in Odoo using Studio-based filters or a dedicated marketing integration.

Ortto Campaigns (email, SMS, push) are marketing containers that group messages and track performance. Odoo CRM does not have a campaign object within the CRM module alone. We tag Contact records with campaign names from Ortto using a dedicated campaign__c tag, and we document campaign performance metrics (open rate, click rate, send volume) in a written campaign inventory for the customer's admin to reference when rebuilding campaigns in Odoo Marketing (a separate Odoo module outside CRM scope) or a third-party email platform.

Ortto custom fields on People (up to 100) are exported with field name, type, and options. We pre-create matching custom fields in Odoo using Studio developer mode before data migration. Field type conversion applies: multi-checkbox from Ortto maps to Odoo many2many_tags; date fields map to Odoo date; number fields map to Odoo float or integer. Aggregate field types are flagged during discovery and excluded from migration because Ortto's aggregate type is not accessible via API; we document these for manual recreation in Odoo.

Ortto Account custom fields (up to 25) map to Odoo Account custom fields via Studio. We apply the same type-conversion logic as People custom fields. Destination platforms with field type restrictions require text concatenation for multi-value selections or a separate relational model for complex picklist structures.

Ortto Capture Widgets (forms and pop-ups) with up to 50 fields are exported for field mapping reference. Form content (templates, body copy, visual styling) requires separate export and manual rebuild because UI-layer configurations are not accessible via Ortto API. We deliver a written form inventory documenting field names, types, validation rules, and submission logic so the customer's admin can rebuild forms in Odoo Website builder or a third-party form tool.

Ortto KB articles and category structures are exported for content migration. Article body content, category hierarchy, and internal linking are preserved. Rich media embeds and embedded video references are flagged for manual adjustment in Odoo Knowledge (a separate Odoo app). We note that Odoo Knowledge requires the Knowledge app to be installed in the customer's Odoo instance; if not present, article migration is deferred to a post-migration Odoo module activation.

Ortto Owners (users who own People, Accounts, Deals) map to Odoo CRM User records. We resolve by email match against the Odoo destination User table. Any Ortto Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before Contact and Account import proceeds. Active/inactive status is preserved using Odoo's active boolean.

Journeys and automation flows in Ortto cannot be exported via API or CSV. We do not migrate automation logic as code. During discovery, we document the Journey canvas structure, trigger conditions, branch logic, and action steps from Ortto's UI. This documentation is delivered as a written automation inventory that the customer's admin or an Odoo implementation partner uses to rebuild flows in Odoo Studio (available on all paid Odoo editions). The inventory includes screenshots, trigger event descriptions, and recommended Odoo Studio equivalents for each action type.