Migrate from Regal.io to Odoo CRM

Regal Contacts map to Odoo Lead by default, with an optional split to Contact+Company for contacts that represent established accounts. The split decision is based on whether the Regal Contact has a company_name attribute or domain-based Company affiliation. We set the Odoo Lead email and phone from Regal's contact attributes, using phone as the primary contact field (Regal requires a phone number for contactability; Odoo tolerates email-only Leads). A custom field regal_contact_id__c preserves the Regal source ID for audit.

Regal's tenant-specific Contact Attributes (profile fields beyond name, email, phone) are extracted from Regal's API attribute schema before migration. Each attribute is mapped to an Odoo Lead custom field created during schema configuration. Multi-value attributes (arrays, tags) map to Odoo Char or text fields with pipe-delimited values. Date, Boolean, and numeric attribute types map to the equivalent Odoo field types. We note any attributes that have no Odoo equivalent and document them for manual enrichment post-migration.

Regal Events (call_initiated, call_completed, sms_sent, email_opened, journey_entered, custom event types) map to Odoo mail.message records linked to the Lead via res_id and model fields. The event type becomes a custom field event_type__c; the event timestamp maps to mail.message.date; event properties (duration, disposition, transcript excerpt) map to additional custom fields on the message record. This preserves the behavioral timeline within Odoo's chatter-like activity view. We batch event writes using Odoo's mail.message batch API to handle high-volume event streams.

Regal Campaigns (outbound programs with list selection, cadence, and goal) map to Odoo CRM Campaign records. Campaign membership (which contacts were assigned to which campaign) migrates as Campaign lines or a linked tag on the Lead. Goal metrics (calls attempted, calls answered, conversion rate) are stored as custom fields on the Odoo Campaign. Cadence and list-refresh logic is platform-specific and documented for manual configuration in Odoo's Campaign follow-up rules.

Regal Journeys (event-triggered sequences of voice, SMS, and email steps) have no direct Odoo equivalent. We extract Journey logic as a step-by-step conditional rule document during discovery, including trigger conditions, step order, channel (voice/SMS/email), and exit criteria. The document is delivered to the customer's admin for reconstruction in Odoo Action Rules or via a third-party marketing automation integration (such as Mautic or Brevo). Journey-trigger conditions that reference Regal Events map to Odoo mail.message domain filters on the equivalent Activity records.

Regal AI Agent configurations — voice scripts, decision trees, persona settings, and handoff logic — are tied to a proprietary runtime that cannot be exported via API or UI. We do not migrate Agent configurations. We deliver a written inventory of every configured AI Agent with its trigger conditions, branching logic, persona description, and handoff rules. If the customer requires AI agent capabilities in Odoo, they select a compatible VoIP telephony add-on (such as a native Asterisk integration or a third-party CCaaS connector) and rebuild agent logic there.

Regal SMS conversations (sent and received messages linked to a Contact) map to Odoo mail.message records with a custom SMS channel indicator. We preserve the message direction (inbound/outbound), timestamp, content, and delivery status. Thread continuity in Odoo depends on the mail gateway configuration; we document the required incoming SMS gateway setup so that future SMS flows through Odoo's messaging channel rather than reverting to Regal.

Regal email thread history attached to Contacts maps to Odoo mail.message records linked to the Lead. Message direction, subject, body, timestamp, and any attachments migrate. Email thread threading (in-reply-to references) is preserved as mail.message parent_id where available. Note that thread continuity in Odoo requires configuring the incoming email gateway (alias domain) post-migration; we document the required configuration steps.

Call transcripts from Regal (available depending on Regal's retention settings at time of export) migrate as ir.attachment records linked to the corresponding mail.message activity. The transcript text is also embedded in the mail.message body for immediate visibility in the activity timeline. Call recording files migrate as ir.attachment records linked to the mail.message; audio file availability depends on Regal's media retention policy and is flagged before migration begins.

Regal branded caller ID carrier registration details and CNAM configuration per campaign are exported as a configuration document. There is no Odoo-native equivalent for caller ID management because Odoo does not include native telephony. We deliver the registration details (carrier account IDs, number assignments, CNAM text) and recommend a VoIP provider (such as Twilio, Asterisk, or a regional carrier) for re-registration post-migration.

Regal's live integrations with Segment, HubSpot, Salesforce, Braze, and Iterable define which contacts are synced and how. We document each active integration endpoint, sync direction, and field mapping during discovery. Post-migration, the customer must reconfigure Odoo's API or webhook integrations with these platforms. If HubSpot or Salesforce is the intended system of record post-migration, we configure Odoo's native bidirectional sync with the relevant platform during the post-migration integration phase.

Regal Custom Objects (tenant-defined schemas beyond standard Contacts, Campaigns, and Events) migrate to Odoo custom models created via the Settings > Technical > Database Structure > Models menu or via data migration scripts. We pre-create the Odoo model with the equivalent field types (Char, Integer, Float, Date, Many2one, One2many) and lookup relationships before data import. Multi-table custom object relationships are resolved using Odoo's Many2one reference fields. Any Custom Object that has a lookup to Regal's native Contact object maps to the corresponding Odoo Lead or Contact record via the regal_contact_id__c source key.

Regal Owners (agents assigned to Contacts and Campaigns) are resolved by email against Odoo's res.users table. Any Regal Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before record import. Owner assignments on Leads migrate as the Lead's user_id field. This step gates the production migration because OwnerId references are required on most Odoo CRM records.

Regal Contactability requires a phone number; contacts without a phone are non-contactable and excluded from Journey triggers. We flag these records during the pre-migration audit and include them in the migration with a custom field contactable__c set to False. In Odoo, these records land as Leads with no phone, which is valid but they will not be reachable by outbound telephony flows unless enriched manually or via a third-party enrichment tool.